Bug 503390

Summary: Amarok adds track to dynamic playlist but it is greyed out and track details claims it does not exist if file path is too long
Product: [Applications] amarok Reporter: robert marshall <robert>
Component: PlaylistAssignee: Amarok Bugs <amarok-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: tuomas
Priority: NOR    
Version First Reported In: 3.2.2   
Target Milestone: kf5   
Platform: KDE Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description robert marshall 2025-04-26 13:51:54 UTC 
If a file in the collection has too long a path it may be in the collection but there's clearly a shorter path limit in the playlist so
/home/robert/Music/currListen/BBCMusMag/vol22/Elgar; James Ehnes, BBC National Orchestra of Wales, David Atherton, Susan Gritton, Andrew Kennedy, BBC Symphony Orchestra and Chorus, David Lloyd-Jones - BBC Music, Volume 22, Number 10: Violin Concerto _ The Spirit of England/01 - Edward Elgar - Violin Concerto in B minor, op. 61: I. Allegro.ogg
(!!!) won't play, track details claiming it doesn't exist.

File name was produced by ripping a cd with k3b

If I rename the directory to a rather shorter name so /home/robert/Music/currListen/BBCMusMag/vol22/BBC Music, Volume 22, Number 10: Violin Concerto _ The Spirit of England  there's an automatic rescan and the tracks in the playlist are no longer greyed out and can be played successfully (this is good!)

Maybe a warning should be produced on adding the tracks or on a collection rescan  that the files can't be played but are in the collection - or the playlist path name length limit should be the same as in the collection?
Comment 1 Tuomas Nurmi 2025-04-30 12:50:45 UTC 
Thank you for the report! This one seems to be duplicate of 298413 so marking it as such. This was something I had a quick look at when doing the database updates some time ago, but there didn't seem to be much synergy, and this would have required more intrusive changes than the other db related bugs, so not fix yet.

*** This bug has been marked as a duplicate of bug 298413 ***