This patch set went into PulseAudio 4.0, which is now in Saucy.
** Changed in: pulseaudio (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1076947
Just committed upstream in PulseAudio git repository.
** Changed in: pulseaudio (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1076947
Title:
Patches posted upstream:
http://lists.freedesktop.org/archives/pulseaudio-discuss/2013-April/016957.html
** Changed in: pulseaudio (Ubuntu)
Status: Triaged = In Progress
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned) = David Henningsson (diwic)
--
You received this bug
I was asked to come up with a hacky workaround, so here it is:
Add a file /usr/bin/unmute-sink, and make sure it's executable, with
this contents:
#!/bin/sh
pactl set-sink-mute 0 0
(You might need to change the first 0 to 1, or use the sink name, if you
have more than one sound card)
Add a
I haven't taken a closer look yet, but I suspect that the case is that
1) when the first user plugs in headphones, the alsa kcontrol Speaker is muted
2) the guest account pulseaudio starts up, without any settings stored
3) the alsa card is loaded and the initial mixer settings are picked up from
