I think you might have two different bugs... A2DP failing to appear in the list or refusing to set is a longstanding problem that has occurred well before the introduction of gdm. It's one of the things we tried to fix in xenial recently but I know it can still occur sometimes even in artful.
How I experience this bug however is that the Bluetooth device is shown as connected but upon login there is no corresponding audio device. -- 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: Disable Bluetooth sink in GDM to allow A2DP in the user session To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1703415/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
