Description of problem: As description says, a high-frequency sound coming from the speakers when there has been no connection to pulseaudio for ~10 seconds. Very annoying, and a regression, seeing as I use pulse now on ubuntu, and it works nice. How reproducible: every time Steps to Reproduce: 1. Boot fedora, turn on speakers 2. done Actual results: High-freq sound coming from speakers Expected results: silence Additional info: The sound disappear when anything is connected to pulseaudio (it seems). Even the pa-volume-control hw-info: http://www.smolts.org/client/show/?uuid=pub_044784f1-3d15-4c08-a282-6c1300053734 Seems like its the "ATI Technologies Inc SB600 Azalia" that is the sinner, seeing as I don't use anything but the dvi-output from the card. What logs are needed for this?
Sounds more like a driver/hw problem. Could you please run "pacmd ls" when you hear this and attach this here. If everything is correct in PA this should tell us that no app is playing audio an the device closed becuase idle. If that is the case then we should reassign this to the kernel, as it is a kernel driver/hw prob.
Created attachment 361305 [details] output from pacmd ls
Created attachment 361316 [details] alsa-info.sh output
The "pacmd ls" shows that all of PA's sinks are in state "SUSPENDED" meaning that the devices are closed. If you hear noise this means the sound must come from somewhere else.
Why changing from "10 seconds" to "for a while?", I counted, and it starts after pretty much 10 seconds every time.
do you see any interesting messages in /var/log/messages ? especially around the time the problem kicks in / goes away (when you start playing sound). -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I'll get a copy of /var/log/messages uploaded as soon as I get the time (hopefully tomorrow). Any other files that would be interesting?
The problem seems to be the same as described on launchpad, and can (probably,haven't tested it yet) temporarily be solved by changing "options snd-hda-intel power_save=10 power_save_controller=N" to "options snd-hda-intel power_save=0 power_save_controller=N" in alsa-base.conf Will test when I get the time.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I can confirm that adding line "options snd-hda-intel power_save=0" to a file in /etc/modprobe.d (for example /etc/modprobe.d/snd_hda_intel.conf) and rebooting works as a workaround for me.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.