Created attachment 345218 [details] output of pulseaudio -vvvv and payplay /usr/share/sounds/login.wav (with bell-window-system references) Description of problem: Getting no sound from any applications. Version-Release number of selected component (if applicable): alsa-lib-1.0.20-1 (I tried alsa-lib-1.0.19-3 from koji, which doesn't work either) How reproducible: 100% Steps to Reproduce: 1. Boot up 2. Attempt to play sound (Rhythmbox, paplay, etc) 3. Actual results: No sound is heard, though pavucontrol sees the streams and all my mixer settings are turned up. Expected results: Glorious sound Additional info: alsa-info url: http://www.alsa-project.org/db/?f=1867b836b49b3b71ef001087437ad137773ce46b verbose output from pulseaudio: http://fpaste.org/paste/12770
Created attachment 345219 [details] lspci -vv
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This is also the case on a F11 Leonidas with all the updates. No sound from any application. lspci -vv 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) Subsystem: Dell Device 024f Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 21 Region 0: Memory at f6fdc000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: HDA Intel Kernel modules: snd-hda-intel
Todays update, on June 16, fixed the problem for me. There were some gstreamer updates which might have done it...
The updates did *NOT* fix my problems. Though I found out that if i play sound using directly the Alsa output(hw) I get sound working. The only catch is that it only plays 1 source at a time.
Ok. Got sound to work again. I had to install. alsa-driver-1.0.20 wget ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.20.tar.bz2 tar jxvf alsa-driver-1.0.20.tar.bz2 cd alsa-driver-1.0.20 ./configure --with-cards=hda-intel make -j 2 make install worked like a charm.
For those who don't want to deal with a compiler, the 1.0.20 alsa RPMS are in "testing". Those got my sound working again.
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. 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 '11'. 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 11'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 11 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 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.