Bluetooth doesn't work on start

Support
28

This could help I got the logs of bluetooth when trying to connect on boot, then after it the logs after running the script and connecting
Pre-script:

yamo: ~ > journalctl -b | grep -iE "bluetooth|hci|btusb"                                                                                                                                                                     <master*> 12:42
May 31 12:40:45 Yamo-Legion5 kernel: ahci 0000:06:00.0: version 3.0
May 31 12:40:45 Yamo-Legion5 kernel: ahci 0000:06:00.0: AHCI vers 0001.0301, 32 command slots, 6 Gbps, SATA mode
May 31 12:40:45 Yamo-Legion5 kernel: ahci 0000:06:00.0: 1/1 ports implemented (port mask 0x1)
May 31 12:40:45 Yamo-Legion5 kernel: ahci 0000:06:00.0: flags: 64bit ncq sntf ilck pm led clo only pmp fbs pio slum part 
May 31 12:40:45 Yamo-Legion5 kernel: scsi host0: ahci
May 31 12:40:45 Yamo-Legion5 kernel: ahci 0000:06:00.1: AHCI vers 0001.0301, 32 command slots, 6 Gbps, SATA mode
May 31 12:40:45 Yamo-Legion5 kernel: ahci 0000:06:00.1: 1/1 ports implemented (port mask 0x1)
May 31 12:40:45 Yamo-Legion5 kernel: ahci 0000:06:00.1: flags: 64bit ncq sntf ilck pm led clo only pmp fbs pio slum part 
May 31 12:40:45 Yamo-Legion5 kernel: scsi host1: ahci
May 31 12:40:45 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.3: xHCI Host Controller
May 31 12:40:45 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.3: new USB bus registered, assigned bus number 1
May 31 12:40:45 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.3: hcc params 0x0268ffe5 hci version 0x110 quirks 0x0000020000000010
May 31 12:40:45 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.3: xHCI Host Controller
May 31 12:40:45 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.3: new USB bus registered, assigned bus number 2
May 31 12:40:45 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.3: Host supports USB 3.1 Enhanced SuperSpeed
May 31 12:40:45 Yamo-Legion5 kernel: usb usb1: Product: xHCI Host Controller
May 31 12:40:45 Yamo-Legion5 kernel: usb usb1: Manufacturer: Linux 6.12.91-1-MANJARO xhci-hcd
May 31 12:40:45 Yamo-Legion5 kernel: usb usb2: Product: xHCI Host Controller
May 31 12:40:45 Yamo-Legion5 kernel: usb usb2: Manufacturer: Linux 6.12.91-1-MANJARO xhci-hcd
May 31 12:40:45 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.4: xHCI Host Controller
May 31 12:40:45 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.4: new USB bus registered, assigned bus number 3
May 31 12:40:45 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.4: hcc params 0x0268ffe5 hci version 0x110 quirks 0x0000020000000010
May 31 12:40:45 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.4: xHCI Host Controller
May 31 12:40:45 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.4: new USB bus registered, assigned bus number 4
May 31 12:40:45 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.4: Host supports USB 3.1 Enhanced SuperSpeed
May 31 12:40:45 Yamo-Legion5 kernel: usb usb3: Product: xHCI Host Controller
May 31 12:40:45 Yamo-Legion5 kernel: usb usb3: Manufacturer: Linux 6.12.91-1-MANJARO xhci-hcd
May 31 12:40:45 Yamo-Legion5 kernel: usb usb4: Product: xHCI Host Controller
May 31 12:40:45 Yamo-Legion5 kernel: usb usb4: Manufacturer: Linux 6.12.91-1-MANJARO xhci-hcd
May 31 12:40:45 Yamo-Legion5 kernel: usb 1-3: new high-speed USB device number 2 using xhci_hcd
May 31 12:40:45 Yamo-Legion5 kernel: usb 3-1: new high-speed USB device number 2 using xhci_hcd
May 31 12:40:45 Yamo-Legion5 kernel: usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd
May 31 12:40:45 Yamo-Legion5 kernel: usb 3-3: new full-speed USB device number 3 using xhci_hcd
May 31 12:40:45 Yamo-Legion5 kernel: usb 3-1.1: new full-speed USB device number 4 using xhci_hcd
May 31 12:40:45 Yamo-Legion5 kernel: usb 3-4: new full-speed USB device number 5 using xhci_hcd
May 31 12:40:49 Yamo-Legion5 NetworkManager[2647]: <info>  [1780220449.0023] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.56.1-1/libnm-device-plugin-bluetooth.so)
May 31 12:40:49 Yamo-Legion5 kernel: Bluetooth: Core ver 2.22
May 31 12:40:49 Yamo-Legion5 kernel: NET: Registered PF_BLUETOOTH protocol family
May 31 12:40:49 Yamo-Legion5 kernel: Bluetooth: HCI device and connection manager initialized
May 31 12:40:49 Yamo-Legion5 kernel: Bluetooth: HCI socket layer initialized
May 31 12:40:49 Yamo-Legion5 kernel: Bluetooth: L2CAP socket layer initialized
May 31 12:40:49 Yamo-Legion5 kernel: Bluetooth: SCO socket layer initialized
May 31 12:40:49 Yamo-Legion5 kernel: usbcore: registered new interface driver btusb
May 31 12:40:49 Yamo-Legion5 systemd[1]: Starting Bluetooth service...
May 31 12:40:49 Yamo-Legion5 (sleep)[3727]: bluetooth.service: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
May 31 12:40:49 Yamo-Legion5 kernel: Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
May 31 12:40:49 Yamo-Legion5 kernel: Bluetooth: hci0: Boot Address: 0x24800
May 31 12:40:49 Yamo-Legion5 kernel: Bluetooth: hci0: Firmware Version: 193-33.24
May 31 12:40:49 Yamo-Legion5 kernel: Bluetooth: hci0: Firmware already loaded
May 31 12:40:49 Yamo-Legion5 kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
May 31 12:40:52 Yamo-Legion5 (bluetoothd)[6774]: bluetooth.service: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
May 31 12:40:52 Yamo-Legion5 bluetoothd[6774]: Bluetooth daemon 5.86
May 31 12:40:52 Yamo-Legion5 systemd[1]: Started Bluetooth service.
May 31 12:40:52 Yamo-Legion5 systemd[1]: Reached target Bluetooth Support.
May 31 12:40:52 Yamo-Legion5 bluetoothd[6774]: Starting SDP server
May 31 12:40:52 Yamo-Legion5 kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
May 31 12:40:52 Yamo-Legion5 kernel: Bluetooth: BNEP filters: protocol multicast
May 31 12:40:52 Yamo-Legion5 kernel: Bluetooth: BNEP socket layer initialized
May 31 12:40:52 Yamo-Legion5 bluetoothd[6774]: Bluetooth management interface 1.23 initialized
May 31 12:40:52 Yamo-Legion5 bluetoothd[6774]: Battery Provider Manager created
May 31 12:40:52 Yamo-Legion5 kernel: Bluetooth: MGMT ver 1.23
May 31 12:40:52 Yamo-Legion5 bluetoothd[6774]: Failed to set default system config for hci0
May 31 12:40:52 Yamo-Legion5 NetworkManager[2647]: <info>  [1780220452.6695] manager: (04:79:70:EC:9C:0B): new Bluetooth device (/org/freedesktop/NetworkManager/Devices/7)
May 31 12:41:00 Yamo-Legion5 kernel: Bluetooth: RFCOMM TTY layer initialized
May 31 12:41:00 Yamo-Legion5 kernel: Bluetooth: RFCOMM socket layer initialized
May 31 12:41:00 Yamo-Legion5 kernel: Bluetooth: RFCOMM ver 1.11
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/ldac
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aptx_hd
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_hd
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aptx
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aac
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aac
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_g
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_g
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/sbc
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/sbc
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_1
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_0
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/faststream
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/faststream_duplex
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_05
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_05
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_05_duplex
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_05_duplex
May 31 12:41:21 Yamo-Legion5 bluetoothd[6774]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
May 31 12:41:26 Yamo-Legion5 systemd[7486]: Reached target Bluetooth.
May 31 12:41:26 Yamo-Legion5 bluetoothd[6774]: profiles/audio/avdtp.c:try_send() send: Transport endpoint is not connected (107)
May 31 12:41:26 Yamo-Legion5 bluetoothd[6774]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 98:47:44:70:8C:93: Input/output error
May 31 12:41:26 Yamo-Legion5 bluetoothd[6774]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 98:47:44:70:8C:93: Device or resource busy
May 31 12:41:47 Yamo-Legion5 sudo[14795]:     yamo : TTY=pts/1 ; PWD=/home/yamo ; USER=root ; COMMAND=/usr/bin/systemctl edit bluetooth.service
May 31 12:42:05 Yamo-Legion5 systemd[1]: /etc/systemd/system/bluetooth.service.d/override.conf:1: Assignment outside of section. Ignoring.

Post-Script:

yamo: ~ > journalctl -b | grep -iE "bluetooth|hci|btusb"                                                                                                                                                                     <master*> 12:42
May 31 12:40:45 Yamo-Legion5 kernel: ahci 0000:06:00.0: version 3.0
May 31 12:40:45 Yamo-Legion5 kernel: ahci 0000:06:00.0: AHCI vers 0001.0301, 32 command slots, 6 Gbps, SATA mode
May 31 12:40:45 Yamo-Legion5 kernel: ahci 0000:06:00.0: 1/1 ports implemented (port mask 0x1)
May 31 12:40:45 Yamo-Legion5 kernel: ahci 0000:06:00.0: flags: 64bit ncq sntf ilck pm led clo only pmp fbs pio slum part 
May 31 12:40:45 Yamo-Legion5 kernel: scsi host0: ahci
May 31 12:40:45 Yamo-Legion5 kernel: ahci 0000:06:00.1: AHCI vers 0001.0301, 32 command slots, 6 Gbps, SATA mode
May 31 12:40:45 Yamo-Legion5 kernel: ahci 0000:06:00.1: 1/1 ports implemented (port mask 0x1)
May 31 12:40:45 Yamo-Legion5 kernel: ahci 0000:06:00.1: flags: 64bit ncq sntf ilck pm led clo only pmp fbs pio slum part 
May 31 12:40:45 Yamo-Legion5 kernel: scsi host1: ahci
May 31 12:40:45 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.3: xHCI Host Controller
May 31 12:40:45 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.3: new USB bus registered, assigned bus number 1
May 31 12:40:45 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.3: hcc params 0x0268ffe5 hci version 0x110 quirks 0x0000020000000010
May 31 12:40:45 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.3: xHCI Host Controller
May 31 12:40:45 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.3: new USB bus registered, assigned bus number 2
May 31 12:40:45 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.3: Host supports USB 3.1 Enhanced SuperSpeed
May 31 12:40:45 Yamo-Legion5 kernel: usb usb1: Product: xHCI Host Controller
May 31 12:40:45 Yamo-Legion5 kernel: usb usb1: Manufacturer: Linux 6.12.91-1-MANJARO xhci-hcd
May 31 12:40:45 Yamo-Legion5 kernel: usb usb2: Product: xHCI Host Controller
May 31 12:40:45 Yamo-Legion5 kernel: usb usb2: Manufacturer: Linux 6.12.91-1-MANJARO xhci-hcd
May 31 12:40:45 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.4: xHCI Host Controller
May 31 12:40:45 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.4: new USB bus registered, assigned bus number 3
May 31 12:40:45 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.4: hcc params 0x0268ffe5 hci version 0x110 quirks 0x0000020000000010
May 31 12:40:45 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.4: xHCI Host Controller
May 31 12:40:45 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.4: new USB bus registered, assigned bus number 4
May 31 12:40:45 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.4: Host supports USB 3.1 Enhanced SuperSpeed
May 31 12:40:45 Yamo-Legion5 kernel: usb usb3: Product: xHCI Host Controller
May 31 12:40:45 Yamo-Legion5 kernel: usb usb3: Manufacturer: Linux 6.12.91-1-MANJARO xhci-hcd
May 31 12:40:45 Yamo-Legion5 kernel: usb usb4: Product: xHCI Host Controller
May 31 12:40:45 Yamo-Legion5 kernel: usb usb4: Manufacturer: Linux 6.12.91-1-MANJARO xhci-hcd
May 31 12:40:45 Yamo-Legion5 kernel: usb 1-3: new high-speed USB device number 2 using xhci_hcd
May 31 12:40:45 Yamo-Legion5 kernel: usb 3-1: new high-speed USB device number 2 using xhci_hcd
May 31 12:40:45 Yamo-Legion5 kernel: usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd
May 31 12:40:45 Yamo-Legion5 kernel: usb 3-3: new full-speed USB device number 3 using xhci_hcd
May 31 12:40:45 Yamo-Legion5 kernel: usb 3-1.1: new full-speed USB device number 4 using xhci_hcd
May 31 12:40:45 Yamo-Legion5 kernel: usb 3-4: new full-speed USB device number 5 using xhci_hcd
May 31 12:40:49 Yamo-Legion5 NetworkManager[2647]: <info>  [1780220449.0023] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.56.1-1/libnm-device-plugin-bluetooth.so)
May 31 12:40:49 Yamo-Legion5 kernel: Bluetooth: Core ver 2.22
May 31 12:40:49 Yamo-Legion5 kernel: NET: Registered PF_BLUETOOTH protocol family
May 31 12:40:49 Yamo-Legion5 kernel: Bluetooth: HCI device and connection manager initialized
May 31 12:40:49 Yamo-Legion5 kernel: Bluetooth: HCI socket layer initialized
May 31 12:40:49 Yamo-Legion5 kernel: Bluetooth: L2CAP socket layer initialized
May 31 12:40:49 Yamo-Legion5 kernel: Bluetooth: SCO socket layer initialized
May 31 12:40:49 Yamo-Legion5 kernel: usbcore: registered new interface driver btusb
May 31 12:40:49 Yamo-Legion5 systemd[1]: Starting Bluetooth service...
May 31 12:40:49 Yamo-Legion5 (sleep)[3727]: bluetooth.service: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
May 31 12:40:49 Yamo-Legion5 kernel: Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
May 31 12:40:49 Yamo-Legion5 kernel: Bluetooth: hci0: Boot Address: 0x24800
May 31 12:40:49 Yamo-Legion5 kernel: Bluetooth: hci0: Firmware Version: 193-33.24
May 31 12:40:49 Yamo-Legion5 kernel: Bluetooth: hci0: Firmware already loaded
May 31 12:40:49 Yamo-Legion5 kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
May 31 12:40:52 Yamo-Legion5 (bluetoothd)[6774]: bluetooth.service: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
May 31 12:40:52 Yamo-Legion5 bluetoothd[6774]: Bluetooth daemon 5.86
May 31 12:40:52 Yamo-Legion5 systemd[1]: Started Bluetooth service.
May 31 12:40:52 Yamo-Legion5 systemd[1]: Reached target Bluetooth Support.
May 31 12:40:52 Yamo-Legion5 bluetoothd[6774]: Starting SDP server
May 31 12:40:52 Yamo-Legion5 kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
May 31 12:40:52 Yamo-Legion5 kernel: Bluetooth: BNEP filters: protocol multicast
May 31 12:40:52 Yamo-Legion5 kernel: Bluetooth: BNEP socket layer initialized
May 31 12:40:52 Yamo-Legion5 bluetoothd[6774]: Bluetooth management interface 1.23 initialized
May 31 12:40:52 Yamo-Legion5 bluetoothd[6774]: Battery Provider Manager created
May 31 12:40:52 Yamo-Legion5 kernel: Bluetooth: MGMT ver 1.23
May 31 12:40:52 Yamo-Legion5 bluetoothd[6774]: Failed to set default system config for hci0
May 31 12:40:52 Yamo-Legion5 NetworkManager[2647]: <info>  [1780220452.6695] manager: (04:79:70:EC:9C:0B): new Bluetooth device (/org/freedesktop/NetworkManager/Devices/7)
May 31 12:41:00 Yamo-Legion5 kernel: Bluetooth: RFCOMM TTY layer initialized
May 31 12:41:00 Yamo-Legion5 kernel: Bluetooth: RFCOMM socket layer initialized
May 31 12:41:00 Yamo-Legion5 kernel: Bluetooth: RFCOMM ver 1.11
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/ldac
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aptx_hd
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_hd
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aptx
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aac
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aac
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_g
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_g
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/sbc
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/sbc
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_1
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_0
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/faststream
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/faststream_duplex
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_05
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_05
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_05_duplex
May 31 12:41:00 Yamo-Legion5 bluetoothd[6774]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_05_duplex
May 31 12:41:21 Yamo-Legion5 bluetoothd[6774]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
May 31 12:41:26 Yamo-Legion5 systemd[7486]: Reached target Bluetooth.
May 31 12:41:26 Yamo-Legion5 bluetoothd[6774]: profiles/audio/avdtp.c:try_send() send: Transport endpoint is not connected (107)
May 31 12:41:26 Yamo-Legion5 bluetoothd[6774]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 98:47:44:70:8C:93: Input/output error
May 31 12:41:26 Yamo-Legion5 bluetoothd[6774]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 98:47:44:70:8C:93: Device or resource busy
May 31 12:41:47 Yamo-Legion5 sudo[14795]:     yamo : TTY=pts/1 ; PWD=/home/yamo ; USER=root ; COMMAND=/usr/bin/systemctl edit bluetooth.service
May 31 12:42:05 Yamo-Legion5 systemd[1]: /etc/systemd/system/bluetooth.service.d/override.conf:1: Assignment outside of section. Ignoring.
May 31 12:42:42 Yamo-Legion5 sudo[19430]:     yamo : TTY=pts/1 ; PWD=/home/yamo ; USER=root ; COMMAND=/usr/bin/modprobe -r btusb
May 31 12:42:42 Yamo-Legion5 kernel: usbcore: deregistering interface driver btusb
May 31 12:42:42 Yamo-Legion5 bluetoothd[6774]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/ldac
May 31 12:42:42 Yamo-Legion5 bluetoothd[6774]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aptx_hd
May 31 12:42:42 Yamo-Legion5 bluetoothd[6774]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_hd
May 31 12:42:42 Yamo-Legion5 bluetoothd[6774]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aptx
May 31 12:42:42 Yamo-Legion5 bluetoothd[6774]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx
May 31 12:42:42 Yamo-Legion5 bluetoothd[6774]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aac
May 31 12:42:42 Yamo-Legion5 bluetoothd[6774]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aac
May 31 12:42:42 Yamo-Legion5 bluetoothd[6774]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_g
May 31 12:42:42 Yamo-Legion5 bluetoothd[6774]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_g
May 31 12:42:42 Yamo-Legion5 bluetoothd[6774]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/sbc
May 31 12:42:42 Yamo-Legion5 bluetoothd[6774]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/sbc
May 31 12:42:42 Yamo-Legion5 bluetoothd[6774]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_1
May 31 12:42:42 Yamo-Legion5 bluetoothd[6774]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_0
May 31 12:42:42 Yamo-Legion5 bluetoothd[6774]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
May 31 12:42:42 Yamo-Legion5 bluetoothd[6774]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
May 31 12:42:42 Yamo-Legion5 bluetoothd[6774]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/faststream
May 31 12:42:42 Yamo-Legion5 bluetoothd[6774]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/faststream_duplex
May 31 12:42:42 Yamo-Legion5 bluetoothd[6774]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_05
May 31 12:42:42 Yamo-Legion5 bluetoothd[6774]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_05
May 31 12:42:42 Yamo-Legion5 bluetoothd[6774]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_05_duplex
May 31 12:42:42 Yamo-Legion5 bluetoothd[6774]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_05_duplex
May 31 12:42:42 Yamo-Legion5 bluetoothd[6774]: Battery Provider Manager destroyed
May 31 12:42:42 Yamo-Legion5 systemd[7486]: Stopped target Bluetooth.
May 31 12:42:42 Yamo-Legion5 systemd[1]: Stopped target Bluetooth Support.
May 31 12:42:42 Yamo-Legion5 sudo[19443]:     yamo : TTY=pts/1 ; PWD=/home/yamo ; USER=root ; COMMAND=/usr/bin/modprobe btusb
May 31 12:42:42 Yamo-Legion5 kernel: usbcore: registered new interface driver btusb
May 31 12:42:42 Yamo-Legion5 systemd[7486]: Reached target Bluetooth.
May 31 12:42:42 Yamo-Legion5 systemd[1]: Reached target Bluetooth Support.
May 31 12:42:42 Yamo-Legion5 sudo[19449]:     yamo : TTY=pts/1 ; PWD=/home/yamo ; USER=root ; COMMAND=/usr/bin/systemctl restart bluetooth
May 31 12:42:42 Yamo-Legion5 bluetoothd[6774]: Terminating
May 31 12:42:42 Yamo-Legion5 systemd[1]: Stopping Bluetooth service...
May 31 12:42:42 Yamo-Legion5 bluetoothd[6774]: Stopping SDP server
May 31 12:42:42 Yamo-Legion5 bluetoothd[6774]: Exit
May 31 12:42:42 Yamo-Legion5 systemd[1]: bluetooth.service: Deactivated successfully.
May 31 12:42:42 Yamo-Legion5 systemd[1]: Stopped Bluetooth service.
May 31 12:42:42 Yamo-Legion5 systemd[1]: Starting Bluetooth service...
May 31 12:42:42 Yamo-Legion5 (bluetoothd)[19457]: bluetooth.service: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
May 31 12:42:42 Yamo-Legion5 bluetoothd[19457]: Bluetooth daemon 5.86
May 31 12:42:42 Yamo-Legion5 systemd[1]: Started Bluetooth service.
May 31 12:42:42 Yamo-Legion5 bluetoothd[19457]: Starting SDP server
May 31 12:42:42 Yamo-Legion5 bluetoothd[19457]: Bluetooth management interface 1.23 initialized
May 31 12:42:42 Yamo-Legion5 kernel: Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
May 31 12:42:42 Yamo-Legion5 kernel: Bluetooth: hci0: Boot Address: 0x24800
May 31 12:42:42 Yamo-Legion5 kernel: Bluetooth: hci0: Firmware Version: 193-33.24
May 31 12:42:42 Yamo-Legion5 kernel: Bluetooth: hci0: Firmware already loaded
May 31 12:42:42 Yamo-Legion5 kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
May 31 12:42:43 Yamo-Legion5 bluetoothd[19457]: Battery Provider Manager created
May 31 12:42:43 Yamo-Legion5 bluetoothd[19457]: Failed to set default system config for hci0
May 31 12:42:43 Yamo-Legion5 kernel: Bluetooth: MGMT ver 1.23
May 31 12:42:43 Yamo-Legion5 NetworkManager[2647]: <info>  [1780220563.1988] manager: (04:79:70:EC:9C:0B): new Bluetooth device (/org/freedesktop/NetworkManager/Devices/8)
May 31 12:42:43 Yamo-Legion5 bluetoothd[19457]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/ldac
May 31 12:42:43 Yamo-Legion5 bluetoothd[19457]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aptx_hd
May 31 12:42:43 Yamo-Legion5 bluetoothd[19457]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_hd
May 31 12:42:43 Yamo-Legion5 bluetoothd[19457]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aptx
May 31 12:42:43 Yamo-Legion5 bluetoothd[19457]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx
May 31 12:42:43 Yamo-Legion5 bluetoothd[19457]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aac
May 31 12:42:43 Yamo-Legion5 bluetoothd[19457]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aac
May 31 12:42:43 Yamo-Legion5 bluetoothd[19457]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_g
May 31 12:42:43 Yamo-Legion5 bluetoothd[19457]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_g
May 31 12:42:43 Yamo-Legion5 bluetoothd[19457]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/sbc
May 31 12:42:43 Yamo-Legion5 bluetoothd[19457]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/sbc
May 31 12:42:43 Yamo-Legion5 bluetoothd[19457]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_1
May 31 12:42:43 Yamo-Legion5 bluetoothd[19457]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_0
May 31 12:42:43 Yamo-Legion5 bluetoothd[19457]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
May 31 12:42:43 Yamo-Legion5 bluetoothd[19457]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
May 31 12:42:43 Yamo-Legion5 bluetoothd[19457]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/faststream
May 31 12:42:43 Yamo-Legion5 bluetoothd[19457]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/faststream_duplex
May 31 12:42:43 Yamo-Legion5 bluetoothd[19457]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_05
May 31 12:42:43 Yamo-Legion5 bluetoothd[19457]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_05
May 31 12:42:43 Yamo-Legion5 bluetoothd[19457]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_05_duplex
May 31 12:42:43 Yamo-Legion5 bluetoothd[19457]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_05_duplex
May 31 12:42:52 Yamo-Legion5 tlp[19827]: Enabling radios: bluetooth wifi.

I also did sudo systemctl edit bluetooth.service and added

[Service]
ExecStartPre=/bin/sleep 3

but that didn’t fix it so I removed it again.

Mod edit: Consecutive posts merged.

29

3 seconds may not be enough.

Another idea for the workaround: restarting with rfkill?

30

I extended the 3 seconds to 10, I will try again on the next boot, and will update you.

I will try rfkill as well.

31

Did you try using the boot parameter to disable autosuspend?

ArchWiki - Bluetooth - bluetoothctl: No default controller available

Power saving measures can cause issues, in which case adding the kernel parameter btusb.enable_autosuspend=n is a potential solution (see bug report).

But inxi data in original post shows PipeWire in use

  Server-2: PipeWire v: 1.6.4 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Switching to PulseAudio would make it easier to disable bluez support for Bluetooth audio devices by removing `pulseaudio-bluetooth`

It should also be possible to disable Bluetooth support in PipeWire session manager Wireplumber.
Bluetooth configuration — WirePlumber 0.5.14 documentation

32

Yes, I had to switch to it since Wayland became the official compositor, but when I originally switched that’s when the issue started

Why would I want to disable bluez support?

33

Could you please run this command, so we have an overview of the installed packages:
pacman -Q | grep -iE "jack|pulse|pipewire"

Edit:
Personally, I hate not being able to figure out the exact reason. But at some point, you just have to admit defeat (for now).

For a while, I had to run several commands via a script after the system woke up. Here’s how you could solve it:
sudo nano /lib/systemd/system-sleep/bluetooth

#!/bin/bash

case "$1" in
    post)
        modprobe -r btusb
        modprobe btusb
        systemctl restart bluetooth
        ;;
esac

Then:
sudo chmod +x /lib/systemd/system-sleep/bluetooth

Of course, the pairing thing is still a pain.

1 Like
34

Apologies
That comment is not relevant for this topic and has been redacted
:facepalm:

1 Like
35

@Teo
I tried to extend the duration to 10 seconds but that did not resolve it, I will try the rfkill method next.

@pwx

Here is the installed packages

yamo: ~ > pacman -Q | grep -iE "jack|pulse|pipewire"                                                                                                                                                                         <master*> 13:50


apulse 0.1.14-1
gst-plugin-pipewire 1:1.6.5-2
kpipewire 6.6.5-1
lib32-libpipewire 1:1.6.5-2
lib32-libpulse 17.0+r98+gb096704c0-1
lib32-pipewire 1:1.6.5-2
lib32-pipewire-jack 1:1.6.5-2
libpipewire 1:1.6.5-2
libpulse 17.0+r98+gb096704c0-1
manjaro-pipewire 20231009-1
pipewire 1:1.6.5-2
pipewire-alsa 1:1.6.5-2
pipewire-audio 1:1.6.5-2
pipewire-jack 1:1.6.5-2
pipewire-pulse 1:1.6.5-2
pipewire-session-manager 1:1.6.5-2
pulseaudio-ctl 1.70-2
pulseaudio-qt 1.8.1-1
pulsemixer 1.5.1-8
qemu-audio-jack 11.0.0-1
qemu-audio-pipewire 11.0.0-1

Thanks for the systemd wake up script, I will do it, quick question would it want the sudo password?

I’m not seeing it would, but I tried to put my script as a script to be run on Autostart and it failed multiple times because it required the password.

@nikgnomic

Thanks for the help.

36

Apart from apulse and qemu, I’ve installed the same packages.

systemd runs as root unless you explicitly specify a user or group in the systemd unit file.

37

AUR package apulse is unlikely to cause problems for Bluetooth devices, but might be a problem with pipewire-pulse audio server and bluez audio streams

GitHub - i-rinat/apulse: PulseAudio emulation for ALSA · GitHub
apulse wasn’t designed to be a drop-in replacement of PulseAudio. It’s pointless, since that will be just reimplementation of original PulseAudio, with the same client-daemon architecture, required by the complete feature set. Instead, only parts of the API that are crucial to specific applications are implemented.

39

@nikgnomic
I went ahead and removed it.

@Teo
I tried rfkill and apparently it has the same effect as my script and fixed it for this boot.

Here are the commands I ran:

yamo: ~ > rfkill list                                                                                                                                                                                                        
0: ideapad_wlan: Wireless LAN
	Soft blocked: no
	Hard blocked: no
1: ideapad_bluetooth: Bluetooth
	Soft blocked: no
	Hard blocked: no
2: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
3: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
yamo: ~ > sudo rfkill block bluetooth                                                                                                                                                                                       
yamo: ~ > sudo rfkill unblock bluetooth                                                                                                                                                                                     
yamo: ~ > sudo systemctl restart bluetooth

Mod edit: Consecutive posts merged.

40

Have you tried rfkill block+unblock and systemctl restart separately? Only one of those might be enought. If systemctl is enough, then you can try just to edit the service and add a bit of delay, like 30 seconds for example.
Seems like the bluetooth service starts a bit too fast and something else is not loaded yet (driver?). So delaying the start of the service might solve the problem. Just a hypothesis, has to be tested.

41

@Teo
I did try before the systemctl restart alone, but it didn’t fix it alone, so I will try later the block+unblock separately, I will also try the systemctl restart again.

isn’t 30 seconds a lot of time? in the logs it seemed that everything was loaded almost instantly in the same second.

I did the 10 seconds but no changes happened.

What does the bluetooth service depend on? (i.e. which driver is the one not being loaded fast enough? how can I find out?)

42

systemctl show -p Requires,Wants,Conflicts,After,BindsTo bluetooth.service

Requires=dbus.socket sysinit.target system.slice -.mount
Wants=-.mount tmp.mount
BindsTo=
Conflicts=shutdown.target
After=system.slice basic.target sysinit.target -.mount systemd-tmpfiles-setup.service tmp.mount systemd-journald.socket dbus.socket systemd-remount-fs.service

lsmod | grep blue

bluetooth 1187840 52 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm
rfkill 45056 6 bluetooth

44

@pwx
I believe I have the same thing
systemctl show -p Requires,Wants,Conflicts,After,BindsTo bluetooth.service 

Requires=-.mount sysinit.target system.slice dbus.socket
Wants=tmp.mount -.mount
BindsTo=
Conflicts=shutdown.target
After=systemd-tmpfiles-setup.service -.mount tmp.mount basic.target dbus.socket sysinit.target systemd-remount-fs.service system.slice systemd-journald.socket

lsmod | grep blue

bluetooth            1110016  34 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm
rfkill                 40960  10 iwlmvm,bluetooth,ideapad_laptop,cfg80211
crc16                  12288  3 bluetooth,amdgpu,ext4

I don’t know if I am looking at the right thing but I tried to search those keywords in here in this log and I don’t believe that I found anything related to them.

Mod edit: Consecutive posts merged. If there are no intervening replies, please edit your previous post instead to add further information. :wink:

45

We’re really in the dark here. Why does this only happen on wake up…

46

Logic dictates that a race condition would be the most likely culprit. :man_shrugging:

3 Likes
47

What made me look twice:

May 31 11:10:57 Yamo-Legion5 bluetoothd[3704]: Bluetooth management interface 1.23 initialized
May 31 11:10:57 Yamo-Legion5 kernel: Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
May 31 11:10:57 Yamo-Legion5 kernel: Bluetooth: hci0: Boot Address: 0x24800
May 31 11:10:57 Yamo-Legion5 kernel: Bluetooth: hci0: Firmware Version: 193-33.24
May 31 11:10:57 Yamo-Legion5 kernel: Bluetooth: hci0: Firmware already loaded

48

Here are some more logs of the issue, I am currently trying to debug this

Jun 03 20:49:13 Yamo-Legion5 kernel: ahci 0000:06:00.0: version 3.0
Jun 03 20:49:13 Yamo-Legion5 kernel: ahci 0000:06:00.0: AHCI vers 0001.0301, 32 command slots, 6 Gbps, SATA mode
Jun 03 20:49:13 Yamo-Legion5 kernel: ahci 0000:06:00.0: 1/1 ports implemented (port mask 0x1)
Jun 03 20:49:13 Yamo-Legion5 kernel: ahci 0000:06:00.0: flags: 64bit ncq sntf ilck pm led clo only pmp fbs pio slum part
Jun 03 20:49:13 Yamo-Legion5 kernel: scsi host0: ahci
Jun 03 20:49:13 Yamo-Legion5 kernel: ahci 0000:06:00.1: AHCI vers 0001.0301, 32 command slots, 6 Gbps, SATA mode
Jun 03 20:49:13 Yamo-Legion5 kernel: ahci 0000:06:00.1: 1/1 ports implemented (port mask 0x1)
Jun 03 20:49:13 Yamo-Legion5 kernel: ahci 0000:06:00.1: flags: 64bit ncq sntf ilck pm led clo only pmp fbs pio slum part
Jun 03 20:49:13 Yamo-Legion5 kernel: scsi host1: ahci
Jun 03 20:49:13 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.3: xHCI Host Controller
Jun 03 20:49:13 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.3: new USB bus registered, assigned bus number 1
Jun 03 20:49:13 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.3: hcc params 0x0268ffe5 hci version 0x110 quirks 0x0000020000000010
Jun 03 20:49:13 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.3: xHCI Host Controller
Jun 03 20:49:13 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.3: new USB bus registered, assigned bus number 2
Jun 03 20:49:13 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.3: Host supports USB 3.1 Enhanced SuperSpeed
Jun 03 20:49:13 Yamo-Legion5 kernel: usb usb1: Product: xHCI Host Controller
Jun 03 20:49:13 Yamo-Legion5 kernel: usb usb1: Manufacturer: Linux 6.12.91-1-MANJARO xhci-hcd
Jun 03 20:49:13 Yamo-Legion5 kernel: usb usb2: Product: xHCI Host Controller
Jun 03 20:49:13 Yamo-Legion5 kernel: usb usb2: Manufacturer: Linux 6.12.91-1-MANJARO xhci-hcd
Jun 03 20:49:13 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.4: xHCI Host Controller
Jun 03 20:49:13 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.4: new USB bus registered, assigned bus number 3
Jun 03 20:49:13 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.4: hcc params 0x0268ffe5 hci version 0x110 quirks 0x0000020000000010
Jun 03 20:49:13 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.4: xHCI Host Controller
Jun 03 20:49:13 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.4: new USB bus registered, assigned bus number 4
Jun 03 20:49:13 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.4: Host supports USB 3.1 Enhanced SuperSpeed
Jun 03 20:49:13 Yamo-Legion5 kernel: usb usb3: Product: xHCI Host Controller
Jun 03 20:49:13 Yamo-Legion5 kernel: usb usb3: Manufacturer: Linux 6.12.91-1-MANJARO xhci-hcd
Jun 03 20:49:13 Yamo-Legion5 kernel: usb usb4: Product: xHCI Host Controller
Jun 03 20:49:13 Yamo-Legion5 kernel: usb usb4: Manufacturer: Linux 6.12.91-1-MANJARO xhci-hcd
Jun 03 20:49:13 Yamo-Legion5 kernel: usb 1-3: new high-speed USB device number 2 using xhci_hcd
Jun 03 20:49:13 Yamo-Legion5 kernel: usb 3-1: new high-speed USB device number 2 using xhci_hcd
Jun 03 20:49:13 Yamo-Legion5 kernel: usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd
Jun 03 20:49:13 Yamo-Legion5 kernel: usb 3-3: new full-speed USB device number 3 using xhci_hcd
Jun 03 20:49:13 Yamo-Legion5 kernel: usb 3-1.1: new full-speed USB device number 4 using xhci_hcd
Jun 03 20:49:13 Yamo-Legion5 kernel: usb 3-4: new full-speed USB device number 5 using xhci_hcd
Jun 03 20:49:17 Yamo-Legion5 NetworkManager[2610]: <info>  [1780508957.0604] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.56.1-1/libnm-device-plugin-bluetooth.so)
Jun 03 20:49:17 Yamo-Legion5 kernel: Bluetooth: Core ver 2.22
Jun 03 20:49:17 Yamo-Legion5 kernel: NET: Registered PF_BLUETOOTH protocol family
Jun 03 20:49:17 Yamo-Legion5 kernel: Bluetooth: HCI device and connection manager initialized
Jun 03 20:49:17 Yamo-Legion5 kernel: Bluetooth: HCI socket layer initialized
Jun 03 20:49:17 Yamo-Legion5 kernel: Bluetooth: L2CAP socket layer initialized
Jun 03 20:49:17 Yamo-Legion5 kernel: Bluetooth: SCO socket layer initialized
Jun 03 20:49:17 Yamo-Legion5 kernel: usbcore: registered new interface driver btusb
Jun 03 20:49:17 Yamo-Legion5 kernel: Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
Jun 03 20:49:17 Yamo-Legion5 kernel: Bluetooth: hci0: Boot Address: 0x24800
Jun 03 20:49:17 Yamo-Legion5 kernel: Bluetooth: hci0: Firmware Version: 193-33.24
Jun 03 20:49:17 Yamo-Legion5 kernel: Bluetooth: hci0: FW download error recovery failed (-19)
Jun 03 20:49:17 Yamo-Legion5 systemd[1]: /etc/systemd/system/bluetooth.service.d/override.conf:1: Assignment outside of section. Ignoring.
Jun 03 20:49:17 Yamo-Legion5 systemd[1]: Starting Bluetooth service...
Jun 03 20:49:17 Yamo-Legion5 (bluetoothd)[3726]: bluetooth.service: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
Jun 03 20:49:17 Yamo-Legion5 bluetoothd[3726]: Bluetooth daemon 5.86
Jun 03 20:49:17 Yamo-Legion5 systemd[1]: Started Bluetooth service.
Jun 03 20:49:17 Yamo-Legion5 systemd[1]: Reached target Bluetooth Support.
Jun 03 20:49:17 Yamo-Legion5 bluetoothd[3726]: Starting SDP server
Jun 03 20:49:17 Yamo-Legion5 bluetoothd[3726]: Bluetooth management interface 1.23 initialized
Jun 03 20:49:17 Yamo-Legion5 kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Jun 03 20:49:17 Yamo-Legion5 kernel: Bluetooth: BNEP filters: protocol multicast
Jun 03 20:49:17 Yamo-Legion5 kernel: Bluetooth: BNEP socket layer initialized
Jun 03 20:49:27 Yamo-Legion5 kernel: Bluetooth: hci0: Reading supported features failed (-110)
Jun 03 20:49:27 Yamo-Legion5 kernel: Bluetooth: hci0: Error reading debug features
Jun 03 20:49:27 Yamo-Legion5 kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
Jun 03 20:49:29 Yamo-Legion5 kernel: Bluetooth: hci0: Failed to read MSFT supported features (-110)
Jun 03 20:49:29 Yamo-Legion5 systemd[1]: Stopped target Bluetooth Support.
Jun 03 20:49:29 Yamo-Legion5 kernel: usb 3-3: new full-speed USB device number 6 using xhci_hcd
Jun 03 20:49:29 Yamo-Legion5 kernel: Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
Jun 03 20:49:29 Yamo-Legion5 kernel: Bluetooth: hci0: Device revision is 1
Jun 03 20:49:29 Yamo-Legion5 kernel: Bluetooth: hci0: Secure boot is enabled
Jun 03 20:49:29 Yamo-Legion5 kernel: Bluetooth: hci0: OTP lock is enabled
Jun 03 20:49:29 Yamo-Legion5 kernel: Bluetooth: hci0: API lock is enabled
Jun 03 20:49:29 Yamo-Legion5 kernel: Bluetooth: hci0: Debug lock is disabled
Jun 03 20:49:29 Yamo-Legion5 kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Jun 03 20:49:29 Yamo-Legion5 kernel: Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
Jun 03 20:49:29 Yamo-Legion5 kernel: Bluetooth: hci0: Boot Address: 0x24800
Jun 03 20:49:29 Yamo-Legion5 kernel: Bluetooth: hci0: Firmware Version: 193-33.24
Jun 03 20:49:31 Yamo-Legion5 kernel: Bluetooth: hci0: Waiting for firmware download to complete
Jun 03 20:49:31 Yamo-Legion5 kernel: Bluetooth: hci0: Firmware loaded in 1767016 usecs
Jun 03 20:49:31 Yamo-Legion5 kernel: Bluetooth: hci0: Waiting for device to boot
Jun 03 20:49:31 Yamo-Legion5 kernel: Bluetooth: hci0: Device booted in 14608 usecs
Jun 03 20:49:31 Yamo-Legion5 kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc
Jun 03 20:49:31 Yamo-Legion5 kernel: Bluetooth: hci0: Applying Intel DDC parameters completed
Jun 03 20:49:31 Yamo-Legion5 kernel: Bluetooth: hci0: Firmware revision 0.3 build 193 week 33 2024
Jun 03 20:49:31 Yamo-Legion5 kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
Jun 03 20:49:31 Yamo-Legion5 systemd[4003]: Reached target Bluetooth.
Jun 03 20:49:31 Yamo-Legion5 systemd[1]: Reached target Bluetooth Support.
Jun 03 20:49:31 Yamo-Legion5 bluetoothd[3726]: Battery Provider Manager created
Jun 03 20:49:31 Yamo-Legion5 kernel: Bluetooth: MGMT ver 1.23
Jun 03 20:49:31 Yamo-Legion5 bluetoothd[3726]: Failed to set default system config for hci0
Jun 03 20:49:32 Yamo-Legion5 NetworkManager[2610]: <info>  [1780508972.0130] manager: (04:79:70:EC:9C:0B): new Bluetooth device (/org/freedesktop/NetworkManager/Devices/7)
Jun 03 20:49:33 Yamo-Legion5 kernel: Bluetooth: RFCOMM TTY layer initialized
Jun 03 20:49:33 Yamo-Legion5 kernel: Bluetooth: RFCOMM socket layer initialized
Jun 03 20:49:33 Yamo-Legion5 kernel: Bluetooth: RFCOMM ver 1.11
Jun 03 20:49:33 Yamo-Legion5 bluetoothd[3726]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSource/ldac
Jun 03 20:49:33 Yamo-Legion5 bluetoothd[3726]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSink/aptx_hd
Jun 03 20:49:33 Yamo-Legion5 bluetoothd[3726]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSource/aptx_hd
Jun 03 20:49:33 Yamo-Legion5 bluetoothd[3726]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSink/aptx
Jun 03 20:49:33 Yamo-Legion5 bluetoothd[3726]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSource/aptx
Jun 03 20:49:33 Yamo-Legion5 bluetoothd[3726]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSink/aac
Jun 03 20:49:33 Yamo-Legion5 bluetoothd[3726]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSource/aac
Jun 03 20:49:33 Yamo-Legion5 bluetoothd[3726]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSink/opus_g
Jun 03 20:49:33 Yamo-Legion5 bluetoothd[3726]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSource/opus_g
Jun 03 20:49:33 Yamo-Legion5 bluetoothd[3726]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSink/sbc
Jun 03 20:49:33 Yamo-Legion5 bluetoothd[3726]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSource/sbc
Jun 03 20:49:33 Yamo-Legion5 bluetoothd[3726]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Jun 03 20:49:33 Yamo-Legion5 bluetoothd[3726]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Jun 03 20:49:33 Yamo-Legion5 bluetoothd[3726]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Jun 03 20:49:33 Yamo-Legion5 bluetoothd[3726]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Jun 03 20:49:33 Yamo-Legion5 bluetoothd[3726]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSource/faststream
Jun 03 20:49:33 Yamo-Legion5 bluetoothd[3726]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSource/faststream_duplex
Jun 03 20:49:33 Yamo-Legion5 bluetoothd[3726]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSink/opus_05
Jun 03 20:49:33 Yamo-Legion5 bluetoothd[3726]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSource/opus_05
Jun 03 20:49:33 Yamo-Legion5 bluetoothd[3726]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Jun 03 20:49:33 Yamo-Legion5 bluetoothd[3726]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Jun 03 20:49:42 Yamo-Legion5 systemd[4003]: Stopped target Bluetooth.
Jun 03 20:51:20 Yamo-Legion5 tlp[20526]: Enabling radios: bluetooth wifi.
Jun 03 20:57:10 Yamo-Legion5 systemd[7668]: Reached target Bluetooth.
Jun 03 20:57:11 Yamo-Legion5 bluetoothd[3726]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to 98:47:44:70:8C:93: Permission denied (13)

Here are the steps I have taken:

  1. Open the system
  2. My system opens the apps I use
  3. I unpair the headset as it was previously paired
  4. Pair it again
  5. it connects for 1-3 seconds and then I see that it gets disconnected and the audio is switched to the laptop’s speakers.

Update: As far as I got with debugging with Gemini (very horrible solutions provided by the LLM btw), apparently it’s a race condition indeed.
Here is what it mentioned

Look closely at this specific log:

> `kernel: Bluetooth: hci0: Firmware already loaded`

This is the smoking gun. When the system wakes up, the kernel sees the Bluetooth chip and says, "Oh, the firmware is already on it from before it went to sleep. I don't need to do anything." But because the chip lost power during suspend, that firmware state is corrupt/zombified.

Then, right at the end of the log when the system tries to actually use the Bluetooth radio to connect your headset:

> `kernel: Bluetooth: hci0: Opcode 0x0c1a failed: -112` *(Error -112 is Host is down)* `bluetoothd[3082]: Failed to set mode: Failed (0x03)` *(Hardware failure)*

The hardware has completely crashed because it's running zombified firmware.

For now it seems that sudo systemctl restart bluetooth fixes the problem, I will go ahead and create it in a wakeup script and hope it works, fingers crossed.

2 Likes