** 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
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1703415
Title:
Bluetooth audio devices/profiles are missing after logging in from GDM
Status in gdm:
Confirmed
Status in PulseAudio:
Confirmed
Status in gdm3 package in Ubuntu:
Fix Committed
Status in pulseaudio package in Ubuntu:
Triaged
Status in gdm3 source package in Xenial:
Triaged
Status in pulseaudio source package in Xenial:
Triaged
Status in gdm3 source package in Zesty:
Triaged
Status in pulseaudio source package in Zesty:
Triaged
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
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
