Created attachment 85674 [details] View of two playlist entries for the same file. One is in the collection; the other is not. When I open amarok, some of the tracks left in the playlist from a previous session show up as not belonging to the local collection (although they are), hence with no metadata such as rating or labels. If I re-add the same tracks from the collection, I can have playlist entries related to the same tracks (and same files), some with metadata and some without. I hope the attached picture will clarify. It happens every time I re-open amarok, but not to all entries in the playlist, so it's a bit random.
Where is your database and where are the tracks located?
The tracks are all under "~/Music", which is the tree included in the local collection. All those folders are in the same ext4 partition as the "home" sub-system. The MySQL database resides in a different ext2 partition. It is NOT physically in the same partition as /var. I use a "bind mount": (in /etc/fstab) /xtra/mysql /var/lib/mysql/ none bind
Is the database accessible when Amarok starts? Or is that partition only mounted once Amarok starts?
The DB is always mounted and accessible. I can connect to it with MySQL client with no intervention on amaroK side.
Thank you for the feedback.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Changing back to REPORTED per request of Myriam (Amarok dev).
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!