I can confirm this problem that Totem hangs when the server does not respond (so it is probably difficult to reproduce). I have not encountered any problems killing Totem in this situation., though.
In my case, I first opened a webradio station through Firefox, by going to http://www.slayradio.org/home.php and clicking on the "Broadband" link in upper left corner. After confirming to open the file in "Video Player", Totem opened but then didn't react (clock cursor appeared, and the Totem window was not repainted any more). Looking at ps -Af , I saw that Totem was started with /tmp/listen.m3u as parameter. I killed the hanging Totem instance and started it manually with that parameter; again it didn't respond. However, after a while it timed out and displayed the same message as described by Vern ("An error occured" etc). I clicked OK and then selected another URL from the playlist window, which was then played without problems. The listen.m3u which is the playlist that was returned from the website contains five different HTTP urls (http://relay?.slayradio.org:8000/), and apparently the very first of these did not respond. I checked this manually on another machine with xmms; it didn't get a connection either to this particular server (relay3), but displayed a meaningful status message ("Connected: waiting for reply"). Looking at the hanging instance with strace -p showed that it waited in a select call: select(20, [19], NULL, NULL, {26, 612000}) In my opinion Totem should in this case: - still respond to user interaction - allow the user to select another entry from the playlist (which should abort the current connection try) - show a status message that tells the user what's going on (so he knows the app is not crashed, but the server "has a problem") -- totem hangs when source does not respond https://bugs.launchpad.net/bugs/176457 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
