Red Hat Bugzilla – Bug 215932
Totem can't start without soundcard
Last modified: 2007-11-30 17:11:49 EST
Description of problem: Totem could not startup. Version-Release number of selected component (if applicable): totem-2.17.3-1.fc7 How reproducible: If starting Totem there's an error-message displays: Totem could not startup. Could not open resource for writing. Steps to Reproduce: 1. Start Totem 2. Receive Error-Message 3. Actual results: Expected results: Additional info:
Created attachment 141541 [details] totem.strace following the out put of $ strace -o totem.strace totem
I figured it out, the error appears if no soundcard is installed or detected!
+1 on this bug. It bit me too. I think a lack of soundcard also crashes firefox under some circumstances, but I'll report that separately if I can reproduce it. 1) Playing movies without a sound card should be possible 2) The message should be a warning, not an error, and it should state clearly that no sound card is available. (Unlike the current user-unfriendly message.)
I closed the upstream bug today: http://bugzilla.gnome.org/show_bug.cgi?id=170719 Patch attached below, will be in 2.16.5
Created attachment 142868 [details] totem-2.16-dont-error-with-no-soundcard.patch
Bug is against rawhide, and I believe this was fixed in the upload of totem-2.17.5.
Created attachment 153723 [details] f7t4 screenshot of totem startup While this bug has been closed and it is 3x months down the track, I am still seeing the: An Error Occurred: "Cannot not open resource for writing" user-unfriendly message with: totem-2.18.1-3.fc7 {fc6/updated/upgraded to f7t4} $ totem ** Message: Error: Could not open resource for writing. gstalsasink.c(625): gst_alsasink_open (): /autoaudiosink0-actual-sink-alsa: Playback open error on device 'default': No such device
Note the machine definitely does not have sound capability, so it would appear the resource is the non-existent audio output. Should this be re-opened, or made a new bug.
(In reply to comment #9) > Note the machine definitely does not have sound capability, so it would appear > the resource is the non-existent audio output. Should this be re-opened, or made > a new bug. File a new bug. I've already fixed this problem in trunk and gnome-2-18 branches upstream. Mind, the original bug was that it didn't even let you *play* anything after it complained about the error. Now you still get the error, but it will let you play the movie.