On further diagnostic (now that we know for sure what we are looking for), the user logged in to TTY2 is relevant. This eliminates the statistical match for a hard match to the problem. If the TTY is logged in as root or not logged in, happens every time.
I'm in the habit of doing all root work directly from text consoles (no X as root for the obvious reason). This is actually more secure than sudo as an X key sniffer can never grab the root password. A program that requires X doesn't get root. I make no exceptions except xterm (testing X config files). I think this is still a direct bug. Users able to play sound ought to be the sum of all logged-in users on all TTY sessions (X or text), not just the current one. I'm adding my user to audio group for now. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
