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 144161 - totem defaults to using artsd even when esound is already running
totem defaults to using artsd even when esound is already running
Status: RESOLVED DUPLICATE of bug 138830
Product: totem
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Bastien Nocera
Bastien Nocera
Depends on:
Blocks:
 
 
Reported: 2004-06-11 13:18 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-06-11 13:18:21 UTC 
Steps to reproduce:
1. Find a computer that cannot do hardware mixing
2. Run a program that set to use esound (e.g. rhythmbox with gstreamer set to
esound)
3. do a ps auxw | grep esd and check that esd is running
3. Run a xine based totem

Expected results:
totem to use esound

Actual results:
totem tries to start artsd (which crashes but that's bug 138830)

Additional information
This bug was spun off from bug 142822
Comment 1 Bastien Nocera 2004-06-14 18:12:28 UTC 
If you remove the arts plugin, does Totem correctly use esound?
Comment 2 Sitsofe Wheeler 2004-06-14 18:16:04 UTC 
Yes - but surely I shouldn't need to? If I have arts running already then it
should use that, if I have esound running already then it should use that and if
neither are running then it should choose...
Comment 3 Bastien Nocera 2004-06-14 18:20:18 UTC 
Well, it will autodetect, the only problem that I can see is that it will crash
because arts is buggy.
So you just need to remove arts, and you'll be done with it.
Comment 4 Bastien Nocera 2004-06-14 18:20:57 UTC 

*** This bug has been marked as a duplicate of 138830 ***
Comment 5 Sitsofe Wheeler 2004-06-14 18:45:20 UTC 
Wait a second! It autodetects wrongly - why does it start artsd when there's a
perfectly good esound already? Are you saying that it is crashing in the
autodetection? If so can't you auto detect esound first?