[Touch-packages] [Bug 1962542] Re: [jammy] Bluetooth headphones unable to connect after suspend in BlueZ 5.63

2022-03-07 Thread Luis Alberto Pabón
Thank you, I was plagued by this issue on my Bose NC700 cans. In my case
bluetoothd isn't crashing btw.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962542

Title:
  [jammy] Bluetooth headphones unable to connect after suspend in BlueZ
  5.63

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Bose quietcomfort 35 is a common headset that can no longer connect to
  a jammy system after just one suspend. This started at the end of
  January but just now really debugging the issue.

  Side note that my bluetooth mouse works fine without problem after any
  amount of suspends.

  The headset is only trying to connect to the jammy system (no other
  bluetooth devices it's paired with has active bluetooth, to isolate
  only the jammy <-> headset issue). This is jammy running on a T590, up
  to date, not proposed.

  heather@fenrir:~$ dpkg -l | grep bluetooth
  ii  gir1.2-gnomebluetooth-1.0:amd643.34.5-4   
amd64Introspection data for GnomeBluetooth
  ii  gnome-bluetooth3.34.5-4   
amd64GNOME Bluetooth tools
  ii  libbluetooth-dev:amd64 5.63-0ubuntu1  
amd64Development files for using the BlueZ Linux Bluetooth 
library
  ii  libbluetooth3:amd645.63-0ubuntu1  
amd64Library to use the BlueZ Linux Bluetooth stack
  ii  libgnome-bluetooth13:amd64 3.34.5-4   
amd64GNOME Bluetooth tools - support library
  ii  pulseaudio-module-bluetooth1:15.99.1+dfsg1-1ubuntu1   
amd64Bluetooth module for PulseAudio sound server

  On a fresh boot (not suspended yet), I can connect the headset
  successfully. Here are the logs of that:

  Mar 01 09:44:02 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as 
/devices/virtual/input/input30
  Mar 01 09:44:02 fenrir systemd-logind[1570]: Watching system buttons on 
/dev/input/event22 (Bose QuietComfort 35 (AVRCP))
  Mar 01 09:44:03 fenrir NetworkManager[1536]:   [1646124243.8660] 
platform-linux: do-add-ip6-address[3: fe80::c1bc:a705:9e66:e0d0]: failure 13 
(Permission denied)
  Mar 01 09:44:04 fenrir bluetoothd[1532]: 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0: fd(32) ready
  Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 6 threads of 3 
processes of 1 users.
  Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Successfully made thread 5660 of 
process 2708 owned by '1000' RT at priority 5.
  Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 7 threads of 3 
processes of 1 users.
  Mar 01 09:44:04 fenrir pulseaudio[2708]: org.freedesktop.DBus.Properties.Get 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0 Volume failed: 
org.freedesktop.DBus.Error.InvalidArgs: No such property 'Volume'
  Mar 01 09:44:04 fenrir pulseaudio[2708]: Battery Level: 70%
  Mar 01 09:44:04 fenrir pulseaudio[2708]: Dock Status: undocked

  But then if I close the laptop lid and reopen, login, and try to
  connect the headset the device is found invalid with the following
  logs:

  Mar 01 00:47:08 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as 
/devices/virtual/input/input152
  Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:08 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:08 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:08 fenrir systemd-logind[1545]: Watching system buttons on 
/dev/input/event19 (Bose QuietComfort 35 (AVRCP))
  Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:09 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:09 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:09 fenrir pulseaudio[253956]: Device doesn't exist for 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F
  Mar 01 00:47:09 fenrir bluetoothd[40741]: src/profile.c:new_conn_reply() 
Hands-Free Voice gateway replied with an error: 
org.bluez.Error.InvalidArguments, Unable to handle new connection
  Mar 01 00:47:09 fenrir pulseaudio[253956]: Device doesn't exist f

[Touch-packages] [Bug 1962542] Re: [jammy] Bluetooth headphones unable to connect after suspend in BlueZ 5.63

2022-03-03 Thread Heather Ellsworth
I just tested this version on jammy and my headset now will reconnect
after a suspend without problems. Thanks so much for cherry-picking
those patches!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962542

Title:
  [jammy] Bluetooth headphones unable to connect after suspend in BlueZ
  5.63

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Bose quietcomfort 35 is a common headset that can no longer connect to
  a jammy system after just one suspend. This started at the end of
  January but just now really debugging the issue.

  Side note that my bluetooth mouse works fine without problem after any
  amount of suspends.

  The headset is only trying to connect to the jammy system (no other
  bluetooth devices it's paired with has active bluetooth, to isolate
  only the jammy <-> headset issue). This is jammy running on a T590, up
  to date, not proposed.

  heather@fenrir:~$ dpkg -l | grep bluetooth
  ii  gir1.2-gnomebluetooth-1.0:amd643.34.5-4   
amd64Introspection data for GnomeBluetooth
  ii  gnome-bluetooth3.34.5-4   
amd64GNOME Bluetooth tools
  ii  libbluetooth-dev:amd64 5.63-0ubuntu1  
amd64Development files for using the BlueZ Linux Bluetooth 
library
  ii  libbluetooth3:amd645.63-0ubuntu1  
amd64Library to use the BlueZ Linux Bluetooth stack
  ii  libgnome-bluetooth13:amd64 3.34.5-4   
amd64GNOME Bluetooth tools - support library
  ii  pulseaudio-module-bluetooth1:15.99.1+dfsg1-1ubuntu1   
amd64Bluetooth module for PulseAudio sound server

  On a fresh boot (not suspended yet), I can connect the headset
  successfully. Here are the logs of that:

  Mar 01 09:44:02 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as 
/devices/virtual/input/input30
  Mar 01 09:44:02 fenrir systemd-logind[1570]: Watching system buttons on 
/dev/input/event22 (Bose QuietComfort 35 (AVRCP))
  Mar 01 09:44:03 fenrir NetworkManager[1536]:   [1646124243.8660] 
platform-linux: do-add-ip6-address[3: fe80::c1bc:a705:9e66:e0d0]: failure 13 
(Permission denied)
  Mar 01 09:44:04 fenrir bluetoothd[1532]: 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0: fd(32) ready
  Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 6 threads of 3 
processes of 1 users.
  Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Successfully made thread 5660 of 
process 2708 owned by '1000' RT at priority 5.
  Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 7 threads of 3 
processes of 1 users.
  Mar 01 09:44:04 fenrir pulseaudio[2708]: org.freedesktop.DBus.Properties.Get 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0 Volume failed: 
org.freedesktop.DBus.Error.InvalidArgs: No such property 'Volume'
  Mar 01 09:44:04 fenrir pulseaudio[2708]: Battery Level: 70%
  Mar 01 09:44:04 fenrir pulseaudio[2708]: Dock Status: undocked

  But then if I close the laptop lid and reopen, login, and try to
  connect the headset the device is found invalid with the following
  logs:

  Mar 01 00:47:08 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as 
/devices/virtual/input/input152
  Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:08 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:08 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:08 fenrir systemd-logind[1545]: Watching system buttons on 
/dev/input/event19 (Bose QuietComfort 35 (AVRCP))
  Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:09 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:09 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:09 fenrir pulseaudio[253956]: Device doesn't exist for 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F
  Mar 01 00:47:09 fenrir bluetoothd[40741]: src/profile.c:new_conn_reply() 
Hands-Free Voice gateway replied with an error: 
org.bluez.Error.InvalidArguments, Unable to handle new connection
  Mar 01 00:47:09 

[Touch-packages] [Bug 1962542] Re: [jammy] Bluetooth headphones unable to connect after suspend in BlueZ 5.63

2022-03-02 Thread Daniel van Vugt
I expect this is https://github.com/bluez/bluez/issues/284 which Jeremy
is going to propose the patch for.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962542

Title:
  [jammy] Bluetooth headphones unable to connect after suspend in BlueZ
  5.63

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  Bose quietcomfort 35 is a common headset that can no longer connect to
  a jammy system after just one suspend. This started at the end of
  January but just now really debugging the issue.

  Side note that my bluetooth mouse works fine without problem after any
  amount of suspends.

  The headset is only trying to connect to the jammy system (no other
  bluetooth devices it's paired with has active bluetooth, to isolate
  only the jammy <-> headset issue). This is jammy running on a T590, up
  to date, not proposed.

  heather@fenrir:~$ dpkg -l | grep bluetooth
  ii  gir1.2-gnomebluetooth-1.0:amd643.34.5-4   
amd64Introspection data for GnomeBluetooth
  ii  gnome-bluetooth3.34.5-4   
amd64GNOME Bluetooth tools
  ii  libbluetooth-dev:amd64 5.63-0ubuntu1  
amd64Development files for using the BlueZ Linux Bluetooth 
library
  ii  libbluetooth3:amd645.63-0ubuntu1  
amd64Library to use the BlueZ Linux Bluetooth stack
  ii  libgnome-bluetooth13:amd64 3.34.5-4   
amd64GNOME Bluetooth tools - support library
  ii  pulseaudio-module-bluetooth1:15.99.1+dfsg1-1ubuntu1   
amd64Bluetooth module for PulseAudio sound server

  On a fresh boot (not suspended yet), I can connect the headset
  successfully. Here are the logs of that:

  Mar 01 09:44:02 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as 
/devices/virtual/input/input30
  Mar 01 09:44:02 fenrir systemd-logind[1570]: Watching system buttons on 
/dev/input/event22 (Bose QuietComfort 35 (AVRCP))
  Mar 01 09:44:03 fenrir NetworkManager[1536]:   [1646124243.8660] 
platform-linux: do-add-ip6-address[3: fe80::c1bc:a705:9e66:e0d0]: failure 13 
(Permission denied)
  Mar 01 09:44:04 fenrir bluetoothd[1532]: 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0: fd(32) ready
  Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 6 threads of 3 
processes of 1 users.
  Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Successfully made thread 5660 of 
process 2708 owned by '1000' RT at priority 5.
  Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 7 threads of 3 
processes of 1 users.
  Mar 01 09:44:04 fenrir pulseaudio[2708]: org.freedesktop.DBus.Properties.Get 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0 Volume failed: 
org.freedesktop.DBus.Error.InvalidArgs: No such property 'Volume'
  Mar 01 09:44:04 fenrir pulseaudio[2708]: Battery Level: 70%
  Mar 01 09:44:04 fenrir pulseaudio[2708]: Dock Status: undocked

  But then if I close the laptop lid and reopen, login, and try to
  connect the headset the device is found invalid with the following
  logs:

  Mar 01 00:47:08 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as 
/devices/virtual/input/input152
  Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:08 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:08 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:08 fenrir systemd-logind[1545]: Watching system buttons on 
/dev/input/event19 (Bose QuietComfort 35 (AVRCP))
  Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:09 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:09 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:09 fenrir pulseaudio[253956]: Device doesn't exist for 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F
  Mar 01 00:47:09 fenrir bluetoothd[40741]: src/profile.c:new_conn_reply() 
Hands-Free Voice gateway replied with an error: 
org.bluez.Error.InvalidArguments, Unable to handle new connection
  Mar 01 00:47:09 fenrir pulseaudio[253956]: Device doesn't exi

[Touch-packages] [Bug 1962542] Re: [jammy] Bluetooth headphones unable to connect after suspend in BlueZ 5.63

2022-03-02 Thread Heather Ellsworth
Regarding comment #17 and missing devices from rfkill, there was just a
miscommunication. I meant that the bluetooth line has not changed, and
only pasted that one. But in both cases (before/after suspend), I do see
all three lines as mentioned in #17. Sorry for the unnecessary
confusion.

I'm also attaching a full journalctl -b0 log.

Then regarding https://github.com/bluez/bluez/issues/272 and
https://github.com/bluez/bluez/issues/220, I do not have a systemd
coredump so doesn't look like 272 directly. I could try to downgrade to
bluez 5.61 and see if that fixes the issue (I expect it does since it
was working fine till recently), but sounds like it's fixed in 5.64 so
I'll test this older version if really necessary :)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962542

Title:
  [jammy] Bluetooth headphones unable to connect after suspend in BlueZ
  5.63

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  Bose quietcomfort 35 is a common headset that can no longer connect to
  a jammy system after just one suspend. This started at the end of
  January but just now really debugging the issue.

  Side note that my bluetooth mouse works fine without problem after any
  amount of suspends.

  The headset is only trying to connect to the jammy system (no other
  bluetooth devices it's paired with has active bluetooth, to isolate
  only the jammy <-> headset issue). This is jammy running on a T590, up
  to date, not proposed.

  heather@fenrir:~$ dpkg -l | grep bluetooth
  ii  gir1.2-gnomebluetooth-1.0:amd643.34.5-4   
amd64Introspection data for GnomeBluetooth
  ii  gnome-bluetooth3.34.5-4   
amd64GNOME Bluetooth tools
  ii  libbluetooth-dev:amd64 5.63-0ubuntu1  
amd64Development files for using the BlueZ Linux Bluetooth 
library
  ii  libbluetooth3:amd645.63-0ubuntu1  
amd64Library to use the BlueZ Linux Bluetooth stack
  ii  libgnome-bluetooth13:amd64 3.34.5-4   
amd64GNOME Bluetooth tools - support library
  ii  pulseaudio-module-bluetooth1:15.99.1+dfsg1-1ubuntu1   
amd64Bluetooth module for PulseAudio sound server

  On a fresh boot (not suspended yet), I can connect the headset
  successfully. Here are the logs of that:

  Mar 01 09:44:02 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as 
/devices/virtual/input/input30
  Mar 01 09:44:02 fenrir systemd-logind[1570]: Watching system buttons on 
/dev/input/event22 (Bose QuietComfort 35 (AVRCP))
  Mar 01 09:44:03 fenrir NetworkManager[1536]:   [1646124243.8660] 
platform-linux: do-add-ip6-address[3: fe80::c1bc:a705:9e66:e0d0]: failure 13 
(Permission denied)
  Mar 01 09:44:04 fenrir bluetoothd[1532]: 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0: fd(32) ready
  Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 6 threads of 3 
processes of 1 users.
  Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Successfully made thread 5660 of 
process 2708 owned by '1000' RT at priority 5.
  Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 7 threads of 3 
processes of 1 users.
  Mar 01 09:44:04 fenrir pulseaudio[2708]: org.freedesktop.DBus.Properties.Get 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0 Volume failed: 
org.freedesktop.DBus.Error.InvalidArgs: No such property 'Volume'
  Mar 01 09:44:04 fenrir pulseaudio[2708]: Battery Level: 70%
  Mar 01 09:44:04 fenrir pulseaudio[2708]: Dock Status: undocked

  But then if I close the laptop lid and reopen, login, and try to
  connect the headset the device is found invalid with the following
  logs:

  Mar 01 00:47:08 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as 
/devices/virtual/input/input152
  Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:08 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:08 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:08 fenrir systemd-logind[1545]: Watching system buttons on 
/dev/input/event19 (Bose QuietComfort 35 (AVRCP))
  Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:09 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 0

[Touch-packages] [Bug 1962542] Re: [jammy] Bluetooth headphones unable to connect after suspend in BlueZ 5.63

2022-03-02 Thread Daniel van Vugt
** Summary changed:

- Bluetooth headphones unable to connect after suspend
+ [jammy] Bluetooth headphones unable to connect after suspend in BlueZ 5.63

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962542

Title:
  [jammy] Bluetooth headphones unable to connect after suspend in BlueZ
  5.63

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  Bose quietcomfort 35 is a common headset that can no longer connect to
  a jammy system after just one suspend. This started at the end of
  January but just now really debugging the issue.

  Side note that my bluetooth mouse works fine without problem after any
  amount of suspends.

  The headset is only trying to connect to the jammy system (no other
  bluetooth devices it's paired with has active bluetooth, to isolate
  only the jammy <-> headset issue). This is jammy running on a T590, up
  to date, not proposed.

  heather@fenrir:~$ dpkg -l | grep bluetooth
  ii  gir1.2-gnomebluetooth-1.0:amd643.34.5-4   
amd64Introspection data for GnomeBluetooth
  ii  gnome-bluetooth3.34.5-4   
amd64GNOME Bluetooth tools
  ii  libbluetooth-dev:amd64 5.63-0ubuntu1  
amd64Development files for using the BlueZ Linux Bluetooth 
library
  ii  libbluetooth3:amd645.63-0ubuntu1  
amd64Library to use the BlueZ Linux Bluetooth stack
  ii  libgnome-bluetooth13:amd64 3.34.5-4   
amd64GNOME Bluetooth tools - support library
  ii  pulseaudio-module-bluetooth1:15.99.1+dfsg1-1ubuntu1   
amd64Bluetooth module for PulseAudio sound server

  On a fresh boot (not suspended yet), I can connect the headset
  successfully. Here are the logs of that:

  Mar 01 09:44:02 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as 
/devices/virtual/input/input30
  Mar 01 09:44:02 fenrir systemd-logind[1570]: Watching system buttons on 
/dev/input/event22 (Bose QuietComfort 35 (AVRCP))
  Mar 01 09:44:03 fenrir NetworkManager[1536]:   [1646124243.8660] 
platform-linux: do-add-ip6-address[3: fe80::c1bc:a705:9e66:e0d0]: failure 13 
(Permission denied)
  Mar 01 09:44:04 fenrir bluetoothd[1532]: 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0: fd(32) ready
  Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 6 threads of 3 
processes of 1 users.
  Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Successfully made thread 5660 of 
process 2708 owned by '1000' RT at priority 5.
  Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 7 threads of 3 
processes of 1 users.
  Mar 01 09:44:04 fenrir pulseaudio[2708]: org.freedesktop.DBus.Properties.Get 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0 Volume failed: 
org.freedesktop.DBus.Error.InvalidArgs: No such property 'Volume'
  Mar 01 09:44:04 fenrir pulseaudio[2708]: Battery Level: 70%
  Mar 01 09:44:04 fenrir pulseaudio[2708]: Dock Status: undocked

  But then if I close the laptop lid and reopen, login, and try to
  connect the headset the device is found invalid with the following
  logs:

  Mar 01 00:47:08 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as 
/devices/virtual/input/input152
  Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:08 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:08 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:08 fenrir systemd-logind[1545]: Watching system buttons on 
/dev/input/event19 (Bose QuietComfort 35 (AVRCP))
  Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:09 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:09 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:09 fenrir pulseaudio[253956]: Device doesn't exist for 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F
  Mar 01 00:47:09 fenrir bluetoothd[40741]: src/profile.c:new_conn_reply() 
Hands-Free Voice gateway replied with an error: 
org.bluez.Error.InvalidArguments, Unable to handle new connection
  Mar 01 00:47:09