GNOME Bugzilla – Bug 630483
Totem hide (informative) HTTP error from user
Last modified: 2012-10-29 18:20:21 UTC
Totem hide (informative) HTTP error from user. Steps for reproduce: 1. Run totem (from console) with some high load online radio URL wich reaches peer connection limit, for example: $ totem http://www.r-uniton.ru:8500 Actual result: Totem show error message: An error occurred Could not open location; you might not have permission to open the file. Expected result: Error message must include HTTP error which I can see in terminal window (from stderr): 400 Server Full Details: Full output from console: ** Message: Error: "http://www.r-uniton.ru:8600": Server Full gstsouphttpsrc.c(1096): gst_soup_http_src_parse_status (): /GstPlayBin2:play/GstURIDecodeBin:uridecodebin0/GstSoupHTTPSrc:source: 400 Server Full Ubuntu 10.04 totem-2.30.2-0ubuntu GStreamer 0.10.28
I got the same here: fbesoain@debian:~$ totem http://www.r-uniton.ru:8500 Cannot connect to server socket err = No existe el fichero o el directorio Cannot connect to server socket jack server is not running or cannot be started epc_publisher_create_server: listening on http://debian:43276/ ** Message: Error: "http://www.r-uniton.ru:8500": Server Full gstsouphttpsrc.c(1099): gst_soup_http_src_parse_status (): /GstPlayBin2:play/GstURIDecodeBin:uridecodebin0/GstSoupHTTPSrc:source: 400 Server Full know in both messages says: Server Full. , I will try later, just for check it out
Displaying the HTTP error code would be confusing and unhelpful for the majority of users. What we could do, however, would be to make the error message more specific for some HTTP error codes. e.g. “Could not open location: the server is full. Please try again later.” for error 400.
From the output it looks like there is some kind of problem here with the error handling. According to the "** Message" the error has a message string which includes "Server Full" (in English though, but still, that can be fixed). However, the error string that totem is showing to the user is a different one. It might come from another error message posted on the bus after the original one, since it's a generic default error message.
Having a reliable way to reproduce this bug would be useful to fix the problem.
I tried to setup icecast[1] to have a maximum limit of users of 0, and ended up getting: Icecast connection limit reached (403), not 400. 400 isn't "server full" either. We have better error messages now. Could you please get the error output (it's on stderr) with a newer version of Totem? It has better debug, and we should be able to add a hack for your case easily. [1]: Installed icecast cp /etc/icecast.xml ~/icecast.xml modify (changed the log dir and the <clients> value under <limits> to 1 icecase -c icecast.xml and tried to connect to
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!