GNOME Bugzilla – Bug 749208
No more pulseaudio output to bluetooth speaker if pulseaudio is started by gdm
Last modified: 2017-10-31 17:00:52 UTC
Issue : https://bbs.archlinux.org/viewtopic.php?id=196689 How to fix it : http://www.debuntu.org/how-to-disable-pulseaudio-and-sound-in-gdm/ Distribution : ArchLinux
Hi, I also have what I believe is this issue, however with me it was the pairing of my bluetooth headphones, not a speaker. However, I believe both are caused by the same thing. It seems that the pulse audio module: module-bluetooth-discover works only if started after the X11 session is up. Perhaps the changes to gdm running on Wayland natively, or some other issue, has caused this command to never successfully run? Further, I have come accross a workaround for the time being: Edit the file: /etc/pulse/default.pa and comment out (with an # at the beginning of the line) the following line: #load-module module-bluetooth-discover now edit the file: /usr/bin/start-pulseaudio-x11 and after the lines: if [ x”$SESSION_MANAGER” != x ] ; then /usr/bin/pactl load-module module-x11-xsmp “display=$DISPLAY session_manager=$SESSION_MANAGER” > /dev/null fi add the following line: /usr/bin/pactl load-module module-bluetooth-discover This way the Pulse audio’s Bluetooth modules will not be downloaded at boot time but after x11 is started. I have a thread on the Archlinux forums here: https://bbs.archlinux.org/viewtopic.php?id=197482 and I reported this issue to pulseaudio, so they can know about it here: https://bugs.freedesktop.org/show_bug.cgi?id=90490
I believe bug 748654 is the same issue as this one.
The issue is that gdm is alway active on tty1 now when loading GNOME... And when connecting bluetooth, gdm pulseaudio get the device, not use one... Will give a look at work on my Fedora where bug doesn't exist.
Any chance of this getting looked at for 3.18? The workaround of loading module-bluetooth-discover after X11 has already started is working for the time being, but it was a chore to figure out that fix, and it might turn a lot of people off from Gnome/Linux as a viable option for Bluetooth audio.
This is still an issue on 3.18
(In reply to Cédric Bellegarde from comment #3) > The issue is that gdm is alway active on tty1 now when loading GNOME... > > And when connecting bluetooth, gdm pulseaudio get the device, not use one... Hm... if so, that means this has probably always been broken in the case of user switching. (If not, how is this handled for user switching?) I'm not sure this can be fixed properly in gdm (a proper fix would take into account user switching). Also not sure what the best component to assign this to would be. I will pick gnome-bluetooth; I doubt there is anything wrong in gnome-bluetooth, but that seems like the best place for further triage....
I was affected by this issue on Debian testing and used the workaround linked in the original report for some months. However now I realized that I can't reproduce this bug anymore – sorry, I have no idea when, where and how it was fixed.
Sorry, please just ignore my last comment. I enabled auto-login for my user in Gnome and didn't need the mentioned workaround. When I disable auto- login I can still reproduce this bug.
I can confirm this issue is still present in GNOME 3.26 https://wiki.archlinux.org/index.php/Bluetooth_headset#Gnome_with_GDM
This is a problem with pulseaudio I'm afraid, nothing that gnome-bluetooth can do about. We only ever use PulseAudio in the gdm session as way to display the Bluetooth icon in gnome-shell if there's a Bluetooth device connected, such as a keyboard, or a mouse. PulseAudio's bug tracker is at: https://bugs.freedesktop.org/