Red Hat Bugzilla – Bug 86481
After ctrl+alt-bs user exit, other users cannot use sound
Last modified: 2007-04-18 12:52:17 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020830
Description of problem:
If a user exits the gnome desktop using ctrl-alt-backspace (may be because an
application has locked), when another user tries to login, permissions on
devices are still held by the previous user. In particular, the sound devices.
If you have a mixer applet on your panel, you get an error dialogue box with
the message "Couldn't open mixer device /dev/sound/mixer". Killing any hung
processes from the previous user does not help. The only solution I have found
is to reboot. Is there some /etc/init.d/ typer service I can restart to reset
Using Redhat 8.0, fully patched via redhat network.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.login to gnome desktop as user A
2.exit desktop using ctrl-alt-backspace
3.login to gnome desktop as user B
Actual Results: user B, who has a mixer applet, gets "Couldn't open mixer
device /dev/sound/mixer" error and has no access to sound.
Expected Results: user B should have access to sound as normal
Nalin, George - is the problem here consolehelper or gdm?
Most likely gdm. The problem is that there are many races and it's possible
that the pam_close_session was not called in that case. This should be fixed in
the newest devel version, but not in the stable version.
This should be now fixed in upstream gdm 126.96.36.199 (stable) which I released today.
We've upgraded, so this is likely fixed in RAWHIDE.
Does it work for you?
I've been using Redhat 9.0 for several months with gdm-188.8.131.52-5.1. This
version does not behave in the same way; a simple ctrl+alt-bs user exit will not
leave the sound device (an others) in an unusable state. However, if the user X
session crashes the same problems can still occur, sometimes. e.g. the
commercial demo version of Tux racers is particularly prone to causing the problem.
Can I use gdm 184.108.40.206 on RH 9? If so I'll try and that and see what happens
with Tux racers....
*** This bug has been marked as a duplicate of 134941 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.