group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #37903
[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 नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1703415
Title:
Bluetooth audio devices/profiles are missing after logging in from GDM
Status in gdm:
Unknown
Status in PulseAudio:
Unknown
Status in gdm3 package in Ubuntu:
Fix Released
Status in gdm3 package in Debian:
New
Bug description:
This is actually a PulseAudio bug, but the workaround is to disable
Bluetooth audio in GDM.
Further discussion (and the source of my understanding about this
issue) upstream are here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805414
To summarise:
GDM opens the A2DP profile for a11y purposes to allow screenreaders to
output over BT audio devices. However Pulse doesn't release those
devices when no audio is being played and the upshot is that once in
the users session A2DP is not available for any Bluetooth audio
devices, this means that you can only use the low quality profile
HSP/HFP.
There is a proposed workaround, but this means that a11y tools which
need to output audio won't be able to use Bluetooth devices within
GDM.
I think that for 17.10 shipping this work-around is acceptable, and we
should revisit in the 18.04 cycle to try and get a proper fix in PA.
The suggested PA bug is:
https://bugs.freedesktop.org/show_bug.cgi?id=57167
but that hasn't seen movement since 2012.
= The work around =
From the Debian wiki: https://wiki.debian.org/BluetoothUser/a2dp
Disable the Bluetooth sink in the GDM PA daemon.
Add this to /var/lib/gdm3/.config/pulse/default.pa
#!/usr/bin/pulseaudio -nF
#
# 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
I have tested this, and I can confirm that it allows access to A2DP
again in the user session.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1703415/+subscriptions