[Kernel-packages] [Bug 2084337] Re: [Intel 9460/9560] Bose QC35-II won't stay paired after upgrade to 24.10

2024-10-16 Thread Sergio Conde Gómez
This affects me using a Sennheiser HD 450BT, however, my Bluetooth
mouse, MX Master 3, works.

$ lsusb | grep -i blue
Bus 001 Device 005: ID 8087:0033 Intel Corp. AX211 Bluetooth

$ sudo dmesg | grep 00:1b:66:e8:f9:8f   

   
[   26.965503] Bluetooth: hci0: Invalid link address type 1 for 
00:1b:66:e8:f9:8f

Currently, I power on the headsets, trigger pairing mode, and connect to
the headsets in Ubuntu (no need to remove and re-pair, I just need to
trigger pairing mode in the headsets).

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2084337

Title:
  [Intel 9460/9560] Bose QC35-II won't stay paired after upgrade to
  24.10

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I've Bose QuietComfort 35 II bluetooth headphones/headset that I've
  been using with Ubuntu for several years now.  Since I upgraded to
  Ubuntu 24.10 yesterday, the headset refuses to connect to Ubuntu until
  I pair it again, every time.

  This is how things worked with 24.04 LTS:

  - I turn on the headset, it plays a little "I'm on" trill
  - the headset autoconnects to my phone and plays a little "I'm connected 
trill"
  - the headset autoconnects to my laptop and plays a little "I'm connected 
trill" (this was sometimes delayed by a few tens seconds, so sometimes I sped 
things up by running a shell script to `bluetoothctl connect 
$headset_mac_address`)
  - I can now play sounds through the headset

  This is how thigs go with 24.10:

  - I turn on the headset, it plays a little "I'm on" trill
  - the headset autoconnects to my phone and plays a little "I'm connected 
trill"
  - the second connection never comes through
  - I run `bluetoothctl connect $headset_mac_address` and I get

  Attempting to connect to 60:AB:D2:43:49:4D
  [CHG] Device 60:AB:D2:43:49:4D Connected: yes
  Failed to connect: org.bluez.Error.Failed br-connection-unknown

  - I open the Bose Connect app on my phone to look at the list of connections. 
 It shows my phone and nothing else.  It should be showing my laptop ("blynas") 
under History, and it used to do that before the upgrade.
  - I click "Connect new..." in the phone app (or pull and hold the button on 
the headset itself to put it in pairing mode), I hear a "ready to be paired" 
trill, I run `bluetooth connect $headset_mac_address` again (or click connect 
in gnome-control-center), and it connects fine.  I can play music and 
everything.  "blynas" is shown in the Current list of connected devices

  - I turn off the headset, I turn it back on
  - the headset autoconnects to both the phone and the laptop, because I'm 
intentionally trying to reproduce the bug, so of course it won't bug.

  Previously, whenever I turned the headset on after turning it off for
  a longer span of time, I had to do the 'Connect new...' thing.

  BTW once I tried to tell gnome-control-center to forget the headset,
  then paired it fresh, which got me a fresh new LinkKey in
  /var/lib/bluetooth/, and things worked fine until another turn-off-
  wait-hours-turn-on-oh-hey-what-is-this-new-laptop-I-don't-know-her-do-
  the-pairing-dance-again-please.

  (I keep track of the link key changes because I have a Windows 10
  partition on this machine and I sometimes boot it, so I need to keep
  the link key synchronized between Ubuntu and the Windows registry,
  otherwise the headset will work only in one of the two OSes.  However
  I haven't booted Windows in months if not years, so this should not be
  relevant.)

  ProblemType: Bug
  DistroRelease: Ubuntu 24.10
  Package: bluez 5.77-0ubuntu1
  ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0
  Uname: Linux 6.11.0-8-generic x86_64
  ApportVersion: 2.30.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 12 15:24:54 2024
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-06-12 (1949 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20Q0CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-8-generic 
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M 
vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to oracular on 2024-10-11 (1 days ago)
  dmi.bios.date: 07/25/2023
  dmi.bios.release: 1.80
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2JETA2W (1.80 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20Q0CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.

[Kernel-packages] [Bug 2081384] Re: bluetooth headphones need reconnect after every reboot

2024-11-14 Thread Sergio Conde Gómez
Coming here from
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2084337

I installed bluez 5.78 packages and kinda resolved it... I did some
reboots (both Ubuntu and the Headset) and don't have to trigger pair
mode in the headset anymore.

However, it looks like the first connecting attempt fails:

Nov 14 10:26:27 setebos bluetoothd[1289]: Authentication attempt without agent
Nov 14 10:26:27 setebos bluetoothd[1289]: src/profile.c:ext_auth() Hands-Free 
Voice gateway rejected 00:1B:66:E8:F9:8F: org.bluez.Error.Rejected
Nov 14 10:26:27 setebos bluetoothd[1289]: Authentication attempt without agent
Nov 14 10:26:27 setebos bluetoothd[1289]: profiles/audio/a2dp.c:auth_cb() 
Access denied: org.bluez.Error.Rejected

And the second one succeeds... keep testing later so I can check if this
is always or sometimes.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2081384

Title:
  bluetooth headphones need reconnect after every reboot

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in bluez source package in Oracular:
  Confirmed
Status in linux source package in Oracular:
  Confirmed

Bug description:
  This issue seems to be caused by a recent package update in oracular.
  Every time I reboot my desktop my bluetooth headset will fail to
  connect until I manually go through forget device -> new pairing.

  journalctl says:

  23:13:44 desktop bluetoothd[3274]: src/profile.c:ext_connect() Hands-Free 
Voice gateway failed connect to 80:C3:33:59:89:D6: Connection refused (111)
  23:13:45 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() 
connect to 80:C3:33:59:89:D6: Connection refused (111)
  23:13:47 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() 
connect to 80:C3:33:59:89:D6: Connection refused (111)
  23:13:59 desktop bluetoothd[3274]: src/profile.c:ext_connect() Hands-Free 
Voice gateway failed connect to 80:C3:33:59:89:D6: Connection refused (111)
  23:13:59 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() 
connect to 80:C3:33:59:89:D6: Connection refused (111)
  23:14:00 desktop bluetoothd[3274]: No matching connection for device
  23:14:04 desktop bluetoothd[3274]: src/profile.c:record_cb() Unable to get 
Hands-Free Voice gateway SDP record: Operation already in progress
  23:14:04 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() 
connect to 80:C3:33:59:89:D6: Connection refused (111)
  23:14:25 desktop bluetoothd[3274]: src/profile.c:ext_connect() Hands-Free 
Voice gateway failed connect to 80:C3:33:59:89:D6: Connection refused (111)
  23:14:25 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() 
connect to 80:C3:33:59:89:D6: Connection refused (111)
  23:14:27 desktop bluetoothd[3274]: profiles/audio/avdtp.c:avdtp_connect_cb() 
connect to 80:C3:33:59:89:D6: Connection refused (111)
  23:15:46 desktop bluetoothd[3274]: 
/org/bluez/hci0/dev_80_C3_33_59_89_D6/sep7/fd0: fd(43) ready

  In dmesg I see lots of:
  [44738.102583] Bluetooth: hci0: ACL packet for unknown connection handle 3837
  [44749.325565] Bluetooth: hci0: ACL packet for unknown connection handle 3837
  [44749.496566] Bluetooth: hci0: ACL packet for unknown connection handle 3837

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2081384/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp