[pulseaudio-discuss] pulseaudio-0.9.21, alsa-1.0.23, kde-4.4.5, consolekit, dbus

[Colin Guthrie]

'Twas brillig, and sibu xolo at 22/09/10 02:04 did gyre and gimble:
> iii---I  I recompiled  kdemultimedia also.  On  restart I obtained sound on 
> the   second login but none subsequenty and cdrom sound  is practicly mute   ~ 
> a tenth as loud as  a hungry mosquito.

FWIW, unless you are wroking on new features, I'd recommend using the
"stable-queue" branch upstream rather than master. It's effectively
0.9.21 with ~180 odd fixes on top. I'm hoping to release this as 0.9.22
pretty soon.

Anyway, if the volume changes, it's typically due to some client
changing it.

In the case of logins this can be a bit confusing. Typically your user's
PA daemon will ignore any volume changes when it is "suspended" but it
will not actually restore them when it is unsuspended (I think, I need
to double check this).

Changes are what happens is this:
 1. You log in and startup a PA process.
 2. You log out, but your PA daemon sticks around for some time.
 3. KDM or something similar sets the volume either by running it's own
PA or via alsa etc. doesn't really matter.
 4. You log in again, before your PA process has died. We look at the
system volume and see it is lower than before and adjust ourselves to fit.

Ironically, I believe if you wait long enough before logging back in,
your PA process will die and when you login it will be restarted and
will ultimately restore the volume properly.

I *think* that's what's going on, but not 100% sure.

Col



-- 

Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
  Mageia Contributor [http://www.mageia.org/]
  PulseAudio Hacker [http://www.pulseaudio.org/]
  Trac Hacker [http://trac.edgewall.org/]