Debian Bug report logs - #805414
gdm3: disable pulseaudio to prevent capturing A2DP sink on session start

Reply or subscribe to this bug.

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Jérémy Lal <kapouer@melix.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: gdm3: disable pulseaudio to prevent capturing A2DP sink on session start

Date: Tue, 17 Nov 2015 23:03:10 +0100

Package: gdm3
Version: 3.18.0-2
Severity: normal

Dear Maintainer,

i'm using a typical gdm3 / gnome-shell 3.18 install and i connect
a bluetooth headset.
At some point in the past (maybe gnome < 3.18 i don't know exactly),
the headset was appearing in the output list of pulseaudio gnome
preferences. Now it never appears.

Reading https://wiki.debian.org/BluetoothUser/a2dp i applied the
"troubleshooting" section explaining how to prevent GDM from
capturing A2DP sink on session start. Now it works again.

So naturally i wonder why it isn't setup like this by default,
and why would one let gdm3 control sound devices.

Jérémy

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (670, 'unstable'), (650, 'testing'), (590, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.1.6 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gdm3 depends on:
ii  accountsservice                       0.6.40-3
ii  adduser                               3.113+nmu3
ii  dconf-cli                             0.24.0-2
ii  dconf-gsettings-backend               0.24.0-2
ii  debconf [debconf-2.0]                 1.5.58
ii  gir1.2-gdm3                           3.18.0-2
ii  gnome-session [x-session-manager]     3.18.1.2-1
ii  gnome-session-bin                     3.18.1.2-1
ii  gnome-settings-daemon                 3.18.2-1
ii  gnome-shell                           3.18.2-1
ii  gnome-terminal [x-terminal-emulator]  3.18.2-1
ii  gsettings-desktop-schemas             3.18.1-1
ii  libaccountsservice0                   0.6.40-3
ii  libaudit1                             1:2.4.4-4
ii  libc6                                 2.19-22
ii  libcanberra-gtk3-0                    0.30-2.1
ii  libcanberra0                          0.30-2.1
ii  libgdk-pixbuf2.0-0                    2.32.2-1
ii  libgdm1                               3.18.0-2
ii  libglib2.0-0                          2.46.2-1
ii  libglib2.0-bin                        2.46.2-1
ii  libgtk-3-0                            3.18.4-1
ii  libpam-modules                        1.1.8-3.1
ii  libpam-runtime                        1.1.8-3.1
ii  libpam-systemd                        227-3
ii  libpam0g                              1.1.8-3.1
ii  librsvg2-common                       2.40.11-1
ii  libselinux1                           2.3-2+b1
ii  libsystemd0                           227-3
ii  libwrap0                              7.6.q-25
ii  libx11-6                              2:1.6.3-1
ii  libxau6                               1:1.0.8-1
ii  libxdmcp6                             1:1.1.2-1
ii  lsb-base                              9.20150917
ii  metacity [x-window-manager]           1:3.18.1-1
ii  mutter [x-window-manager]             3.18.2-1
ii  policykit-1                           0.105-13
ii  ucf                                   3.0031
ii  x11-common                            1:7.7+12
ii  x11-xserver-utils                     7.7+5
ii  xterm [x-terminal-emulator]           320-1

Versions of packages gdm3 recommends:
ii  at-spi2-core               2.18.3-1
ii  desktop-base               8.0.2
ii  gnome-icon-theme           3.12.0-1
ii  gnome-icon-theme-symbolic  3.12.0-1
ii  x11-xkb-utils              7.7+2
ii  xserver-xephyr             2:1.17.3-2
ii  xserver-xorg               1:7.7+12
ii  zenity                     3.18.1.1-1

Versions of packages gdm3 suggests:
pn  gnome-orca            <none>
ii  libpam-gnome-keyring  3.18.2-1

-- debconf information:
* shared/default-x-display-manager: gdm3
  gdm3/daemon_name: /usr/sbin/gdm3

Message #10 received at 805414@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Jérémy Lal <kapouer@melix.org>, 805414@bugs.debian.org

Subject: Re: Bug#805414: gdm3: disable pulseaudio to prevent capturing A2DP sink on session start

Date: Tue, 17 Nov 2015 23:14:28 +0100

[Message part 1 (text/plain, inline)]

Am 17.11.2015 um 23:03 schrieb Jérémy Lal:
> Package: gdm3
> Version: 3.18.0-2
> Severity: normal
> 
> Dear Maintainer,
> 
> i'm using a typical gdm3 / gnome-shell 3.18 install and i connect
> a bluetooth headset.
> At some point in the past (maybe gnome < 3.18 i don't know exactly),
> the headset was appearing in the output list of pulseaudio gnome
> preferences. Now it never appears.
> 
> Reading https://wiki.debian.org/BluetoothUser/a2dp i applied the
> "troubleshooting" section explaining how to prevent GDM from
> capturing A2DP sink on session start. Now it works again.
> 
> So naturally i wonder why it isn't setup like this by default,
> and why would one let gdm3 control sound devices.
> 


We need pulseaudio in the gdm session for accessibility, e.g. the screen
reader requires it.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #15 received at 805414@bugs.debian.org (full text, mbox, reply):

From: Matthew Gabeler-Lee <cheetah@fastcat.org>

To: Debian Bug Tracking System <805414@bugs.debian.org>

Subject: Re: gdm3: disable pulseaudio to prevent capturing A2DP sink on session start

Date: Wed, 03 Aug 2016 21:38:44 -0400

Package: gdm3
Version: 3.20.1-1
Followup-For: Bug #805414

It seems like gdm3 should not be claiming the A2DP audio interface, or
really _any_ audio interface when it is not 'active' / visible.

It needs the keyboard to accept passwords, but it doesn't prevent me from
using my keyboard after I log in ;)

I realize the PA bits are going to be (much) more complicated than the
keyboard example, but the principle applies I think.

Being ignorant of PA, I'm also a bit confused as to why A2DP is special
here.  Other sound devices aren't broken by gdm3 wanting to have sound
services available for accessibility, why is A2DP different here?

Message #20 received at 805414@bugs.debian.org (full text, mbox, reply):

From: Olivier Berger <olivier.berger@telecom-sudparis.eu>

To: 805414@bugs.debian.org

Subject: Re: Bug#805414: gdm3: disable pulseaudio to prevent capturing A2DP sink on session start

Date: Tue, 20 Dec 2016 11:49:43 +0100

Hi.

On Wed, Aug 03, 2016 at 09:38:44PM -0400, Matthew Gabeler-Lee wrote:
> 
> It seems like gdm3 should not be claiming the A2DP audio interface, or
> really _any_ audio interface when it is not 'active' / visible.
> 

I've experienced this issue also on a friend's machine where a2dp wasn't available until we applied the workaround.

How do other distros manage that ?

Anyone caring ?

Thanks in advance.

Best regards,
-- 
Olivier BERGER 
http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8
Ingenieur Recherche - Dept INF
Institut Mines-Telecom, Telecom SudParis, Evry (France)

Message #25 received at 805414@bugs.debian.org (full text, mbox, reply):

From: Tuxicoman <debian@jesuislibre.net>

To: 805414@bugs.debian.org

Subject: Re: Bug#805414: gdm3: disable pulseaudio to prevent capturing A2DP sink on session start

Date: Wed, 19 Apr 2017 21:16:03 +0200

Everyone who want to send audio to an bluetooth receiver will face this
issue.

Can we at least include the workaround from the wiki https://wiki.debia
n.org/BluetoothUser/a2dp

In order to prevent GDM from capturing the A2DP sink on session start,
edit /var/lib/gdm3/.config/pulse/client.conf (or create it, if it
doesn't exist):

autospawn = no
daemon-binary = /bin/true

After that you have to grant access to this file to Debian-gdm user:

# chown Debian-gdm:Debian-gdm /var/lib/gdm3/.config/pulse/client.conf

Message #30 received at 805414@bugs.debian.org (full text, mbox, reply):

From: Aurelien Jacobs <aurel@gnuage.org>

To: Debian Bug Tracking System <805414@bugs.debian.org>

Subject: Re: gdm3: disable pulseaudio to prevent capturing A2DP sink on session start

Date: Sat, 24 Jun 2017 02:10:26 +0200

Package: gdm3
Version: 3.22.3-3
Followup-For: Bug #805414

The workaround from https://wiki.debian.org/BluetoothUser/a2dp used to
work, but starting with gdm3 3.22.3-2, it is not enough anymore.
I found out that I now need the following additional step to really
prevent gdm3 to start pulseaudio:

rm /var/lib/gdm3/.config/systemd/user/sockets.target.wants/pulseaudio.socket

This, along with the /var/lib/gdm3/.config/pulse/client.conf file, got
my bluetooth headset working again.

Message #35 received at 805414@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupre <anarcat@debian.org>

To: Aurelien Jacobs <aurel@gnuage.org>, 805414@bugs.debian.org

Subject: Re: Bug#805414: gdm3: disable pulseaudio to prevent capturing A2DP sink on session start

Date: Sat, 1 Jul 2017 19:26:36 -0400

[Message part 1 (text/plain, inline)]

On Sat, Jun 24, 2017 at 02:10:26AM +0200, Aurelien Jacobs wrote:
> Package: gdm3
> Version: 3.22.3-3
> Followup-For: Bug #805414
> 
> The workaround from https://wiki.debian.org/BluetoothUser/a2dp used to
> work, but starting with gdm3 3.22.3-2, it is not enough anymore.
> I found out that I now need the following additional step to really
> prevent gdm3 to start pulseaudio:
> 
> rm /var/lib/gdm3/.config/systemd/user/sockets.target.wants/pulseaudio.socket
> 
> This, along with the /var/lib/gdm3/.config/pulse/client.conf file, got
> my bluetooth headset working again.

Confirmed. Got the same thing here. This is the freshly released Debian
stretch and wasn't a problem when I was using lightdm.

I have edited the wiki to fix this workaround, but it seems to me
important to fix this in the long run.

Why does pulseaudio hold on to the device anyways? Shouldn't PA just go
away once the user is logged in in the first place? I understand the
reasoning behind GDM running PA on the login screen, but I fail to see
why it stays running afterwards.

With that logic, even regular "sound card" audio wouldn't work with that
setup. I guess the only reason that currently works (and may not be an
issue for most people) is because (1) most people don't have bluetooth
speakers (yet) and (2) this bug is bluetooth-specific.

If this was the case for ALSA, you would have a serious uproar and this
would be a RC bug which would have blocked stretch.

I think this should be fixed in a point release and it may be worth
bumping up the severity accordingly.

A.

-- 
Dr. King’s major assumption was that if you are nonviolent, if you
suffer, your opponent will see your suffering and will be moved to
change his heart. He only made one fallacious assumption: In order for
nonviolence to work, your opponent must have a conscience. The United
States has none.        - Stokely Carmichael

[signature.asc (application/pgp-signature, inline)]

Message #40 received at 805414@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Antoine Beaupre <anarcat@debian.org>, 805414@bugs.debian.org, Aurelien Jacobs <aurel@gnuage.org>

Subject: Re: Bug#805414: gdm3: disable pulseaudio to prevent capturing A2DP sink on session start

Date: Sun, 2 Jul 2017 02:21:13 +0200

[Message part 1 (text/plain, inline)]

Am 02.07.2017 um 01:26 schrieb Antoine Beaupre:

> I think this should be fixed in a point release and it may be worth
> bumping up the severity accordingly.

Sure, once there is a fix we can include it in a point release.
So far there is none afaics, or is there?
Has anyone who is affected by this and cares about it notified upstream?




-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #45 received at 805414@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Michael Biebl <biebl@debian.org>, 805414@bugs.debian.org, Aurelien Jacobs <aurel@gnuage.org>

Subject: Re: Bug#805414: gdm3: disable pulseaudio to prevent capturing A2DP sink on session start

Date: Sat, 01 Jul 2017 20:30:57 -0400

On 2017-07-02 02:21:13, Michael Biebl wrote:
> Am 02.07.2017 um 01:26 schrieb Antoine Beaupre:
>
>> I think this should be fixed in a point release and it may be worth
>> bumping up the severity accordingly.
>
> Sure, once there is a fix we can include it in a point release.

Great.

> So far there is none afaics, or is there?

I see workarounds that completely disable pulseaudio, but nothing that
clearly fixes the issue itself.

> Has anyone who is affected by this and cares about it notified upstream?

I'd be happy to - gnome is the upstream here?

Or do we treat this as a PA bug ("should release BT")?

A.

-- 
No animal has more liberty than the cat; but it buries the mess it
makes. The cat is the best anarchist. Until they learn that from the cat
I cannot respect them.
                        - For whom the bell tolls, Ernest Hemingway

Message #50 received at 805414@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Antoine Beaupré <anarcat@debian.org>, 805414@bugs.debian.org, Aurelien Jacobs <aurel@gnuage.org>

Subject: Re: Bug#805414: gdm3: disable pulseaudio to prevent capturing A2DP sink on session start

Date: Sun, 2 Jul 2017 02:38:33 +0200

[Message part 1 (text/plain, inline)]

Am 02.07.2017 um 02:30 schrieb Antoine Beaupré:
> Or do we treat this as a PA bug ("should release BT")?

I'm not sure, actually.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #55 received at 805414@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Antoine Beaupré <anarcat@debian.org>, 805414@bugs.debian.org, Aurelien Jacobs <aurel@gnuage.org>

Subject: Re: Bug#805414: gdm3: disable pulseaudio to prevent capturing A2DP sink on session start

Date: Sun, 2 Jul 2017 02:41:26 +0200

[Message part 1 (text/plain, inline)]

Am 02.07.2017 um 02:38 schrieb Michael Biebl:
> Am 02.07.2017 um 02:30 schrieb Antoine Beaupré:
>> Or do we treat this as a PA bug ("should release BT")?
> 
> I'm not sure, actually.


https://wiki.archlinux.org/index.php/Talk:Bluetooth_headset#GDMs_pulseaudio_instance_captures_bluetooth_headset

suggests that a custom PA config shipped by gdm could workaround this by
unloading the bluetooth module.

That feels a bit like a hack though.
The real issue is probably that PA doesn't release the BT device.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #60 received at 805414@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Michael Biebl <biebl@debian.org>, 805414@bugs.debian.org, Aurelien Jacobs <aurel@gnuage.org>

Subject: Re: Bug#805414: gdm3: disable pulseaudio to prevent capturing A2DP sink on session start

Date: Sun, 02 Jul 2017 17:11:21 -0400

On 2017-07-02 02:41:26, Michael Biebl wrote:
> Am 02.07.2017 um 02:38 schrieb Michael Biebl:
>> Am 02.07.2017 um 02:30 schrieb Antoine Beaupré:
>>> Or do we treat this as a PA bug ("should release BT")?
>> 
>> I'm not sure, actually.
>
>
> https://wiki.archlinux.org/index.php/Talk:Bluetooth_headset#GDMs_pulseaudio_instance_captures_bluetooth_headset
>
> suggests that a custom PA config shipped by gdm could workaround this by
> unloading the bluetooth module.
>
> That feels a bit like a hack though.
> The real issue is probably that PA doesn't release the BT device.

So I have found this is already reported in the PA bugtracker in #845938
(merged with #848130) - let's treat this separately.

There's a workaround for GDM: disable bluetooth support as documented in
the Arch wiki. We could patch the gdm3 pacakge to do exactly that while
PA fixes its stuff.

The rationale behind disabling BT support there is that there's zero UI
in GDM3 to pair devices. Until those exists, it's meaningless to have BT
support at the login prompt: it will never work, short of the user
switching to a VT and hacking commands by hand, at which point all bets
are off and we can assume the user will figure out a way.

Therefore I would argue we can have a workaround here, in the gdm3
package, for now.

I'll trickle up the PA bugs on the side as well.

Sounds good?

A.

-- 
We must learn to live together as brothers or perish together as fools.
                        - Martin Luther King, Jr.

Message #65 received at 805414@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Antoine Beaupré <anarcat@debian.org>, 805414@bugs.debian.org, Aurelien Jacobs <aurel@gnuage.org>, Felipe Sateler <fsateler@debian.org>

Subject: Re: Bug#805414: gdm3: disable pulseaudio to prevent capturing A2DP sink on session start

Date: Sun, 2 Jul 2017 23:16:19 +0200

[Message part 1 (text/plain, inline)]

Am 02.07.2017 um 23:11 schrieb Antoine Beaupré:
> On 2017-07-02 02:41:26, Michael Biebl wrote:
>> Am 02.07.2017 um 02:38 schrieb Michael Biebl:
>>> Am 02.07.2017 um 02:30 schrieb Antoine Beaupré:
>>>> Or do we treat this as a PA bug ("should release BT")?
>>>
>>> I'm not sure, actually.
>>
>>
>> https://wiki.archlinux.org/index.php/Talk:Bluetooth_headset#GDMs_pulseaudio_instance_captures_bluetooth_headset
>>
>> suggests that a custom PA config shipped by gdm could workaround this by
>> unloading the bluetooth module.
>>
>> That feels a bit like a hack though.
>> The real issue is probably that PA doesn't release the BT device.
> 
> So I have found this is already reported in the PA bugtracker in #845938
> (merged with #848130) - let's treat this separately.
> 
> There's a workaround for GDM: disable bluetooth support as documented in
> the Arch wiki. We could patch the gdm3 pacakge to do exactly that while
> PA fixes its stuff.
> 
> The rationale behind disabling BT support there is that there's zero UI
> in GDM3 to pair devices. Until those exists, it's meaningless to have BT
> support at the login prompt: it will never work, short of the user
> switching to a VT and hacking commands by hand, at which point all bets
> are off and we can assume the user will figure out a way.
> 
> Therefore I would argue we can have a workaround here, in the gdm3
> package, for now.

Have you tested the workaround from the arch wiki and can you confirm it
works?

Felipe, would appreciate your input on this. Do you think disabling
bluetooth support in the gdm PA instance is a proper fix or are the
side-effects which we need to be aware of?

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #70 received at 805414@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Michael Biebl <biebl@debian.org>, 805414@bugs.debian.org, Aurelien Jacobs <aurel@gnuage.org>, Felipe Sateler <fsateler@debian.org>

Subject: Re: Bug#805414: gdm3: disable pulseaudio to prevent capturing A2DP sink on session start

Date: Sun, 02 Jul 2017 17:36:07 -0400

On 2017-07-02 23:16:19, Michael Biebl wrote:
> Am 02.07.2017 um 23:11 schrieb Antoine Beaupré:
>> On 2017-07-02 02:41:26, Michael Biebl wrote:
>>> Am 02.07.2017 um 02:38 schrieb Michael Biebl:
>>>> Am 02.07.2017 um 02:30 schrieb Antoine Beaupré:
>>>>> Or do we treat this as a PA bug ("should release BT")?
>>>>
>>>> I'm not sure, actually.
>>>
>>>
>>> https://wiki.archlinux.org/index.php/Talk:Bluetooth_headset#GDMs_pulseaudio_instance_captures_bluetooth_headset
>>>
>>> suggests that a custom PA config shipped by gdm could workaround this by
>>> unloading the bluetooth module.
>>>
>>> That feels a bit like a hack though.
>>> The real issue is probably that PA doesn't release the BT device.
>> 
>> So I have found this is already reported in the PA bugtracker in #845938
>> (merged with #848130) - let's treat this separately.
>> 
>> There's a workaround for GDM: disable bluetooth support as documented in
>> the Arch wiki. We could patch the gdm3 pacakge to do exactly that while
>> PA fixes its stuff.
>> 
>> The rationale behind disabling BT support there is that there's zero UI
>> in GDM3 to pair devices. Until those exists, it's meaningless to have BT
>> support at the login prompt: it will never work, short of the user
>> switching to a VT and hacking commands by hand, at which point all bets
>> are off and we can assume the user will figure out a way.
>> 
>> Therefore I would argue we can have a workaround here, in the gdm3
>> package, for now.
>
> Have you tested the workaround from the arch wiki and can you confirm it
> works?

I cannot, unfortunately, test this anymore, as I have disabled the
pulseaudio socket as directed earlier, with:

rm /var/lib/gdm3/.config/systemd/user/sockets.target.wants/pulseaudio.socket

I don't know what that was pointing to, so I can't quite restore that
behavior directly.

A.

-- 
Imagination is more important than knowledge.
Knowledge is limited.
Imagination encircles the world.
                        - Albert Einstein

Message #75 received at 805414@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Antoine Beaupré <anarcat@debian.org>, 805414@bugs.debian.org, Aurelien Jacobs <aurel@gnuage.org>, Felipe Sateler <fsateler@debian.org>

Subject: Re: Bug#805414: gdm3: disable pulseaudio to prevent capturing A2DP sink on session start

Date: Sun, 2 Jul 2017 23:43:55 +0200

[Message part 1 (text/plain, inline)]

Am 02.07.2017 um 23:36 schrieb Antoine Beaupré:
> On 2017-07-02 23:16:19, Michael Biebl wrote:

>> Have you tested the workaround from the arch wiki and can you confirm it
>> works?
> 
> I cannot, unfortunately, test this anymore, as I have disabled the
> pulseaudio socket as directed earlier, with:
> 
> rm /var/lib/gdm3/.config/systemd/user/sockets.target.wants/pulseaudio.socket
> 
> I don't know what that was pointing to, so I can't quite restore that
> behavior directly.

That's from the postinst:

UNIT=/usr/lib/systemd/user/pulseaudio.socket
USERUNITDIR=/var/lib/gdm3/.config/systemd/user
if ! [ -L $USERUNITDIR/sockets.target.wants/pulseaudio.socket ]; then
  mkdir -p $USERUNITDIR/sockets.target.wants
  ln -sf $UNIT $USERUNITDIR/sockets.target.wants
fi

You can run that manually or simply re-install the gdm3 package so that
code is run again.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #80 received at 805414@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Michael Biebl <biebl@debian.org>, 805414@bugs.debian.org, Aurelien Jacobs <aurel@gnuage.org>, Felipe Sateler <fsateler@debian.org>

Subject: Re: Bug#805414: gdm3: disable pulseaudio to prevent capturing A2DP sink on session start

Date: Sun, 02 Jul 2017 18:05:09 -0400

On 2017-07-02 23:43:55, Michael Biebl wrote:
> Am 02.07.2017 um 23:36 schrieb Antoine Beaupré:
>> On 2017-07-02 23:16:19, Michael Biebl wrote:
>
>>> Have you tested the workaround from the arch wiki and can you confirm it
>>> works?
>> 
>> I cannot, unfortunately, test this anymore, as I have disabled the
>> pulseaudio socket as directed earlier, with:
>> 
>> rm /var/lib/gdm3/.config/systemd/user/sockets.target.wants/pulseaudio.socket
>> 
>> I don't know what that was pointing to, so I can't quite restore that
>> behavior directly.
>
> That's from the postinst:
>
> UNIT=/usr/lib/systemd/user/pulseaudio.socket
> USERUNITDIR=/var/lib/gdm3/.config/systemd/user
> if ! [ -L $USERUNITDIR/sockets.target.wants/pulseaudio.socket ]; then
>   mkdir -p $USERUNITDIR/sockets.target.wants
>   ln -sf $UNIT $USERUNITDIR/sockets.target.wants
> fi
>
> You can run that manually or simply re-install the gdm3 package so that
> code is run again.

Thanks! I believe I have rolled back the workarounds and implemented the
fix default.pa documented in the Arch wiki. Everything seems to work
normally now, ie. I can correctly connect through A2DP to my bluetooth
speaker.

(I have a different speaker than yesterday, mind you, but I am assuming
the problem is consistent across devices.)

A.

-- 
The Net treats censorship as damage and routes around it.
                         - John Gilmore

Message #85 received at 805414@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Antoine Beaupré <anarcat@debian.org>, 805414@bugs.debian.org, Aurelien Jacobs <aurel@gnuage.org>, Felipe Sateler <fsateler@debian.org>

Subject: Re: Bug#805414: gdm3: disable pulseaudio to prevent capturing A2DP sink on session start

Date: Mon, 3 Jul 2017 15:46:20 +0200

[Message part 1 (text/plain, inline)]

Am 03.07.2017 um 00:05 schrieb Antoine Beaupré:
> On 2017-07-02 23:43:55, Michael Biebl wrote:
>> Am 02.07.2017 um 23:36 schrieb Antoine Beaupré:
>>> On 2017-07-02 23:16:19, Michael Biebl wrote:
>>
>>>> Have you tested the workaround from the arch wiki and can you confirm it
>>>> works?
>>>
>>> I cannot, unfortunately, test this anymore, as I have disabled the
>>> pulseaudio socket as directed earlier, with:
>>>
>>> rm /var/lib/gdm3/.config/systemd/user/sockets.target.wants/pulseaudio.socket
>>>
>>> I don't know what that was pointing to, so I can't quite restore that
>>> behavior directly.
>>
>> That's from the postinst:
>>
>> UNIT=/usr/lib/systemd/user/pulseaudio.socket
>> USERUNITDIR=/var/lib/gdm3/.config/systemd/user
>> if ! [ -L $USERUNITDIR/sockets.target.wants/pulseaudio.socket ]; then
>>   mkdir -p $USERUNITDIR/sockets.target.wants
>>   ln -sf $UNIT $USERUNITDIR/sockets.target.wants
>> fi
>>
>> You can run that manually or simply re-install the gdm3 package so that
>> code is run again.
> 
> Thanks! I believe I have rolled back the workarounds and implemented the
> fix default.pa documented in the Arch wiki. Everything seems to work
> normally now, ie. I can correctly connect through A2DP to my bluetooth
> speaker.

Since concerns were raised that this might break existing a11y setups, I
don't plan to make an upload with this change.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #90 received at 805414@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Michael Biebl <biebl@debian.org>, 805414@bugs.debian.org, Aurelien Jacobs <aurel@gnuage.org>, Felipe Sateler <fsateler@debian.org>

Subject: Re: Bug#805414: gdm3: disable pulseaudio to prevent capturing A2DP sink on session start

Date: Mon, 03 Jul 2017 10:20:16 -0400

On 2017-07-03 15:46:20, Michael Biebl wrote:
> Am 03.07.2017 um 00:05 schrieb Antoine Beaupré:
>> On 2017-07-02 23:43:55, Michael Biebl wrote:
>>> Am 02.07.2017 um 23:36 schrieb Antoine Beaupré:
>>>> On 2017-07-02 23:16:19, Michael Biebl wrote:
>>>
>>>>> Have you tested the workaround from the arch wiki and can you confirm it
>>>>> works?
>>>>
>>>> I cannot, unfortunately, test this anymore, as I have disabled the
>>>> pulseaudio socket as directed earlier, with:
>>>>
>>>> rm /var/lib/gdm3/.config/systemd/user/sockets.target.wants/pulseaudio.socket
>>>>
>>>> I don't know what that was pointing to, so I can't quite restore that
>>>> behavior directly.
>>>
>>> That's from the postinst:
>>>
>>> UNIT=/usr/lib/systemd/user/pulseaudio.socket
>>> USERUNITDIR=/var/lib/gdm3/.config/systemd/user
>>> if ! [ -L $USERUNITDIR/sockets.target.wants/pulseaudio.socket ]; then
>>>   mkdir -p $USERUNITDIR/sockets.target.wants
>>>   ln -sf $UNIT $USERUNITDIR/sockets.target.wants
>>> fi
>>>
>>> You can run that manually or simply re-install the gdm3 package so that
>>> code is run again.
>> 
>> Thanks! I believe I have rolled back the workarounds and implemented the
>> fix default.pa documented in the Arch wiki. Everything seems to work
>> normally now, ie. I can correctly connect through A2DP to my bluetooth
>> speaker.
>
> Since concerns were raised that this might break existing a11y setups, I
> don't plan to make an upload with this change.

I don't understand the impact this could have regarding
accessibility. There are, as far as I know, currently no usable way to
have bluetooth audio working at all in the gdm3 login prompt, because
there's no way to associate a device, so there's no loss of
functionality here. But there *is* a loss of functionality for
everyone (*including* screen reader users) *after* the user is logged
in: they cannot correctly configure bluetooth devices!

Can we get a better idea of the use case you are worried about here?

To be really clear here, the change I am proposing is the one documented
in the Arch wiki and now also in the Debian wiki:

https://wiki.debian.org/BluetoothUser/a2dp#Workaround_2:_disable_pulseaudio.27s_bluetooth_in_gdm

which currently consists of adding the following
/var/lib/gdm3/.config/pulse/default.pa file:

#!/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

How would this break accessibility?

Thanks,

A.

-- 
Thoughtcrime does not entail death: thoughtcrime IS death.
                        - Winston Smith, 1984

Message #95 received at 805414@bugs.debian.org (full text, mbox, reply):

From: Felipe Sateler <fsateler@debian.org>

To: Antoine Beaupré <anarcat@debian.org>, debian-accessibility@lists.debian.org

Cc: Michael Biebl <biebl@debian.org>, 805414@bugs.debian.org, Aurelien Jacobs <aurel@gnuage.org>

Subject: Re: Bug#805414: gdm3: disable pulseaudio to prevent capturing A2DP sink on session start

Date: Mon, 3 Jul 2017 10:27:36 -0400

[Message part 1 (text/plain, inline)]

Adding the a11y list to CC.

Dear a11y team, a short summary for you: Currently, pulseaudio does not
negotiate bluetooth devices the same way it does with alsa devices, with a
result that is undesirable: if the gdm login screen grabs the BT device, it
becomes unavailable in the logged in session. The change being discussed
here is to disable bluetooth in the gdm login screen.

On Mon, Jul 3, 2017 at 10:20 AM, Antoine Beaupré <anarcat@debian.org> wrote:

> On 2017-07-03 15:46:20, Michael Biebl wrote:
> > Am 03.07.2017 um 00:05 schrieb Antoine Beaupré:
> >> On 2017-07-02 23:43:55, Michael Biebl wrote:
> >>> Am 02.07.2017 um 23:36 schrieb Antoine Beaupré:
> >>>> On 2017-07-02 23:16:19, Michael Biebl wrote:
> >>>
> >>>>> Have you tested the workaround from the arch wiki and can you
> confirm it
> >>>>> works?
> >>>>
> >>>> I cannot, unfortunately, test this anymore, as I have disabled the
> >>>> pulseaudio socket as directed earlier, with:
> >>>>
> >>>> rm /var/lib/gdm3/.config/systemd/user/sockets.target.wants/
> pulseaudio.socket
> >>>>
> >>>> I don't know what that was pointing to, so I can't quite restore that
> >>>> behavior directly.
> >>>
> >>> That's from the postinst:
> >>>
> >>> UNIT=/usr/lib/systemd/user/pulseaudio.socket
> >>> USERUNITDIR=/var/lib/gdm3/.config/systemd/user
> >>> if ! [ -L $USERUNITDIR/sockets.target.wants/pulseaudio.socket ]; then
> >>>   mkdir -p $USERUNITDIR/sockets.target.wants
> >>>   ln -sf $UNIT $USERUNITDIR/sockets.target.wants
> >>> fi
> >>>
> >>> You can run that manually or simply re-install the gdm3 package so that
> >>> code is run again.
> >>
> >> Thanks! I believe I have rolled back the workarounds and implemented the
> >> fix default.pa documented in the Arch wiki. Everything seems to work
> >> normally now, ie. I can correctly connect through A2DP to my bluetooth
> >> speaker.
> >
> > Since concerns were raised that this might break existing a11y setups, I
> > don't plan to make an upload with this change.
>
> I don't understand the impact this could have regarding
> accessibility. There are, as far as I know, currently no usable way to
> have bluetooth audio working at all in the gdm3 login prompt, because
> there's no way to associate a device, so there's no loss of
> functionality here. But there *is* a loss of functionality for
> everyone (*including* screen reader users) *after* the user is logged
> in: they cannot correctly configure bluetooth devices!
>

Bluetooth pairings are global. Once you configured them in your user
session, they will become available to gdm too.


>
> Can we get a better idea of the use case you are worried about here?
>

Here is where the input of the a11y team would be very appreciated. Is
disabling bluetooth in the login screen likely to cause problem?


>
> To be really clear here, the change I am proposing is the one documented
> in the Arch wiki and now also in the Debian wiki:
>
> https://wiki.debian.org/BluetoothUser/a2dp#Workaround_
> 2:_disable_pulseaudio.27s_bluetooth_in_gdm
>
> which currently consists of adding the following
> /var/lib/gdm3/.config/pulse/default.pa file:
>
> #!/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
>
> How would this break accessibility?
>

My own thought is that if your only speakers are BT, how are you going to
have the screen read if there is no BT?

-- 

Saludos,
Felipe Sateler

[Message part 2 (text/html, inline)]

Message #100 received at 805414@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Jude DaShiell <jdashiel@panix.com>, Felipe Sateler <fsateler@debian.org>, debian-accessibility@lists.debian.org

Cc: Michael Biebl <biebl@debian.org>, 805414@bugs.debian.org, Aurelien Jacobs <aurel@gnuage.org>

Subject: Re: Bug#805414: gdm3: disable pulseaudio to prevent capturing A2DP sink on session start

Date: Mon, 03 Jul 2017 11:24:25 -0400

On 2017-07-03 11:10:37, Jude DaShiell wrote:
> What happens to someone who only has a bluetooth keyboard and has a 
> bluetooth dongle connected to their computer to use bluetooth 
> temporarily since their usb keyboard broke?

I do not believe the proposed workaround disables bluetooth
altogether. It just disables bluetooth *audio*.

A.

-- 
We won't have a society if we destroy the environment.
                        - Margaret Mead

Message #105 received at 805414@bugs.debian.org (full text, mbox, reply):

From: Jude DaShiell <jdashiel@panix.com>

To: Felipe Sateler <fsateler@debian.org>, Antoine Beaupré <anarcat@debian.org>, debian-accessibility@lists.debian.org

Cc: Michael Biebl <biebl@debian.org>, 805414@bugs.debian.org, Aurelien Jacobs <aurel@gnuage.org>

Subject: Re: Bug#805414: gdm3: disable pulseaudio to prevent capturing A2DP sink on session start

Date: Mon, 3 Jul 2017 11:10:37 -0400 (EDT)

What happens to someone who only has a bluetooth keyboard and has a 
bluetooth dongle connected to their computer to use bluetooth 
temporarily since their usb keyboard broke?

On Mon, 3 Jul 2017, Felipe Sateler wrote:

> Date: Mon, 3 Jul 2017 10:27:36
> From: Felipe Sateler <fsateler@debian.org>
> To: Antoine Beaupr? <anarcat@debian.org>,
>     debian-accessibility@lists.debian.org
> Cc: Michael Biebl <biebl@debian.org>, 805414@bugs.debian.org,
>     Aurelien Jacobs <aurel@gnuage.org>
> Subject: Re: Bug#805414: gdm3: disable pulseaudio to prevent capturing A2DP
>     sink on session start
> Resent-Date: Mon,  3 Jul 2017 14:28:34 +0000 (UTC)
> Resent-From: debian-accessibility@lists.debian.org
> 
> Adding the a11y list to CC.
>
> Dear a11y team, a short summary for you: Currently, pulseaudio does not
> negotiate bluetooth devices the same way it does with alsa devices, with a
> result that is undesirable: if the gdm login screen grabs the BT device, it
> becomes unavailable in the logged in session. The change being discussed
> here is to disable bluetooth in the gdm login screen.
>
> On Mon, Jul 3, 2017 at 10:20 AM, Antoine Beaupr? <anarcat@debian.org> wrote:
>
>> On 2017-07-03 15:46:20, Michael Biebl wrote:
>>> Am 03.07.2017 um 00:05 schrieb Antoine Beaupr?:
>>>> On 2017-07-02 23:43:55, Michael Biebl wrote:
>>>>> Am 02.07.2017 um 23:36 schrieb Antoine Beaupr?:
>>>>>> On 2017-07-02 23:16:19, Michael Biebl wrote:
>>>>>
>>>>>>> Have you tested the workaround from the arch wiki and can you
>> confirm it
>>>>>>> works?
>>>>>>
>>>>>> I cannot, unfortunately, test this anymore, as I have disabled the
>>>>>> pulseaudio socket as directed earlier, with:
>>>>>>
>>>>>> rm /var/lib/gdm3/.config/systemd/user/sockets.target.wants/
>> pulseaudio.socket
>>>>>>
>>>>>> I don't know what that was pointing to, so I can't quite restore that
>>>>>> behavior directly.
>>>>>
>>>>> That's from the postinst:
>>>>>
>>>>> UNIT=/usr/lib/systemd/user/pulseaudio.socket
>>>>> USERUNITDIR=/var/lib/gdm3/.config/systemd/user
>>>>> if ! [ -L $USERUNITDIR/sockets.target.wants/pulseaudio.socket ]; then
>>>>>   mkdir -p $USERUNITDIR/sockets.target.wants
>>>>>   ln -sf $UNIT $USERUNITDIR/sockets.target.wants
>>>>> fi
>>>>>
>>>>> You can run that manually or simply re-install the gdm3 package so that
>>>>> code is run again.
>>>>
>>>> Thanks! I believe I have rolled back the workarounds and implemented the
>>>> fix default.pa documented in the Arch wiki. Everything seems to work
>>>> normally now, ie. I can correctly connect through A2DP to my bluetooth
>>>> speaker.
>>>
>>> Since concerns were raised that this might break existing a11y setups, I
>>> don't plan to make an upload with this change.
>>
>> I don't understand the impact this could have regarding
>> accessibility. There are, as far as I know, currently no usable way to
>> have bluetooth audio working at all in the gdm3 login prompt, because
>> there's no way to associate a device, so there's no loss of
>> functionality here. But there *is* a loss of functionality for
>> everyone (*including* screen reader users) *after* the user is logged
>> in: they cannot correctly configure bluetooth devices!
>>
>
> Bluetooth pairings are global. Once you configured them in your user
> session, they will become available to gdm too.
>
>
>>
>> Can we get a better idea of the use case you are worried about here?
>>
>
> Here is where the input of the a11y team would be very appreciated. Is
> disabling bluetooth in the login screen likely to cause problem?
>
>
>>
>> To be really clear here, the change I am proposing is the one documented
>> in the Arch wiki and now also in the Debian wiki:
>>
>> https://wiki.debian.org/BluetoothUser/a2dp#Workaround_
>> 2:_disable_pulseaudio.27s_bluetooth_in_gdm
>>
>> which currently consists of adding the following
>> /var/lib/gdm3/.config/pulse/default.pa file:
>>
>> #!/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
>>
>> How would this break accessibility?
>>
>
> My own thought is that if your only speakers are BT, how are you going to
> have the screen read if there is no BT?
>
>

-- 

Message #112 received at 805414@bugs.debian.org (full text, mbox, reply):

From: Tino Mettler <tino@tikei.de>

To: Jude DaShiell <jdashiel@panix.com>

Cc: Felipe Sateler <fsateler@debian.org>, Antoine Beaupré <anarcat@debian.org>, debian-accessibility@lists.debian.org, Michael Biebl <biebl@debian.org>, 805414@bugs.debian.org, Aurelien Jacobs <aurel@gnuage.org>

Subject: Re: Bug#805414: gdm3: disable pulseaudio to prevent capturing A2DP sink on session start

Date: Thu, 7 Dec 2017 14:38:56 +0100

On Mon, Jul 03, 2017 at 11:10:37 -0400, Jude DaShiell wrote:
> What happens to someone who only has a bluetooth keyboard and has a
> bluetooth dongle connected to their computer to use bluetooth temporarily
> since their usb keyboard broke?

Hi,

if this is related to "disable bluetooth in the gdm login screen": this
was meant in the pulseaudio context, where bluetooth audio would be
disabled in the pulseaudio config which is used by gdm. Therefore,
input devices like mice and keyboards won't be affected.

Regards,
Tino

Message #117 received at 805414@bugs.debian.org (full text, mbox, reply):

From: Matthias Urlichs <matthias@urlichs.de>

To: 805414@bugs.debian.org

Subject: An alternate workaround

Date: Tue, 6 Feb 2018 08:07:25 +0100

is to bite the bullet and run pulseaudio as a system-wide service. Yes I
know this is not "recommended" but, to be blunt, IMHO that
recommendation is bollocks.

No more fighting about which PA daemon gets a device, and you can
actually use mpd without impacting your regular audio output.

-- 
-- Matthias Urlichs

Message #122 received at 805414@bugs.debian.org (full text, mbox, reply):

From: Arnaud Rebillout <arnaud.rebillout@collabora.com>

To: 805414@bugs.debian.org

Subject: Re: Bug#805414: gdm3: disable pulseaudio to prevent capturing A2DP sink on session start

Date: Sun, 13 Jan 2019 13:25:43 +0700

Just an update on this bug, as it is in Debian unstable.

I noticed that the bug can't be reproduced on a GNOME/Wayland session. I
can see in the logs that the PA GDM daemon gets killed with SIGTERM. I
don't know enough about Wayland to tell you what happens there. I'm just
surprised because I *think* I bumped into this bug at a time where I was
running GNOME/Wayland, so I'm not sure if there was a change in Wayland,
or if I'm mistaken.

In any case, for those running GNOME/X11, the bug is still there and can
be reproduced.

(choosing between Wayland/X11 is done by editing the file
/etc/gdm3/daemon.conf)

There's an effort to solve that upstream at
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/merge_requests/10,
I just pushed an updated version of a patch.

Thanks,

  Arnaud

Send a report that this bug log contains spam.