On Thu, 2009-12-24 at 02:04 +0100, Ludovico Cavedon wrote: > Hi, > I found the cause of the issue. This is what happens of first boot/login > (i.e., when there is no ~/.pulse directory). > > * boot: > /etc/init.d/alsa-utils start # set volume to default levels > * login: > pulseaudio --start # keep current volume (no saved one available) > * logout: > #pulseaudio keeps running!! > * reboot > /etc/init.d/alsa-utils stop # save current volume and mute mixer > kill pulseudio # save current volume (oops, mixer is mute!) > > > Second boot/login: > * boot: > /etc/init.d/alsa-utils start # set volume to saved one (good!) > * login: > pulseaudio --start # restore volume to saved one (oops, muted!) > > Note that alsa and pulseaudio store volume separately. > > I am attaching an easy proof-of-concept fix: prevent alsa-utils from > zeroing the mixer. It work for me. > > But I would not blame alsa for doing that. I'd rather think that we > should ensure that pulseaudio gets stopped before "alsa-utils stop" is > called or when the user is logged out. > > Thanks, > Ludovico >
Works for me as well. I appreciate your work Ludovico. Thanks, Nathan A. Stine -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
