Red Hat Bugzilla – Bug 595171
Switching between X to TTY kills audio
Last modified: 2010-08-04 06:48:12 EDT
Created attachment 415987 [details]
Frozen Amarok after TTY switch
Description of problem:
When I switch from X to a TTY with e.g. Amarok running, sound immediatly stops playing and my soundcard is basically dead.
Programs hang accessing it.
Version-Release number of selected component (if applicable):
Fedora-13 pre-release updated to the latest packages.
Steps to Reproduce:
1. Start Amarok and play a file
2. Switch to a TTY, by pressing Ctrl+F2, playback stops
3. Switch back to X
Amarok goes crazy, playing flash videos in firefox hangs firefox. No sound at all. Even restarting amarok doesn't help.
Switching to a TTY shouldn't influence sound at all.
Linux cebox 22.214.171.124-85.fc13.i686 #1 SMP Thu May 6 18:44:12 UTC 2010 i686 i686 i386 GNU/Linux
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03)
Created attachment 415989 [details]
Frozen Firefox after TTY switch
Clemens, are you logged in on the tty you're switching to? You should only use the sound hardware if you're logged on in an active session.
What difference does it make?
When I switch from X to a fresh TTY my sound system is completly messed up, which clearly shouldn't happen.
This is expected behaviour. Access to the audio card by processes of your uid is limited to the consoles where you are the owner. This is done for security reasons so that you cannot eavesdrop into what is played back or recorded in other user's sessions, or can fool the user by playing back your own audio in his session.
This logic has been introduced years ago with the ConsoleKit migration.
Switching back to a console where you are the owner will make audio continue to play.
> Switching back to a console where you are the owner will make audio continue to
No it doesn't, and thats what this bug report is about.
As soon as I switch to another terminal, my sound system is dead until i reboot.
Is there anything I could do in order to track that bug down?
any update in this? I also reproduce this problem on another laptop which has an intel audio chip.
*** This bug has been marked as a duplicate of bug 608712 ***