On Fri 09 Mar 2012 11:45 +0000, Tom Gundersen wrote:
On Fri, Mar 9, 2012 at 10:27 AM, XeCycle <xecycle@gmail.com> wrote:
I use pulseaudio on my laptop. I start it by `start-pulseaudio-x11` in something like .xinitrc (I use a standalone wm with lxdm). When I resume from pm-suspend, the system beeper issues several beeps; when I open a urxvt, a bash completion failure will issue a beep too. However when any program that talks to pulseaudio starts (or try again to talk to it), e.g. start pavucontrol, everything is normal again.
My guess is that what happens is that pulseaudio blocks the sound device, and that's the reason you don't hear the beep when it is running (i.e. when sounds play). Disabling PA as Ralf suggests would in this case not help at all, and likely just make it worse (I wish people would stop suggesting to disable PA regardless of what the problem is, in most cases this is not going to make things easier).
I'm confused. Why is pulseaudio so necessary? I just use alsa for sound and have no problems whatsoever. Granted, I don't use one of them fancy shmancy desktop environments.