After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 582090 - totem handles non-existent playlist songs poorly
totem handles non-existent playlist songs poorly
Status: RESOLVED DUPLICATE of bug 303942
Product: totem
Classification: Core
Component: general
2.26.x
Other All
: Normal normal
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-05-10 19:02 UTC by Martin Olsson
Modified: 2009-05-10 21:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description Martin Olsson 2009-05-10 19:02:40 UTC
Please describe the problem:
When I load a playlist (I used .m3u format) into totem, it will happily load in all the songs listed even if they don't exist. Of course once the music has been playing for a while it eventually gets to the non existing song and then totem shows an error and the music _stops_ until you press OK.

For many reasons I feel that the error should be shown directly when the playlist is loaded instead:

A) an explicit user action is "temporally connected" to the error,
B) once I've started my music playlist / music videos or whatever I know that they will play all evening

A few hours ago I had dragged a huge folder from a network share into totem and all the songs in that directory tree was playing. After a while the music stopped and it said "location not found". This prompted me to incorrectly start troubleshooting / debugging the network.

I guess what's needed is a small file_exists() check in the play list loading function or so ... ?

Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Philip Withnall 2009-05-10 21:17:20 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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