** Description changed: This is a meta-bug for the following problem: PulseAudio does not update the volume at ALSA level. You can verify this by running alsamixer and see that the volumes do not change in the expected way. This can happen in the following cases: - * You switch ports (e g unplugging headphones, but speakers remain silent), and there is no information in the module-device-restore database - * The PulseAudio volume before and after switching port is on the exact same level - * You increase the volume while the actual sink/source is closed. + * You switch ports (e g unplugging headphones, but speakers remain silent), and there is no information in the module-device-restore database + * The PulseAudio volume before and after switching port is on the exact same level + * You increase the volume while the actual sink/source is closed. SRU Justification: [Impact] This seems to be a quite common problem. Result is usability problem and confused users as the volume appears to be correct, but is not. [Development fix] Fixed by patches 0106 and 0017 in lp:~ubuntu-audio- dev/pulseaudio/ubuntu.precise [Stable fix] Fixed by patches 0106 and 0017 in lp:~ubuntu-audio- dev/pulseaudio/ubuntu.oneiric + + [Test case] + + 1) First, make sure you're on a system with jack detection working and that you have ALSA sliders for "headphone" and "speaker". + 2) Make sure you don't have .pulse directory, either by booting a live-CD, or by + switching to a VT, log in as the same user as you're currently logged in to in X, execute "pulseaudio -k", "rm -rf ~/.pulse" (will remove your pulseaudio settings so you might want to back it up instead). + 3) In the GUI, open sound settings to make sure pulseaudio is started. Plug in headphones and notice that the "speaker" slider is now muted in alsamixer. Close alsamixer and unplug headphones. Reopen alsamixer. + 4) If the bug is present, "speaker" is still at its lowest level, if the bug is fixed, "speaker" has returned to a normal level. + + [Regression potential] + + * The 0106 patch is quite obvious, and has already been accepted upstream. + * The 0017 patch is less obvious but I've tested it here and had a good look through the code and I'm quite sure it would not cause regressions. Such regressions would theoretically be the wrong volume being set.
** Description changed: This is a meta-bug for the following problem: - PulseAudio does not update the volume at ALSA level. You can verify this - by running alsamixer and see that the volumes do not change in the + PulseAudio 1.0 does not update the volume at ALSA level. You can verify + this by running alsamixer and see that the volumes do not change in the expected way. This can happen in the following cases: * You switch ports (e g unplugging headphones, but speakers remain silent), and there is no information in the module-device-restore database * The PulseAudio volume before and after switching port is on the exact same level * You increase the volume while the actual sink/source is closed. SRU Justification: [Impact] This seems to be a quite common problem. Result is usability problem and confused users as the volume appears to be correct, but is not. [Development fix] Fixed by patches 0106 and 0017 in lp:~ubuntu-audio- dev/pulseaudio/ubuntu.precise [Stable fix] Fixed by patches 0106 and 0017 in lp:~ubuntu-audio- dev/pulseaudio/ubuntu.oneiric [Test case] 1) First, make sure you're on a system with jack detection working and that you have ALSA sliders for "headphone" and "speaker". - 2) Make sure you don't have .pulse directory, either by booting a live-CD, or by - switching to a VT, log in as the same user as you're currently logged in to in X, execute "pulseaudio -k", "rm -rf ~/.pulse" (will remove your pulseaudio settings so you might want to back it up instead). - 3) In the GUI, open sound settings to make sure pulseaudio is started. Plug in headphones and notice that the "speaker" slider is now muted in alsamixer. Close alsamixer and unplug headphones. Reopen alsamixer. + 2) Make sure you don't have .pulse directory, either by booting a live-CD, or by + switching to a VT, log in as the same user as you're currently logged in to in X, execute "pulseaudio -k", "rm -rf ~/.pulse" (will remove your pulseaudio settings so you might want to back it up instead). + 3) In the GUI, open sound settings to make sure pulseaudio is started. Plug in headphones and notice that the "speaker" slider is now muted in alsamixer. Close alsamixer and unplug headphones. Reopen alsamixer. 4) If the bug is present, "speaker" is still at its lowest level, if the bug is fixed, "speaker" has returned to a normal level. [Regression potential] * The 0106 patch is quite obvious, and has already been accepted upstream. * The 0017 patch is less obvious but I've tested it here and had a good look through the code and I'm quite sure it would not cause regressions. Such regressions would theoretically be the wrong volume being set. ** Description changed: This is a meta-bug for the following problem: PulseAudio 1.0 does not update the volume at ALSA level. You can verify this by running alsamixer and see that the volumes do not change in the expected way. This can happen in the following cases: * You switch ports (e g unplugging headphones, but speakers remain silent), and there is no information in the module-device-restore database * The PulseAudio volume before and after switching port is on the exact same level * You increase the volume while the actual sink/source is closed. SRU Justification: [Impact] This seems to be a quite common problem. Result is usability problem and confused users as the volume appears to be correct, but is not. [Development fix] Fixed by patches 0106 and 0017 in lp:~ubuntu-audio- dev/pulseaudio/ubuntu.precise [Stable fix] Fixed by patches 0106 and 0017 in lp:~ubuntu-audio- dev/pulseaudio/ubuntu.oneiric [Test case] 1) First, make sure you're on a system with jack detection working and that you have ALSA sliders for "headphone" and "speaker". 2) Make sure you don't have .pulse directory, either by booting a live-CD, or by switching to a VT, log in as the same user as you're currently logged in to in X, execute "pulseaudio -k", "rm -rf ~/.pulse" (will remove your pulseaudio settings so you might want to back it up instead). 3) In the GUI, open sound settings to make sure pulseaudio is started. Plug in headphones and notice that the "speaker" slider is now muted in alsamixer. Close alsamixer and unplug headphones. Reopen alsamixer. 4) If the bug is present, "speaker" is still at its lowest level, if the bug is fixed, "speaker" has returned to a normal level. [Regression potential] * The 0106 patch is quite obvious, and has already been accepted upstream. - * The 0017 patch is less obvious but I've tested it here and had a good look through the code and I'm quite sure it would not cause regressions. Such regressions would theoretically be the wrong volume being set. + * The 0017 patch is less obvious but I've tested it here and had a good look through the code and I'm quite sure it would not cause regressions. Such regressions would theoretically be the wrong volume being set, or that underlying bugs would make the wrong volume better than the right volume. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/877954 Title: Oneiric regression: Pulseaudio sometimes forgets to set ALSA volumes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/877954/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
