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 368159 - Totem fails if no soundcard is present
Totem fails if no soundcard is present
Status: RESOLVED DUPLICATE of bug 170719
Product: totem
Classification: Core
Component: GStreamer backend
2.16.x
Other All
: Normal minor
: ---
Assigned To: Maintainer alias for GStreamer component of Totem
Maintainer alias for GStreamer component of Totem
Depends on:
Blocks:
 
 
Reported: 2006-10-31 08:37 UTC by Frederik Hertzum
Modified: 2006-11-01 18:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Frederik Hertzum 2006-10-31 08:37:34 UTC
Please describe the problem:
Even when playing video files, Totem decides to give up if no sound card is present. There is no problem if the sound card is actually present but used by another process. This happens even if the video file does not have an audiotrack.

Steps to reproduce:
1. Disable your sound card (pull it out, turn it off, unload modules (should work) or similar)
2. Open a video file in Totem, with a supported plugin
3. Sit back and watch the fireworks... not happening.


Actual results:
I get an error message saying: "Could not open resource for writing." and totem stops. The main totem window loads in the background, but is removed just prior to the message appearing.

Expected results:
I would expect some sort of warning message like: "Could not find audio device for playback" (and only if audio is attempted to be played) and the program to drop audio playback, but still support video playback, skipping files that did not contain video.

Does this happen every time?
Yes, this happens every time. As far as I know it's not even restricted to this version.

Other information:
It's likely a design flaw that's been around since the very first version (although I have only seen it in this version and 2.14, since I didn't use it before then -- and then only briefly). I have no idea if the problem is present using the xine-lib backend or if the mozilla plugin is affected, but I would suspect so.
Comment 1 Tim-Philipp Müller 2006-10-31 10:16:36 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 170719 ***
Comment 2 Frederik Hertzum 2006-11-01 18:41:43 UTC
search function for bugzilla should be updated.