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 142822 - totem crashes if sound device is already in use
totem crashes if sound device is already in use
Status: RESOLVED DUPLICATE of bug 138830
Product: totem
Classification: Core
Component: general
unspecified
Other Linux
: Normal major
: ---
Assigned To: Bastien Nocera
Bastien Nocera
Depends on:
Blocks:
 
 
Reported: 2004-05-20 09:25 UTC by Sitsofe Wheeler
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6


Description Sitsofe Wheeler 2004-05-20 09:25:30 UTC 
Steps to reproduce:
1. Start rhythmbox
2. Start playing a track
3. Start totem from the command line

Actual result:
totem appears to load but then vanishes and a dialog saying:
The Application "totem" has quit unexpectedly.
You can inform the developers of what happened to help them fix it.  Or you can
restart the application right now.

(but how to find out who to inform? :)

If you start it from the command line it is clear that totem knows what is wrong
because it sometimes says:
ALSA lib pcm_hw.c:1056:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p failed: Device
or resource busy

Expected result:
totem to start and sit there (this is the first time I've started it). If I try
to play a movie or something that requires sound I expect it to pop up a dialog
saying that it couldn't get the device.

This version of totem was downloaded from freshrpms (totem-0.99.11-1.1.fc2.fr)
was built without gstreamer support (i.e with xinelib support), the system uses
ALSA and gstreamer has been set to use OSS source and sinks.
Comment 1 Sitsofe Wheeler 2004-05-20 09:38:21 UTC 
Oops forgot to say that my sound card was an Ensoniq ES1371
Comment 2 Bastien Nocera 2004-05-29 23:24:32 UTC 
Please attach the backtrace of the crash, and of the hang.
Comment 3 Sitsofe Wheeler 2004-06-01 08:31:48 UTC 
Phew. It took a while to run totem through gdb but here's the result.

Program received signal SIGSEGV, Segmentation fault.
0x0231c1fc in Arts::StartupManager::startup () from /usr/lib/libmcop.so.1
(gdb) bt

+ Trace 46980

  • #0 Arts::StartupManager::startup
    from /usr/lib/libmcop.so.1
  • #1 Arts::Dispatcher::Dispatcher
    from /usr/lib/libmcop.so.1
  • #2 arts_backend_init
    from /usr/lib/libartscbackend.so.0
  • #3 arts_init
    from /usr/lib/libartsc.so.0
  • #4 ??
    from /usr/lib/xine/plugins/1.0.0/xineplug_ao_out_arts.so 

I have no idea why it appears to be using the arts backend since I use GNOME and
esound.
Comment 4 Bastien Nocera 2004-06-01 10:09:38 UTC 
Known bug in arts. See:
http://bugs.kde.org/show_bug.cgi?id=62603

*** This bug has been marked as a duplicate of 138830 ***
Comment 5 Sitsofe Wheeler 2004-06-01 22:10:03 UTC 
Why is totem defaulting to using arts?
Comment 6 Bastien Nocera 2004-06-02 00:15:11 UTC 
Because it can't find anything else...
Comment 7 Sitsofe Wheeler 2004-06-02 08:09:45 UTC 
Hmm... So what's the search order? Does totem look for esound?