[prev in list] [next in list] [prev in thread] [next in thread]
List: amarok-bugs-dist
Subject: [Bug 158581] New: wrong deviceid if path contains symlinks
From: Roman <mereandor () gmail ! com>
Date: 2008-02-29 15:17:22
Message-ID: 20080229161721.158581.mereandor () gmail ! com
[Download RAW message or body]
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=158581
Summary: wrong deviceid if path contains symlinks
Product: amarok
Version: unspecified
Platform: Compiled Sources
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
AssignedTo: amarok-bugs-dist kde org
ReportedBy: mereandor gmail com
Version: 1.4 svn (from less than a week ago) (using KDE 3.5.8)
Installed from: Compiled From Sources
Compiler: gcc-4.2.3
OS: Linux
As it seems amarok does not resolve symlinks to get the correct device, thus the \
media management does not work properly (files are dropped from the collection when \
the device is removed, ...). Here is an example to illustrate this:
/media is a symlink to /run/media resides on the /-device, removeable devices are \
mounted under /run/media Now a removable disk is mounted at /run/media/mm. If I add \
this folder to my collection the deviceid is set correctly. But when I add /media/mm \
instead the deviceid is set to the /-device, thus ending in the misbehavior mentioned \
above.
The proper way of handling this would be to compare the realpath of a directory (it's \
path with all symlinks resolved) with the list of realpaths of all mount-points to \
see on which device the data in this directory is stored. \
_______________________________________________ Amarok-bugs-dist mailing list
Amarok-bugs-dist@kde.org
https://mail.kde.org/mailman/listinfo/amarok-bugs-dist
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic