[Bug 1703415] Re: Bluetooth audio devices/profiles are missing after logging in from GDM
** Changed in: pulseaudio Status: Unknown => New ** Changed in: gdm Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1703415 Title: Bluetooth audio devices/profiles are missing after logging in from GDM To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1703415/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1703415] Re: Bluetooth audio devices/profiles are missing after logging in from GDM
Oops. It appears this was fixed in gdm3 in 2017. If you have any more problems then please open new bugs. ** Tags added: a2dp ** No longer affects: gdm3 (Ubuntu Zesty) ** No longer affects: pulseaudio (Ubuntu Zesty) ** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #323 https://gitlab.gnome.org/GNOME/gdm/-/issues/323 ** Changed in: gdm Importance: Medium => Unknown ** Changed in: gdm Status: Expired => Unknown ** Changed in: gdm Remote watch: GNOME Bug Tracker #784856 => gitlab.gnome.org/GNOME/gdm/-/issues #323 ** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #340 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/340 ** Changed in: pulseaudio Importance: Medium => Unknown ** Changed in: pulseaudio Remote watch: freedesktop.org Bugzilla #57167 => gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #340 ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** No longer affects: bluez (Ubuntu Xenial) ** No longer affects: gdm3 (Ubuntu Xenial) ** No longer affects: pulseaudio (Ubuntu Xenial) ** Changed in: bluez (Ubuntu) Status: New => Confirmed ** No longer affects: bluez (Ubuntu) ** No longer affects: pulseaudio (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1703415 Title: Bluetooth audio devices/profiles are missing after logging in from GDM To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1703415/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1703415] Re: Bluetooth audio devices/profiles are missing after logging in from GDM
Hello, I'm landing here after tracking a bug : I could not output sound to my SRS-XB22 bluetooth speaker. I had in logs : `src/service.c:btd_service_connect() a2dp-sink profile connect failed for F8:DF:15:7F:ED:AA: Protocol not available` I found a workaround here https://askubuntu.com/questions/1172000/a2dp-sink-profile-connect-failed ``` $ pactl load-module module-bluetooth-policy $ pactl load-module module-bluetooth-discover ``` I did not understand why these commands were mandatory as I already have them in `/etc/pulse/default.pa` Then I checked my `~/.config/pulse/default.pa` and found this : ``` #!/usr/bin/pulseaudio -nF # # Work around for PA not allowing access to A2DP profiles in the user session # because GDM already has it open. # LP: #1703415 # load system wide configuration .include /etc/pulse/default.pa ### unload driver modules for Bluetooth hardware .ifexists module-bluetooth-policy.so unload-module module-bluetooth-policy .endif .ifexists module-bluetooth-discover.so unload-module module-bluetooth-discover .endif ``` So here, we are : today, with - Ubuntu 20.10 - Pulseaudio 1:13.99.2-1ubuntu2.1 - BlueZ 5.55-0ubuntu1.1 => I do not reproduce the original bug. => Moreover, the now unnecessary workaround in `~/.config/pulse/default.pa` is preventing normal use for bluetooth devices. **Workaround for the workaround** : comment the lines in `~/.config/pulse/default.pa` ``` #!/usr/bin/pulseaudio -nF # # Work around for PA not allowing access to A2DP profiles in the user session # because GDM already has it open. # LP: #1703415 # load system wide configuration .include /etc/pulse/default.pa ### unload driver modules for Bluetooth hardware #.ifexists module-bluetooth-policy.so # unload-module module-bluetooth-policy #.endif # #.ifexists module-bluetooth-discover.so # unload-module module-bluetooth-discover #.endif ``` -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1703415 Title: Bluetooth audio devices/profiles are missing after logging in from GDM To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1703415/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1703415] Re: Bluetooth audio devices/profiles are missing after logging in from GDM
Launchpad has imported 3 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=57167. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2012-11-15T19:31:15+00:00 Tanu Kaskinen wrote: In module-bluetooth-device.c in filter_cb() there's this piece of code: if (acquire) if (bt_transport_acquire(u, FALSE) >= 0) { if (u->source) pa_source_suspend(u->source, FALSE, PA_SUSPEND_IDLE|PA_SUSPEND_USER); if (u->sink) pa_sink_suspend(u->sink, FALSE, PA_SUSPEND_IDLE|PA_SUSPEND_USER); } The acquire variable is set to true if the bluetooth audio state changed to "playing". This can happen without pulseaudio requesting it, so if we want to have strict equivalence "sink/source suspended" == "audio state is 'playing'" (and I think we want that), then it makes sense that module-bluetooth-device unsuspends the sink/source. The problem here is that there's no clean "force unsuspend" mechanism in pulseaudio. pa_sink_suspend(u->sink, FALSE, PA_SUSPEND_IDLE|PA_SUSPEND_USER) may not actually unsuspend the sink, because there are also other suspend reasons than just IDLE and USER. So, depending on the situation, the sink may or may not get unsuspended. module-bluetooth-device could list all possible reasons in the pa_sink_suspend() call, but that would be ugly. When adding new suspend reasons, it would be very easy to forget to update the pa_sink_suspend() call in module-bluetooth-device, and besides, if those suspend reasons are originally set by some other code, the original reasons to suspend don't really disappear when module-bluetooth-device unsuspends the sink, the old reasons are just overridden. I think there should be a function for forcing unsuspending. The semantics would be such that the sink gets unsuspended regardless of any standing suspend reasons, but all standing suspend reasons would be remembered, and once a new suspend request would be made, the forced unsuspend would cease to have effect, the sink would suspend and things would return to normal. A related thing is that I would like to replace the single suspend reason bitfield in pa_sink with an individual suspend request object for each suspend request. The single suspend reason bitfield is prone to conflicts if multiple places use the same reason (for example, module- bluetooth-device uses the USER reason which is also used for other purposes). Reply at: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1703415/comments/0 On 2012-11-15T20:44:28+00:00 Tanu Kaskinen wrote: (In reply to comment #0) > The problem here is that > there's no clean "force unsuspend" mechanism in pulseaudio. > pa_sink_suspend(u->sink, FALSE, PA_SUSPEND_IDLE|PA_SUSPEND_USER) may not > actually unsuspend the sink, because there are also other suspend reasons > than just IDLE and USER. So, depending on the situation, the sink may or may > not get unsuspended. > > module-bluetooth-device could list all possible reasons in the > pa_sink_suspend() call, but that would be ugly. When adding new suspend > reasons, it would be very easy to forget to update the pa_sink_suspend() > call in module-bluetooth-device, and besides, if those suspend reasons are > originally set by some other code, the original reasons to suspend don't > really disappear when module-bluetooth-device unsuspends the sink, the old > reasons are just overridden. Correction: there is the PA_SUSPEND_ALL suspend cause. That looks like a good simple solution to this bug, even though it doesn't solve all the described problems. But at least it will reliably unsuspend the sink. Reply at: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1703415/comments/1 On 2018-07-30T10:19:12+00:00 Gitlab-migration wrote: -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org'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.freedesktop.org/pulseaudio/pulseaudio/issues/340. Reply at: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1703415/comments/16 ** Changed in: pulseaudio Status: Confirmed => Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1703415 Title: Bluetooth audio devices/profiles are missing after logging in from GDM To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1703415/+subscriptions -- deskto
[Bug 1703415] Re: Bluetooth audio devices/profiles are missing after logging in from GDM
** Changed in: gdm Status: Confirmed => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1703415 Title: Bluetooth audio devices/profiles are missing after logging in from GDM To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1703415/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1703415] Re: Bluetooth audio devices/profiles are missing after logging in from GDM
I can confirm this one on (X)ubuntu 14.04.5 LTS with XFCE 4.10 desktop. The suggested fixes work for me aswell. Another problem appears when bluetooth is disabled on boot (which I always do because of paranoia ;)). Both Pulseaudio modules won't get loaded by my XFCE autostart script. I have to run it again after bluetooth is enabled manually. Then my JBL Flip 3 speaker appers instantly in the Pulseaudio settings besides the onboard sound device. Everything else works like a charm. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1703415 Title: Bluetooth audio devices/profiles are missing after logging in from GDM To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1703415/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1703415] Re: Bluetooth audio devices/profiles are missing after logging in from GDM
This bug was fixed in the package gdm3 - 3.24.2-1ubuntu9 --- gdm3 (3.24.2-1ubuntu9) artful; urgency=medium * debian/default.pa - Added new file to disable Bluetooth audio devices in PulseAudio from gdm3. (LP: #1703415) (LP: #1489651) * debian/gdm3.install - Added details of the default.pa file * debian/gdm3.postinst - Added installation of default.pa and creation of dir if it doesn't exist. -- Will Cooke Thu, 13 Jul 2017 12:14:34 +0100 ** Changed in: gdm3 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1703415 Title: Bluetooth audio devices/profiles are missing after logging in from GDM To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1703415/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1703415] Re: Bluetooth audio devices/profiles are missing after logging in from GDM
** Also affects: pulseaudio (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu Xenial) Importance: Undecided => High ** Changed in: gdm3 (Ubuntu Xenial) Status: New => Triaged ** Changed in: gdm3 (Ubuntu Zesty) Importance: Undecided => High ** Changed in: gdm3 (Ubuntu Zesty) Status: New => Triaged ** Changed in: pulseaudio (Ubuntu Xenial) Importance: Undecided => High ** Changed in: pulseaudio (Ubuntu Xenial) Status: New => Triaged ** Changed in: pulseaudio (Ubuntu Zesty) Importance: Undecided => High ** Changed in: pulseaudio (Ubuntu Zesty) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1703415 Title: Bluetooth audio devices/profiles are missing after logging in from GDM To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1703415/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1703415] Re: Bluetooth audio devices/profiles are missing after logging in from GDM
** Changed in: gdm3 (Ubuntu) Assignee: (unassigned) => Will Cooke (willcooke) ** Changed in: gdm3 (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1703415 Title: Bluetooth audio devices/profiles are missing after logging in from GDM To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1703415/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1703415] Re: Bluetooth audio devices/profiles are missing after logging in from GDM
** Changed in: pulseaudio (Ubuntu) Importance: Undecided => High ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Triaged ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1703415 Title: Bluetooth audio devices/profiles are missing after logging in from GDM To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1703415/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1703415] Re: Bluetooth audio devices/profiles are missing after logging in from GDM
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1703415 Title: Bluetooth audio devices/profiles are missing after logging in from GDM To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1703415/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1703415] Re: Bluetooth audio devices/profiles are missing after logging in from GDM
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1703415 Title: Bluetooth audio devices/profiles are missing after logging in from GDM To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1703415/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1703415] Re: Bluetooth audio devices/profiles are missing after logging in from GDM
** Summary changed: - Disable Bluetooth sink in GDM to allow A2DP in the user session + Bluetooth audio devices/profiles are missing after logging in from GDM -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1703415 Title: Bluetooth audio devices/profiles are missing after logging in from GDM To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1703415/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs