GNOME Bugzilla – Bug 662382
Wrong output selected after connecting to A2DP device
Last modified: 2021-06-09 16:30:23 UTC
I have a Bluetooth A2DP device (Logitech) that I use to stream sound from my Laptop to my HiFi system. After resuming my laptop, I go to the bluetooth panel of g-c-c and enable to connection to the device. Thereafter, sound is directly streamed to the A2DP device. However, when I press the volume keys, it is the volume for the disabled, internal speakers, which is changed. Also, in the sound panel of g-c-c, under output, is is the internal speakers which are selected. I have to select the A2DP device in the sound panel before the volume slider is associated with the correct device. The proper behaviour should be that upon connecting to the device, the output is correctly set and the volume slider associated with the right device.
Mass reassign, sorry for the noise.
Bump, should be an easy fix and would improve usability considerably.
(In reply to comment #2) > Bump, should be an easy fix and would improve usability considerably. This isn't a forum, and please don't comment on the "easiness" of patches unless you're willing to provide them.
*** Bug 741994 has been marked as a duplicate of this bug. ***
*** Bug 744347 has been marked as a duplicate of this bug. ***
This bug is still present in version 3.21.90 Since it isn't mentioned here – as a workaround you can load a pulseaudio module by adding this to /etc/pulse/default.pa: load-module module-switch-on-connect
I'm experiencing a similar issue. I have a speaker plugged into the headphone socket ("Headphones - Built-in Audio"). I then plug an USB headset ("Speakers - LifeChat LX-3000 Headset") and audio is automatically routed to it. However, the volume control in GNOME 3.24.3 continues controlling the old device. I then go to Settings / Sound and "Headphones - Built-in Audio" is still selected. I select the USB headset (audio continues playing normally) and now I can adjust the volume (both in the Sound setting and in the volume applet). alsa-plugins-pulseaudio-1.1.4-1.fc26.x86_64 gnome-shell-3.24.3-1.fc26.x86_64 gnome-settings-daemon-3.24.3-2.fc26.x86_64 gsound-1.0.2-3.fc26.x86_64 jack-audio-connection-kit-1.9.10-8.fc26.x86_64 portaudio-19-24.fc26.x86_64 pulseaudio-10.0-4.fc26.x86_64 pulseaudio-gdm-hooks-10.0-4.fc26.x86_64 pulseaudio-libs-10.0-4.fc26.x86_64 pulseaudio-libs-glib2-10.0-4.fc26.x86_64 pulseaudio-module-bluetooth-10.0-4.fc26.x86_64 pulseaudio-module-x11-10.0-4.fc26.x86_64 pulseaudio-utils-10.0-4.fc26.x86_64
I can't reproduce this bug for some time now. Several months ago I wanted to see if I can still reproduce it, so I commented out 'load-module module-switch-on-connect' in /etc/pulse/default.pa I wanted to test it for some days but then I forgot about it – it just worked (for several months now).
Sorry, I should add that I use Debian Testing, so now that's gnome-control-center 3.30.3.
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new bug report at https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/ Thank you for your understanding and your help.