Red Hat Bugzilla – Bug 362701
artsd hangs around forever when launched from GNOME
Last modified: 2015-07-13 13:35:54 EDT
I have the same issue on RHEL5 after launching k3b over ssh.
+++ This bug was initially created as a clone of Bug #140262 +++
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2)
Description of problem:
If artsd is launched from within GNOME (as opposed to when KDE is set
as the desktop) then it will continue to run after the user logs out.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Log into GNOME.
2. Start a terminal.
(this will actually fail since noatun doesn't work with wavs but
4. Quit noatun.
5. Log out of GNOME.
6. Log into a virtual terminal.
7. run ps auxw | grep artsd
An artsd process is found.
No artsd process to be running.
We are seeing this a lot in the small computer room we have because
users sign in and out all the time and use things like K3B from GNOME.
I'm not sure if this is leading to sound problems (i.e. the device
can't be obtained when they log into GNOME because the soundcard has
no hardware mixing and is kept open by artsd).
This does not happen if the Desktop Environment is set to be KDE.
-- Additional comment from email@example.com on 2005-10-20 18:55 EST --
This is still here in FC4's arts-1.4.2-0.fc4.1
-- Additional comment from firstname.lastname@example.org on 2006-05-26 13:14 EST --
This is still here in FC5's arts-1.5.2-0.1.fc5 . Perhaps this should be filed
against the devel version?
-- Additional comment from email@example.com on 2007-03-12 17:55 EST --
Still here on FC6 with arts-1.5.6-0.1.fc6
Same issue with RHEL5.1
Same issue with RHEL5.2
Does this still happen with the current version?
Hi, thanks for the message. I am not able to reproduce this with RHEL5.5.