I’m currently having trouble with the Bluetooth module on my GIGABYTE GC-WB1733D-I (Bluetooth 5/Wireless AC 9260/160MHz Dual Band WiFi/Expansion Card)(Hardware Description from Gigabyte).
My system does recognize the adapter as a Bluetooth USB device and I can make connections, however, after about 5-10 minutes of usage, the device times out and becomes nonreactive. I can log out and log back in (or restart my system) and the adapter will work perfectly again, however, until doing that I cannot re-enable the service using the KDE GUI or systemctl commands.
lsusb | grep -i “blue” output
Bus 007 Device 003: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter
sudo modinfo btrtl output
filename: /lib/modules/6.1.10-1-default/kernel/drivers/bluetooth/btrtl.ko.zst
firmware: rtl_bt/rtl8852cu_config.bin
firmware: rtl_bt/rtl8852cu_fw.bin
firmware: rtl_bt/rtl8852bu_config.bin
firmware: rtl_bt/rtl8852bu_fw.bin
firmware: rtl_bt/rtl8852au_config.bin
firmware: rtl_bt/rtl8852au_fw.bin
firmware: rtl_bt/rtl8822b_config.bin
firmware: rtl_bt/rtl8822b_fw.bin
firmware: rtl_bt/rtl8821a_config.bin
firmware: rtl_bt/rtl8821a_fw.bin
firmware: rtl_bt/rtl8761a_config.bin
firmware: rtl_bt/rtl8761a_fw.bin
firmware: rtl_bt/rtl8723ds_config.bin
firmware: rtl_bt/rtl8723ds_fw.bin
firmware: rtl_bt/rtl8723bs_config.bin
firmware: rtl_bt/rtl8723bs_fw.bin
firmware: rtl_bt/rtl8723b_config.bin
firmware: rtl_bt/rtl8723b_fw.bin
firmware: rtl_bt/rtl8723a_fw.bin
license: GPL
version: 0.1
description: Bluetooth support for Realtek devices ver 0.1
author: Daniel Drake <drake@endlessm.com>
suserelease: openSUSE Tumbleweed
srcversion: 9F5808F54251CD9A089F889
depends: bluetooth
retpoline: Y
intree: Y
I took a capture of the dmesg output showing what occurs when the device fails.
[ 636.724827] Bluetooth: hci0: command 0x043d tx timeout
[ 665.241053] usb 7-1: reset full-speed USB device number 3 using ohci-pci
[ 712.848989] usb 7-1: reset full-speed USB device number 3 using ohci-pci
[ 715.921002] usb 7-1: reset full-speed USB device number 3 using ohci-pci
[ 728.412994] usb 7-1: reset full-speed USB device number 3 using ohci-pci
[ 731.352989] usb 7-1: reset full-speed USB device number 3 using ohci-pci
[ 768.293125] usb 7-1: reset full-speed USB device number 3 using ohci-pci
[ 786.365097] usb 7-1: reset full-speed USB device number 3 using ohci-pci
[ 795.165016] usb 7-1: reset full-speed USB device number 3 using ohci-pci
[ 798.253034] usb 7-1: reset full-speed USB device number 3 using ohci-pci
[ 842.344950] usb 7-1: reset full-speed USB device number 3 using ohci-pci
[ 852.112993] usb 7-1: reset full-speed USB device number 3 using ohci-pci
[ 858.048945] usb 7-1: reset full-speed USB device number 3 using ohci-pci
[ 861.121044] usb 7-1: reset full-speed USB device number 3 using ohci-pci
[ 891.754346] Bluetooth: hci0: link tx timeout
[ 891.754360] Bluetooth: hci0: killing stalled connection 07:bf:74:91:72:c7
[ 893.784943] Bluetooth: hci0: command 0x0406 tx timeout
[ 897.469025] usb 7-1: reset full-speed USB device number 3 using ohci-pci
[ 911.128930] usb 7-1: reset full-speed USB device number 3 using ohci-pci
[ 914.901050] Bluetooth: hci0: link tx timeout
[ 914.901065] Bluetooth: hci0: killing stalled connection 07:bf:74:91:72:c7
[ 928.692954] usb 7-1: reset full-speed USB device number 3 using ohci-pci
[ 931.772878] usb 7-1: reset full-speed USB device number 3 using ohci-pci
[ 934.800985] usb 7-1: reset full-speed USB device number 3 using ohci-pci
[ 937.620877] usb 7-1: reset full-speed USB device number 3 using ohci-pci
[ 941.192870] usb 7-1: reset full-speed USB device number 3 using ohci-pci
[ 947.056874] usb 7-1: reset full-speed USB device number 3 using ohci-pci
[ 956.292854] usb 7-1: reset full-speed USB device number 3 using ohci-pci
[ 965.396890] Bluetooth: hci0: command 0x0c03 tx timeout
[ 973.556842] Bluetooth: hci0: HCI reset during shutdown failed
[ 981.524814] Bluetooth: hci0: Opcode 0x c03 failed: -110
[ 982.004940] Bluetooth: hci0: urb 0000000079a11b98 failed to resubmit (113)
[ 983.540822] Bluetooth: hci0: Failed to read MSFT supported features (-110)
[ 1008.308820] Bluetooth: hci0: Opcode 0x c03 failed: -110
[ 1008.308841] Bluetooth: hci0: MSFT extension not registered
[ 1073.012789] Bluetooth: hci0: Opcode 0x c03 failed: -110
[ 1073.012809] Bluetooth: hci0: MSFT extension not registered
[ 1090.868867] Bluetooth: hci0: Opcode 0x c03 failed: -110
[ 1090.868883] Bluetooth: hci0: MSFT extension not registered
[ 1213.940739] Bluetooth: hci0: Opcode 0x c03 failed: -110
[ 1213.940756] Bluetooth: hci0: MSFT extension not registered
[ 1562.356296] Bluetooth: hci0: Opcode 0x c03 failed: -110
[ 1562.356305] Bluetooth: hci0: MSFT extension not registered
[ 1869.844004] Bluetooth: hci0: Opcode 0x c03 failed: -110
[ 1869.844021] Bluetooth: hci0: MSFT extension not registered
Any suggestions or tips regarding this issue are appreciated!
Output from journalctl -b 0 | grep -i “firmware” | grep -i “blue” is:
Feb 17 21:47:59 Kjell.home plasmashell[2038]: plasma-pk-updates: Got update package: "kernel-firmware-bluetooth;20230210-1.1;noarch;download.opensuse.org-oss_2" , summary: "Kernel firmware files for various Bluetooth drivers" , type: "enhancement"
Feb 19 11:52:36 localhost.localdomain plasmashell[2038]: plasma-pk-updates: Got update package: "kernel-firmware-bluetooth;20230210-1.1;noarch;download.opensuse.org-oss_2" , summary: "Kernel firmware files for various Bluetooth drivers" , type: "enhancement"
Additional output from journalctl -b 0 | grep -iE “blue|wifi|giga” when the last failure occured may be interesting:
Feb 17 06:26:10 Kjell.home systemd[1834]: Starting Blueman Applet...
Feb 17 06:26:10 Kjell.home systemd[1834]: app-blueman@autostart.service: Skipped due to 'exec-condition'.
Feb 17 06:26:10 Kjell.home systemd[1834]: Condition check resulted in Blueman Applet being skipped.
Feb 17 06:26:12 Kjell.home kded5[2019]: kf.bluezqt: PendingCall Error: "The name org.bluez.obex was not provided by any .service files"
Feb 17 06:26:19 Kjell.home systemd[1834]: Reached target Bluetooth.
Feb 17 06:36:10 Kjell.home wireplumber[2140]: Transport Acquire() failed for transport /org/bluez/hci0/dev_07_BF_74_91_72_C7/sep1/fd0 (Input/output error)
Feb 17 06:36:10 Kjell.home wireplumber[2140]: (bluez_output.07_BF_74_91_72_C7.1-19) suspended -> error (Start error: Input/output error)
Feb 17 06:36:12 Kjell.home plasmashell[2038]: org.kde.plasma.pulseaudio: No object for name "bluez_output.07_BF_74_91_72_C7.1"
Feb 17 06:36:53 Kjell.home wireplumber[2140]: (bluez_output.07_BF_74_91_72_C7.1-23) suspended -> error (Start error: Operation not permitted)
Feb 17 06:38:40 Kjell.home wireplumber[2140]: (bluez_output.07_BF_74_91_72_C7.1-23) suspended -> error (Start error: Operation not permitted)
Feb 17 06:40:12 Kjell.home wireplumber[2140]: (bluez_output.07_BF_74_91_72_C7.1-23) suspended -> error (Start error: Operation not permitted)
Feb 17 06:40:30 Kjell.home plasmashell[2038]: org.kde.plasma.pulseaudio: No object for name "bluez_input.07_BF_74_91_72_C7.0"
Feb 17 06:40:30 Kjell.home plasmashell[2038]: org.kde.plasma.pulseaudio: No object for name "bluez_output.07_BF_74_91_72_C7.1"
Feb 17 06:40:30 Kjell.home plasmashell[2038]: org.kde.plasma.pulseaudio: No object for name "bluez_input.07_BF_74_91_72_C7.0"
Feb 17 06:40:54 Kjell.home plasmashell[2038]: kf.bluezqt: PendingCall Error: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network conne
ction was broken."
Feb 17 06:41:35 Kjell.home plasmashell[2038]: kf.bluezqt: PendingCall Error: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network conne
ction was broken."
Feb 17 06:41:57 Kjell.home plasmashell[2038]: kf.bluezqt: PendingCall Error: ""
Feb 17 06:42:26 Kjell.home systemsettings[6484]: kf.bluezqt: PendingCall Error: "Authentication Failed"
Feb 17 06:43:29 Kjell.home sudo[6693]: katalyst : TTY=pts/1 ; PWD=/home/katalyst ; USER=root ; COMMAND=/usr/bin/systemctl restart bluetooth
Feb 17 06:43:30 Kjell.home kded5[2019]: kf.bluezqt: PendingCall Error: ""
Feb 17 06:43:49 Kjell.home systemsettings[6484]: kf.bluezqt: PendingCall Error: "Authentication Failed"
Feb 17 06:45:52 Kjell.home systemsettings[6484]: kf.bluezqt: PendingCall Error: "Authentication Failed"
Feb 17 06:51:40 Kjell.home systemsettings[6484]: kf.bluezqt: PendingCall Error: "Authentication Failed"
Feb 17 06:56:21 Kjell.home sudo[7896]: katalyst : TTY=pts/3 ; PWD=/home/katalyst ; USER=root ; COMMAND=/usr/bin/journalctl -b -t bluetoothd
Feb 17 06:56:48 Kjell.home systemsettings[6484]: kf.bluezqt: PendingCall Error: "Authentication Failed"
If you are asked to show a certain result please show what you were asked for (and not what you think might be a better option). People who try to help you don’t know your system and can’t see what you are doing (and mostly do not have crystal balls either). They purely have to rely on what you are showing and the answers you are providing to their questions …
The easiest way to answer an information request is to copy the command line you used, the complete result shown and the next empty command prompt from your terminal and paste it in your forums post (as “preformatted text”) e.g.
# uname -a
Linux SYSTEM01 6.1.12-1-default #1 SMP PREEMPT_DYNAMIC Wed Feb 15 05:31:41 UTC 2023 (373f017) x86_64 x86_64 x86_64 GNU/Linux
#
That is surprising!
Probably you miss-interpreted the “0” in -b 0 (that should be a zero!).
You can try
journalctl -b | grep luetooth
(zero is the default)
In case you want to do file transfer via bluetooth you need the package bluez-obexd and you have to enable/start the dbus-org.bluez.obex.service.
Why do you have bluemanandbluedevil5 installed? Which one are you using?
Alright, back to provide some more input!
The output from journalctl -b | grep luetooth is
localhost:~ # journalctl -b 0 | grep luetooth
Feb 20 21:44:24 localhost kernel: Bluetooth: Core ver 2.22
Feb 20 21:44:24 localhost kernel: Bluetooth: HCI device and connection manager initialized
Feb 20 21:44:24 localhost kernel: Bluetooth: HCI socket layer initialized
Feb 20 21:44:24 localhost kernel: Bluetooth: L2CAP socket layer initialized
Feb 20 21:44:24 localhost kernel: Bluetooth: SCO socket layer initialized
Feb 20 21:44:24 localhost kernel: Bluetooth: hci0: Found device firmware: intel/ibt-18-16-1.sfi
Feb 20 21:44:24 localhost kernel: Bluetooth: hci0: Boot Address: 0x40800
Feb 20 21:44:24 localhost kernel: Bluetooth: hci0: Firmware Version: 108-45.22
Feb 20 21:44:24 localhost kernel: Bluetooth: hci0: Firmware already loaded
Feb 20 21:44:29 localhost systemd[1]: Starting Bluetooth service...
Feb 20 21:44:29 localhost systemd[1116]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
Feb 20 21:44:29 localhost bluetoothd[1116]: Bluetooth daemon 5.66
Feb 20 21:44:29 localhost systemd[1]: Started Bluetooth service.
Feb 20 21:44:29 localhost systemd[1]: Reached target Bluetooth Support.
Feb 20 21:44:29 localhost bluetoothd[1116]: Starting SDP server
Feb 20 21:44:29 localhost kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Feb 20 21:44:29 localhost kernel: Bluetooth: BNEP filters: protocol multicast
Feb 20 21:44:29 localhost kernel: Bluetooth: BNEP socket layer initialized
Feb 20 21:44:29 localhost bluetoothd[1116]: Bluetooth management interface 1.22 initialized
Feb 20 21:44:29 localhost bluetoothd[1116]: Battery Provider Manager created
Feb 20 21:44:29 localhost dbus-daemon[1117]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.2' (uid=0 pid=1116 comm="/usr/libexec/bluetooth/bluetoothd")
Feb 20 21:44:29 localhost kernel: Bluetooth: MGMT ver 1.22
Feb 20 21:44:29 localhost bluetoothd[1116]: Admin Policy Set interface registered
Feb 20 21:44:29 localhost bluetoothd[1116]: Admin Policy Status interface registered
Feb 20 21:44:29 localhost bluetoothd[1116]: Adv Monitor Manager created with supported features:0x00000001, enabled features:0x00000001, max number of supported monitors:32, max number of supported patterns:16
Feb 20 21:44:29 localhost.localdomain NetworkManager[1299]: <info> [1676925869.6114] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.42.0/libnm-device-plugin-bluetooth.so)
Feb 20 21:44:48 localhost.localdomain kernel: Bluetooth: RFCOMM TTY layer initialized
Feb 20 21:44:48 localhost.localdomain kernel: Bluetooth: RFCOMM socket layer initialized
Feb 20 21:44:48 localhost.localdomain kernel: Bluetooth: RFCOMM ver 1.11
Feb 20 21:44:48 localhost.localdomain bluetoothd[1116]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSource/ldac
Feb 20 21:44:48 localhost.localdomain bluetoothd[1116]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSink/aptx_hd
Feb 20 21:44:48 localhost.localdomain bluetoothd[1116]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSource/aptx_hd
Feb 20 21:44:48 localhost.localdomain bluetoothd[1116]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSink/aptx
Feb 20 21:44:48 localhost.localdomain bluetoothd[1116]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSource/aptx
Feb 20 21:44:48 localhost.localdomain bluetoothd[1116]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSink/aac
Feb 20 21:44:48 localhost.localdomain bluetoothd[1116]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSource/aac
Feb 20 21:44:48 localhost.localdomain bluetoothd[1116]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSink/sbc
Feb 20 21:44:48 localhost.localdomain bluetoothd[1116]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSource/sbc
Feb 20 21:44:48 localhost.localdomain bluetoothd[1116]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSink/sbc_xq
Feb 20 21:44:48 localhost.localdomain bluetoothd[1116]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSource/sbc_xq
Feb 20 21:44:48 localhost.localdomain bluetoothd[1116]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Feb 20 21:44:48 localhost.localdomain bluetoothd[1116]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Feb 20 21:44:48 localhost.localdomain bluetoothd[1116]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Feb 20 21:44:48 localhost.localdomain bluetoothd[1116]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Feb 20 21:44:48 localhost.localdomain bluetoothd[1116]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSource/faststream
Feb 20 21:44:48 localhost.localdomain bluetoothd[1116]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSource/faststream_duplex
Feb 20 21:44:48 localhost.localdomain bluetoothd[1116]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSink/opus_05
Feb 20 21:44:48 localhost.localdomain bluetoothd[1116]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSource/opus_05
Feb 20 21:44:48 localhost.localdomain bluetoothd[1116]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Feb 20 21:44:48 localhost.localdomain bluetoothd[1116]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Feb 20 21:45:02 localhost.localdomain bluetoothd[1116]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
localhost:~ #
Thank you for the tip. I was going to look into this next so I’ve downloaded that package now.
I was trying to see if I had more success with blueman than bluedevil5, but my results were the same. I will remove blueman then since I am not using it.
Your thoughts and suggestions are much appreciated!
So I booted up today and found that my system wasn’t recognizing devices. I forced a bluetooth scan and this was the output. S2 is the headphones by the way.
That looks good to me provided that 07_BF_74_91_72_C7 is the device you want to connect.
If that is not the device you want to connect to can you try “bluetoothctl connect 07:BF:74:91:72:C7” (change the address to the device you want to connect). Please post the command and what comes after it.
Yes, that is the device I wanted to connect to, but the original issue is that some held or blocked process was originally blocking the connection until I issued those commands in bluetoothctl. I would prefer not to do this if not necessary.
I’m wondering if this line had anything to do with it.
In the beginning (as described in your post #1) your bluetooth-devices were recognized on startup, you could use them for ~10 minutes and then the connection would be terminated.
Now your bluetooth-devices are no longer recognized on startup, but work after you issue bluetoothctl scan. Does the connection then last or will it be terminated after some time?
I haven’t used the headphones since finding out this solution but will this week.
After some searching, I found this thread on github about a similiar issue with Home-Assistant. At the bottom of the thread, there is a link to another thread where someone is saying this is an issue with the Realtek driver interacting with the kernel.
I’ll provide another update after using this forced scan solution this week.
Nice solution. I’ve written the rule now and will check back in in one week if issues stopped occurring. Otherwise, it will be sooner
Is there a command that can show me if this rule is loaded into the kernel or not?
