Ticket #663 (closed defect: fixed)

Opened 2 years ago

Last modified 2 years ago

remember the settings of the last used audio devices

Reported by: kiddo Owned by: lennart
Milestone: Component: daemon
Keywords: Cc:

Description

Upstream GNOME (https://bugzilla.gnome.org/show_bug.cgi?id=592833) said this was a pulseaudio bug.

Let's take the use case of laptops, usb sound cards or usb headsets/mics. These can be hotplugged anytime with pulseaudio.

However, gnome-volume-control in Ubuntu Karmic (which currently has pulseaudio 0.9.18) doesn't seem to remember their settings, or even which one was set as the true default. Plug a usb mic, change its volume and unplug/replug, its volume will be reset.

Attachments

pacmd-ls.txt (23.0 kB) - added by kiddo 2 years ago.
output of pacmd ls

Change History

Changed 2 years ago by lennart

Uh, that works perfectly fine here. Maybe this is a Ubuntu-specific bug?

Changed 2 years ago by kiddo

Demonstration of the problem under ubuntu's current dev release: http://launchpadlibrarian.net/32678042/volume%20levels%20reset.ogv

Output of pulseaudio -vvv: http://launchpadlibrarian.net/32678086/pulseaudio.log

Changed 2 years ago by kiddo

Ah, and I filed it in the Ubuntu bug tracker too (but no reply on that side yet): https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/427520

Changed 2 years ago by kiddo

Oh, I have to mention, this affects pavucontrol in the same way as depicted with gnome-volume-control

Changed 2 years ago by lennart

Please reproduce this and then attach the output of "pacmd ls" here!

Changed 2 years ago by kiddo

output of pacmd ls

Changed 2 years ago by kiddo

In what context must I execute "pacmd ls" (I mean, what do you mean by "please reproduce this"; is there a particular time I must run "pacmd ls"?)

Anyway, I just ran it after the "bunch of plugging/unplugging operations", with the mic currently plugged in, and attached it to this ticket.

Changed 2 years ago by lennart

Hmm, module-device-restore seems to be loaded properly. Not sure what is going on here.

Changed 2 years ago by lennart

Hmm, in your -vvvv output there's this line:

module-device-restore.c: Restoring volume for source alsa_input.usb-AKM_AK5370-00.analog-mono.

THis suggests that volume save/restore works properly. Not sure what is going on on.

Hmm, could you please try this: plug in the hw, change the volume to some level, then wait for 20s, then unplug, then replug. Is the volume restored then?

Currently we only save the volume state to disks after 10s passed. So maybe this is the simple explanation for this problem.

Changed 2 years ago by kiddo

Nope, I had suspected that, but I just did the following:

- plug the mic, raise its volume - wait 54 seconds, unplug - wait 25 seconds, replug

Problem is still there: on replug, the mic volume is reset to the low end.

Changed 2 years ago by kiddo

Just a thought, have you tested on Ubuntu's current dev release (I'm assuming you're probably on Fedora), maybe in a virtual machine or live CD?

Changed 2 years ago by kiddo

  • status changed from new to closed
  • resolution set to fixed

For some reason, the pulseaudio 0.9.19 package updates in Ubuntu today fixes the problem. Yay!

Note: See TracTickets for help on using tickets.