Hide Forgot
Created attachment 489914 [details] Output from alsa-info Description of problem: I have not been able to figure out a pattern to this, but the audio on my machine is randomly cutting out. I originally thought it was related to suspend, but lately I've been noticing the issue even when I haven't suspended. I spent some time debugging with fenris02 on IRC, and tested at least the following: * Pulseaudio is indeed running * Permissions are correct (getfacl /dev/snd/*) * SELinux is permissive * Logging out and back into the graphical console did not fix it Version-Release number of selected component (if applicable): How reproducible: Very random. Steps to Reproduce: 1. Open a youtube video, play an mp3 with totem, or the like 2. 3. Actual results: Sound plays Expected results: Software indicates that sound is playing, but no sound actually plays Additional info:
Created attachment 489915 [details] Output from pulseaudio -vvvvv
http://www.smolts.org/client/show/pub_515e5d4d-50f2-414a-b6c4-eb749d5346db
Created attachment 491626 [details] Output from pacmd ls
is the output from pulseaudio -vvvvv after or before the problem occurs? can you pinpoint the point in that log when you notice the problem? that would make it easier to try and figure out what's going wrong.
The output is from when I tried to restart pulseaudio while the problem was occurring. Since the problem occurs so sporadically, the only way to capture the output from pulseaudio -vvvvv when it begins would be to a) have the pulseaudio daemon always run with -vvvvv, and b) to set a cron job to play a sound every 10 minutes so I'm more likely to notice when the issue begins. Should I do that?
it would be useful to have pulseaudio and /var/log/messages output from when it happens, definitely. you can kill pulseaudio right after boot and re-run it from a console with -vvvvv then just leave it running till the problem happens, i guess?
OK, I'll give that a try. I might even be fancy and nohup it to a file.
Was there a resolution to this? I've found what seems to be the same problem in RHEL 6.2. Any information would be great.
This problem fixed itself for me when I upgraded from FC14 to FC16.
Ah, thanks for the update. Sadly I can't update any further. I think it may be caused by the differential between the alsa-libs and alsa-driver in case anyone else stumbles upon this problem.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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