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 577419 - Improve error message when fail to download video
Improve error message when fail to download video
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: dont know
0.10.x
Other Linux
: Normal enhancement
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-03-31 08:03 UTC by Robert Ancell
Modified: 2010-05-22 18:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description Robert Ancell 2009-03-31 08:03:34 UTC 
Currently when the HTTP download of a video fails Totem reports:
"Could Not Open Location; you might not have permission to play the file."

This is misleading to users in at least two common cases:

a.  The video URL does not work (not available, e.g. if I search for "ibm linux ad prodigy" and play the first video the URL fails with a 404.

b.  Video URLs stored in playlists appear to go stale and return 404.  If the video is searched for again it has a new URL.

It would be better if there was an error message for a failed TCP/IP connection:
"This video cannot be downloaded.  Please check your network connection"

and an HTTP error response:
"This video is no longer available"
(not great but not sure what else you can say)

For more information see:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/323649
Comment 1 Bastien Nocera 2009-03-31 12:29:36 UTC 
GStreamer is the one giving us crappy error messages.

This was fixed in the xine-lib backend a long time ago. The code in bvw_error_from_gst_error() tries it best, but is far from complete.
Comment 2 Tim-Philipp Müller 2010-04-04 12:52:23 UTC 
Could someone attach a GST_DEBUG=*:4 log please?
Comment 3 Tobias Mueller 2010-05-22 18:33:52 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!