This bug appears for me in both Kubuntu 13.10 and an up-to-date Chakra Linux. The workaround I only tested in Chakra, since there is no Kubuntu on my machine any more. And I think, but am not sure, the problem showed up first with the arrival of Amarok 2.8. Okay, lets get to the bug description. Fist I noticed, that m3u-playlists which point to files who's names contain a question mark, will not be played correctly. The file with the question mark in it's name was greyed out and could not be played. Checking the meta-data of the song in question I saw that the address where Amarok looks for it does not contain the question mark and thus a error message was generated in the summery tab that its file (the one without question mark in it's name) can't be found. Next I checked the m3u-playlist-file and found that everything was encoded correctly. The question mark was replaced by %3F - with capital "F" as all other letters were capital letters too. Don't know why, but changed it to %3f - please notice the lowercase "f" - and like a miracle the song appeared in the playlist again and also could be played. What I write above holds for any question mark in the path to the sound file. And it even gets worse. M3U-playlists containing a question mark in their name do not appear in the list of the "Saved Playlists" at all. Thus I would say the bug is, that Amarok does not know how to handle question marks in filenames, either when they are not encoded or when a capital "F" is used in the encoding. With a lowercase "f" in the playlist everything works as expected. Would be nice if this could be fixed, since I've got quite a few question marks in my automatically by k3b generated play-lists. Cheers Knut
Thank you for reporting this bug 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 "CONFIRMED" when replying. Thank you!
(In reply to Justin Zobel from comment #1) > Thank you for reporting this bug 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 "CONFIRMED" when > replying. Thank you! Hey, can't reproduce this bug since I can't start amarok anymore. Installed amarok 2.9.71 a while and switched back to Sayonara 'cause it was a bit buggy and no further versions came out. When I tried to start it right know the main window did not show up. I only got an error messages saying "TypeError berichtet einen Skriptfehler: Cannot call method 'connect' of undefined". Just let me know when a new version comes out and I try again.
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!