Version: 2.3.2 (using KDE 4.5.4) OS: unspecified (I saw bug 195161, which is somehow related to this one - both require more sophisticated handling of file/directory paths.) Currently it is possible to have multiple Amarok-on-Linux instances access the same collection database (which may be located on a home server, for example). For this to work, the music directory must be at the exact same location, for example /mnt/data/Music. When you add an Amarok-on-Windows instance, this does not work anymore: It is not possible to have the exact same paths on a Windows system, for two reasons: 1) because they use so-called drive letters 2) because the path separator is a backslash instead of a slash (the latter is currently not a problem, because even Windows instances use slashes internally, but once bug 195161 gets fixed by having backslashes in the database, instead of slashes, it will become a problem) So while an example entry in the collection database (urls table), created by the Linux instance looks like this: id deviceid rpath directory uniqueid 7638 -1 ./mnt/data/Music/Madina Lake - (2007) - [Alternative Rock] - From Them, Through Us, To You/[12] Madina Lake - Morning Sadness.mp3 602 amarok-sqltrackuid://5f1300e27f2bbd51fef5b14722d2f966 ... the same entry created by a Windows instance looks like that: id deviceid rpath directory uniqueid 7638 -1 M:/Music/Madina Lake - (2007) - [Alternative Rock] - From Them, Through Us, To You/[12] Madina Lake - Morning Sadness.mp3 1681 amarok-sqltrackuid://5f1300e27f2bbd51fef5b14722d2f966 We need a way to make this OS-independent, so that it's possible to access the collection database by multiple Amarok instances on different OSes at the same time. Reproducible: Always
This is a duplicate of bug 160841
*** This bug has been marked as a duplicate of bug 160841 ***
If you call it a duplicate, you should change the summary / title of the original bug - I guess it should be changed to something like "Paths need to be OS-independent". If it had that summary, I would have found it on my search, and just commented instead of opened a new bug report ;)