Bug 609666 - "play login.wav" in an SSH console fails with a freeze, unless logged in locally
Summary: "play login.wav" in an SSH console fails with a freeze, unless logged in locally
Alias: None
Product: Fedora
Classification: Fedora
Component: alsa-lib
Version: 13
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Jaroslav Kysela
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-30 19:38 UTC by Marcos
Modified: 2011-06-27 19:12 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2011-06-27 19:12:47 UTC

Attachments (Terms of Use)

Description Marcos 2010-06-30 19:38:25 UTC
Description of problem:
When logged in remotely (ssh or VNC), audio is only available if the same user is also logged in locally.

How reproducible:

Steps to Reproduce:

If logged in locally as mgpapp (X or console) on pc1:
1. [mgpapp@pc2 ~]$ ssh pc1
2. [mgpapp@pc2 ~]$ play /usr/share/sounds/purple/login.wav
Actual results:
The console freezes with the following display, without having played anything on the speakers of pc1:

[mgpapp@rana ~]$ play /usr/share/sounds/purple/login.wav


 File Size: 192k      Bit Rate: 706k
  Encoding: Signed PCM    
  Channels: 2 @ 16-bit   
Samplerate: 22050Hz      
Replaygain: off         
  Duration: 00:00:02.18  

In:0.00% 00:00:00.00 [00:00:02.18] Out:0     [      |      ]        Clip:0   

Expected results:

Normal playback of the file login.wav through the speakers of pc1.

Additional info:

If I login locally into pc1 (X or console), the procedure above produced the expected results.
If I logout from pc1, the procedure above produces the freeze described above.
If I log back in, it produces expected results again again.

Comment 1 Marcos 2010-06-30 19:42:56 UTC
In Steps to Reproduce, the first line should read:
If NOT logged in locally as mgpapp (X or console) on pc1:

Comment 2 Bug Zapper 2011-06-01 15:08:23 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 3 Bug Zapper 2011-06-27 19:12:47 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.