Description of problem: Pulseaudio seems to work fine, but no audio is played. Sound hardware works fine, I can even hear slight sound cracks on system logon (when pulseaudio initializes I guess). Sound codecs are fine. But dragging volume and mute/unmunte gives no effect. Version-Release number of selected component (if applicable): Name : pulseaudio Arch : i386 Version : 0.9.13 Release : 7.fc11 Additional info: There is one issue a can blame though. Since update from Fedora 9 to Fedora 10 beta, Pulseaudio volume control *always* started as muted on first logon. I had to unmute it manually. I guess previous behavior affects the new volume control applet but I have no clue how to fix it.
Have you played around with the mixer on the sound card? THis sounds like a mixer misinitialization issue. Try "alsamixer -c0" and play around with the controls.
I tried alsamixergui - I played with controls but it didn't help. I would like to supply any additional information but I've got no clue what should I look at.
What sound card is this? Can you play audio when you bypass PA? i.e. does "aplay -D plughw:0 < /dev/urandom" work?
Sound card: 00:1e.2 Multimedia audio controller: Intel Corporation 82801G (ICH7 Family) AC'97 Audio Controller (rev 01) aplay says: [root@digger sk]# aplay -D plughw:0 < /dev/urandom Playing raw data 'stdin' : Unsigned 8 bit, Rate 8000 Hz, Mono and waits until I break it - no sound is heard. I played around with Pulseaudio Manager devices and their volume controls - so not volume control applet is not muted on gnome start up, but I've got no sound either. These are the contents of /var/log/messages from last logon: Jan 8 22:24:29 digger pulseaudio[4422]: main.c: Called SUID root and real-time/high-priority scheduling was requested in the configuration. However, we lack the necessary privileges: Jan 8 22:24:29 digger pulseaudio[4422]: main.c: We are not in group 'pulse-rt' and PolicyKit refuse to grant us privileges. Dropping SUID again. Jan 8 22:24:29 digger pulseaudio[4422]: main.c: For enabling real-time scheduling please acquire the appropriate PolicyKit privileges, or become a member of 'pulse-rt', or increase the RLIMIT_NICE/RLIMIT_RTPRIO resource limits for this user. Jan 8 22:24:29 digger pulseaudio[4422]: main.c: High-priority scheduling enabled in configuration but not allowed by policy. Jan 8 22:24:29 digger pulseaudio[4422]: core-util.c: setpriority(): Отказано в доступе Jan 8 22:24:29 digger pulseaudio[4422]: ltdl-bind-now.c: Failed to find original dlopen loader. Jan 8 22:24:29 digger pulseaudio[4425]: pid.c: Stale PID file, overwriting. Jan 8 22:24:30 digger pulseaudio[4425]: alsa-util.c: Device front:0 doesn't support 44100 Hz, changed to 48000 Hz. Jan 8 22:24:30 digger pulseaudio[4425]: alsa-util.c: Device front:0 doesn't support 44100 Hz, changed to 48000 Hz. Jan 8 22:24:39 digger pulseaudio[4474]: main.c: Called SUID root and real-time/high-priority scheduling was requested in the configuration. However, we lack the necessary privileges: Jan 8 22:24:39 digger pulseaudio[4474]: main.c: We are not in group 'pulse-rt' and PolicyKit refuse to grant us privileges. Dropping SUID again. Jan 8 22:24:39 digger pulseaudio[4474]: main.c: For enabling real-time scheduling please acquire the appropriate PolicyKit privileges, or become a member of 'pulse-rt', or increase the RLIMIT_NICE/RLIMIT_RTPRIO resource limits for this user. Jan 8 22:24:39 digger pulseaudio[4474]: main.c: High-priority scheduling enabled in configuration but not allowed by policy. Jan 8 22:24:39 digger pulseaudio[4474]: core-util.c: setpriority(): Отказано в доступе Jan 8 22:24:39 digger pulseaudio[4474]: ltdl-bind-now.c: Failed to find original dlopen loader. Jan 8 22:24:39 digger pulseaudio[4480]: pid.c: Daemon already running.
Kernel: Linux digger 2.6.28-3.fc11.i686 #1 SMP Fri Dec 26 08:07:00 EST 2008 i686 i686 i386 GNU/Linux
If aplay doesn't work either, then this is most likely a mixer issue. Also it is not PA related but an ALSA issue. Reassigning to the kernel.
Sergey, it would be good if you could follow these suggestions: http://forums.fedoraforum.org/showpost.php?p=1206905&postcount=14
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 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.