GNOME Bugzilla – Bug 784856
login screen's pulseaudio blocks bluetooth use in the user session after login
Last modified: 2018-05-24 11:37:48 UTC
When using gdm as a login manager it's not possible to use an a2dp bluetooth audio profile in the session because the login screen pulseaudio instance is creating a conflict that has been reported in various distributions, unsure why it was not upstreamed et https://bugzilla.redhat.com/show_bug.cgi?id=1356136 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805414 https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1703415 some distribution even documented a gdm workaround in their wiki https://wiki.archlinux.org/index.php/Bluetooth_headset#Gnome_with_GDM https://wiki.debian.org/BluetoothUser/a2dp#Workaround_ extract from the debian recommended change "Workaround 1: disable pulseaudio in gdm In order to prevent GDM from capturing the A2DP sink on session start, edit /var/lib/gdm3/.config/pulse/client.conf (or create it, if it doesn't exist): autospawn = no daemon-binary = /bin/true" The issue is also known by upstream pulseaudio, it's mentioned for example in https://bugs.freedesktop.org/show_bug.cgi?id=73325#c56. The right place to fix it might be pulseaudio but things are not been moving on that front and users keep hitting those problems so maybe gdm could workaround the issue in some way? (not enabling pulseaudio bluetooth on the login screen, stopping its pulseaudio server when starting the session, ...)?
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gdm/issues/323.