Bluetooth headset discovered but fails to connect [Solved]

Help for Current Versions of MX
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
Message
Author
pteroglossus
Posts: 8
Joined: Sat Dec 24, 2022 2:10 pm

Bluetooth headset discovered but fails to connect [Solved]

#1 Post by pteroglossus »

Hi everyone,

I'm almost done setting up a persistent USB MX21 install on my professional laptop to use it without restrictions.

Everything has been surprisingly easy to install, but I'm having a hard time connecting my Bose QC35II headphones. The system was able to find and connect to my Bluetooth mouse without any issue, so it must be related to the audio server I guess?

I tried to find answers on forums but couldn't find much except https://www.linux.org/threads/cant-conn ... oth.37649/, but apt-get couldn't locate the "libspa-0.2-bluetooth" package and I'm not sure it's the cause of the problem anyway.

Here is the System Info:

Code: Select all

System:    Kernel: 5.10.0-18-amd64 [5.10.140-1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/antiX/vmlinuz quiet splasht nosplash lang=en_US kbd=fr 
           tz=America/Argentina/Buenos_Aires persist_all splasht 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.16.1 vt: 7 
           dm: LightDM 1.26.0 Distro: MX-21.2.1_x64 Wildflower September 18  2022 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: LENOVO product: 20RD001FFR v: ThinkPad E15 serial: <filter> 
           Chassis: type: 10 serial: <filter> 
           Mobo: LENOVO model: 20RD001FFR v: SDK0J40697 WIN serial: <filter> UEFI: LENOVO 
           v: R16ET23W (1.09 ) date: 01/07/2020 
Battery:   ID-1: BAT0 charge: 39.4 Wh (100.0%) condition: 39.4/45.7 Wh (86.1%) volts: 12.3 
           min: 11.1 model: Celxpert 5B10W138 type: Li-poly serial: <filter> status: Full 
           cycles: 138 
CPU:       Info: Quad Core model: Intel Core i5-10210U bits: 64 type: MT MCP arch: Kaby Lake 
           note: check family: 6 model-id: 8E (142) stepping: C (12) microcode: CA cache: 
           L2: 6 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 33599 
           Speed: 700 MHz min/max: 400/4200 MHz Core speeds (MHz): 1: 700 2: 700 3: 700 4: 700 
           5: 700 6: 700 7: 700 8: 700 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: mmio_stale_data 
           status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable 
           Type: retbleed mitigation: Enhanced IBRS 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: Enhanced IBRS, IBPB: conditional, RSB filling, PBRSB-eIBRS: SW sequence 
           Type: srbds status: Vulnerable: No microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel CometLake-U GT2 [UHD Graphics] vendor: Lenovo driver: i915 v: kernel 
           bus-ID: 00:02.0 chip-ID: 8086:9b41 class-ID: 0300 
           Device-2: Chicony Integrated Camera type: USB driver: uvcvideo bus-ID: 1-8:3 
           chip-ID: 04f2:b6d9 class-ID: 0e02 serial: <filter> 
           Display: x11 server: X.Org 1.20.11 compositor: xfwm4 v: 4.16.1 driver: 
           loaded: modesetting unloaded: fbdev,vesa display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") 
           s-diag: 582mm (22.9") 
           Monitor-1: eDP-1 res: 1920x1080 hz: 60 dpi: 142 size: 344x194mm (13.5x7.6") 
           diag: 395mm (15.5") 
           OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.3.5 
           direct render: Yes 
Audio:     Device-1: Intel Comet Lake PCH-LP cAVS vendor: Lenovo driver: snd_hda_intel v: kernel 
           alternate: snd_sof_pci bus-ID: 00:1f.3 chip-ID: 8086:02c8 class-ID: 0403 
           Sound Server-1: ALSA v: k5.10.0-18-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Intel Comet Lake PCH-LP CNVi WiFi driver: iwlwifi v: kernel modules: wl 
           port: 3000 bus-ID: 00:14.3 chip-ID: 8086:02f0 class-ID: 0280 
           IF: wlan0 state: up mac: <filter> 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Lenovo 
           driver: r8169 v: kernel port: 2000 bus-ID: 04:00.0 chip-ID: 10ec:8168 class-ID: 0200 
           IF: eth0 state: down mac: <filter> 
           IF-ID-1: ipv6leakintrf0 state: unknown speed: N/A duplex: N/A mac: <filter> 
           IF-ID-2: proton0 state: unknown speed: 10 Mbps duplex: full mac: N/A 
Bluetooth: Device-1: Intel type: USB driver: btusb v: 0.8 bus-ID: 1-10:5 chip-ID: 8087:0026 
           class-ID: e001 
           Report: hciconfig ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2 
           sub-v: 24bf hci-v: 5.2 rev: 24bf 
           Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: slave accept 
           service-classes: rendering, capturing, object transfer, audio 
Drives:    Local Storage: total: 253.13 GiB used: 6.94 GiB (2.7%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Toshiba model: N/A size: 238.47 GiB 
           block-size: physical: 512 B logical: 512 B speed: 15.8 Gb/s lanes: 2 type: SSD 
           serial: <filter> rev: 0108ADLA temp: 37.9 C scheme: GPT 
           ID-2: /dev/sda maj-min: 8:0 type: USB vendor: Kingston model: DataTraveler 3.0 
           size: 14.65 GiB block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> 
           rev: PMAP scheme: MBR 
           SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: file size: 200 MiB used: 0 KiB (0.0%) priority: -2 
           file: /live/boot-dev/swap-file 
Sensors:   System Temperatures: cpu: 56.0 C mobo: 0.0 C 
           Fan Speeds (RPM): cpu: 0 
Repos:     Packages: note: see --pkg apt: 1979 lib: 983 flatpak: 0 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb https://espejito.fder.edu.uy/mxlinux/packages/mx/repo/ bullseye main non-free
           Active apt repos in: /etc/apt/sources.list.d/protonvpn-stable.list 
           1: deb [arch="all", signed-by=/usr/share/keyrings/protonvpn-stable-archive-keyring.gpg] https://repo.protonvpn.com/debian stable main
Info:      Processes: 273 Uptime: 3h 28m wakeups: 4 Memory: 7.48 GiB used: 4.73 GiB (63.1%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: N/A 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: UEFI
Additionally, I've attached a screenshot of the Bluetooth Manager windows and the output of "apt -a show bluetooth".

Thanks for your help and Merry Christmas to all of you!
You do not have the required permissions to view the files attached to this post.
Last edited by pteroglossus on Wed Jan 04, 2023 7:17 pm, edited 1 time in total.

pteroglossus
Posts: 8
Joined: Sat Dec 24, 2022 2:10 pm

Re: Bluetooth headset discovered but fails to connect [Solved]

#2 Post by pteroglossus »

Hi,

I got it to work by removing the device from the Bluetooth Manager, paired again and this time I got a series of pairing requests which I accepted.

It's working well, the only issue now is that I get those pairing requests every time I connect the device.

I'll try and look for a way to make those automatically accepted.

User avatar
argonaut459
Posts: 524
Joined: Tue Oct 04, 2022 11:49 am

Re: Bluetooth headset discovered but fails to connect

#3 Post by argonaut459 »

IIRC there is an option for trusted device, and maybe even an auto connect.

See if these make the pairing requests obsolete.
Thank you very much in advance :heart:
Linux noob being grateful for help and assistance.

pteroglossus
Posts: 8
Joined: Sat Dec 24, 2022 2:10 pm

Re: Bluetooth headset discovered but fails to connect

#4 Post by pteroglossus »

Thanks for your reply, which I just saw. There is indeed an option to automatically connect trusted devices. For some reason I didn't see the pairing requests after my first attempts.

Post Reply

Return to “MX Help”