Bug 165375

Summary: Dragonplayer gives no feedback if it cannot play the media requested
Product: [Applications] dragonplayer Reporter: David Edmundson <kde>
Component: generalAssignee: Dragon Player Mailing List <dragon-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: fabiolocati, nate, rakuco, tsudakazuki, xaver.xn
Priority: NOR Keywords: usability
Version First Reported In: 22.11.90   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In: 25.08.0
Sentry Crash Report:

Description David Edmundson 2008-06-30 01:30:24 UTC
Version:            (using KDE 4.0.83)
Installed from:    Compiled From Sources

Dragonplayer gives no feedback if it cannot play the media requested. If a user tells it to play, for example a DVD ISO or a word document, Dragon player just says "no media" loaded.

Some feedback to the user is needed. Personally I'd rather not have a popup-dialog box. Any suggestions?
Comment 1 Xaver Wurzenberger 2009-05-23 21:32:14 UTC
Confirmed here. I had to start it via console to find out why it did nothing when trying to play a dvd.

In my case, the file permissions were incorrect, so the stout error was "libdvdread: Can't open /dev/sr0 for reading". To a newbie user, no feedback = unusable program.

Unlike David, I'd like to see an error dialog in cases like this. Yes, it's annoying but if there is an error I want to have as much information as possible right 'in my face' (and not somewhere in the statusbar or sth).

Additionally, David's and my case show that there should be different error messages as well, to make a difference between "I can't read that filetype" and "I can't access the DVD (check permissions)".

Regards,
X.W.
Comment 2 Harald Sitter 2012-06-02 17:38:10 UTC
*** Bug 267377 has been marked as a duplicate of this bug. ***
Comment 3 Justin Zobel 2021-03-09 05:38:56 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 4 Nate Graham 2025-04-13 20:48:34 UTC
This has been fixed in the upcoming 25.08 release.