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 309966 - startup without a sound card fails
startup without a sound card fails
Status: RESOLVED DUPLICATE of bug 170719
Product: totem
Classification: Core
Component: general
1.0.x
Other All
: Normal blocker
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2005-07-10 18:54 UTC by Steven Howe
Modified: 2005-07-10 19:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description Steven Howe 2005-07-10 18:54:00 UTC
Please describe the problem:
Totem has an option for to '--disable-sound'. But if you don't have a sound
card, the program posts a window with "ALSA device "default" does not exist."
and then quits.

What is the point of having the '--disable-sound' if the program is still
testing for a soundcard. The default "ALSA device" should become /dev/null.

No doubt your asking "How is it possible to not have a sound card?" I have a usb
sound device, that outputs to a stereo. When the portable is not attached, I
don't have a sound device, but I still have eyes.

Steps to reproduce:
1. disbale your sound card in the bios (or in /etc/modules.conf)
2. run the program totem (with or without --disable-sound)
3. 


Actual results:
Get an error window with the message "Totem could not start up. .... (see above)

Expected results:
A warning window if sound was enabled, telling the user no sound device found.
If totem was started with '--disable-sound', I'd expect the program to start. 

Does this happen every time?
YES

Other information:
Only foolish comments about programmers failing to fully explore found and
explicit startup conditions.
Comment 1 Bastien Nocera 2005-07-10 19:00:50 UTC
And a user who fails to look for duplicates :)

*** This bug has been marked as a duplicate of 170719 ***