GNOME Bugzilla – Bug 721043
no diagnostics whatsoever
Last modified: 2014-01-07 14:56:03 UTC
When i am staring at black screen how do I tell Is totem buffering/locked up/playing black video/failing to display non-black video? When you read the fineprint at the bottom you can see if position is changing or not. There is Playing and Paused fineprint, I wonder if there is Buffering as well. Recent totem does not keep big buffer and buffering is not configurable so I can't tell .. If the fine print says Playing and the position is updating how do I tell if I have black video/failing codec/what codec it would be?
Totem doesn't show an error because GStreamer doesn't report any back to it. It might be a hang, or an infinite loop, no way to tell without you giving a reproducer. You can then get more debug information using: GST_DEBUG=*:9 totem No need to post that log though, the video file with which to reproduce the problem should be enough.
After checking with other players I found that I actually have a file that has silence with black screen at the start. Still it's very hard to tell what's going on with totem.
(In reply to comment #2) > After checking with other players I found that I actually have a file that has > silence with black screen at the start. Well, that's helpful. > Still it's very hard to tell what's going on with totem. Does the time label in the status bar not change?
It does. It is, not very prominent label with the player fullscreen. Also I cannot tell what codec totem uses and if it is working properly or reporting any errors. There is no troubleshooting section in the docs.
(In reply to comment #4) > It does. It is, not very prominent label with the player fullscreen. The fullscreen controls have been redesigned already. See totem master. > Also I cannot tell what codec totem uses and if it is working properly or > reporting any errors. If there are errors to report, they will popup a dialogue. > There is no troubleshooting section in the docs. Report a bug with all the details you can, and we'll tell you what we need :) Closing this as incomplete as it seems to be a user error (and the UI has already been changed to make it easier not to make this mistake in the future).