Tumbleweed KDE and I changed the setting to enable at login in the applet. It was previously set to “Restore previous status” but it always disables it when I login.
Did you check the bluetooth service settings in YaST? It needs to be set to “at system start”.
YaST->Services
At reboot:
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
Active: active (running) since Sun 2024-01-14 11:56:05 EST; 25s ago
Docs: man:bluetoothd(8)
Main PID: 1568 (bluetoothd)
Status: “Running”
Tasks: 1 (limit: 4915)
CPU: 18ms
CGroup: /system.slice/bluetooth.service
└─1568 /usr/libexec/bluetooth/bluetoothd
bluetoothd[1568]: Endpoint registered: sender=:1.59 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
bluetoothd[1568]: Endpoint registered: sender=:1.59 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
bluetoothd[1568]: Endpoint registered: sender=:1.59 path=/MediaEndpoint/A2DPSource/faststream
bluetoothd[1568]: Endpoint registered: sender=:1.59 path=/MediaEndpoint/A2DPSource/faststream_duplex
bluetoothd[1568]: Endpoint registered: sender=:1.59 path=/MediaEndpoint/A2DPSink/opus_05
bluetoothd[1568]: Endpoint registered: sender=:1.59 path=/MediaEndpoint/A2DPSource/opus_05
bluetoothd[1568]: Endpoint registered: sender=:1.59 path=/MediaEndpoint/A2DPSink/opus_05_duplex
bluetoothd[1568]: Endpoint registered: sender=:1.59 path=/MediaEndpoint/A2DPSource/opus_05_duplex
bluetoothd[1568]: Failed to add UUID: Failed (0x03)
bluetoothd[1568]: Failed to add UUID: Failed (0x03)
Please also check
Systemsettings->Startup and Shutdown->Background Services->Bluetooth
Yast Services Bluetooth set “At Boot”
KDE System Settings Background Services Bluetooth checked and enabled
Can you tell how you re-enable Bluetooth after a boot?
Is that through the KDE applet
Or using something else?
Essentially yes, except I have to click on “show hidden icons” and then I didn’t know you could right click on those icons until just now, so i was left clicking on the Bluetooth icon and then checking “Enable Bluetooth” above my list of previously connected devices. Works fine once it’s enabled and on every other Distribution I’ve tried. I’m about to boot up a live TW disk and see what that does.
dmesg | grep “Bluetooth” (since it doesnt show up in lspci or lsusb)
8.226174] Bluetooth: Core ver 2.22
[ 8.226192] Bluetooth: HCI device and connection manager initialized
[ 8.226195] Bluetooth: HCI socket layer initialized
[ 8.226197] Bluetooth: L2CAP socket layer initialized
[ 8.226198] Bluetooth: SCO socket layer initialized
[ 8.356298] Bluetooth: hci0: Device revision is 0
[ 8.356301] Bluetooth: hci0: Secure boot is enabled
[ 8.356302] Bluetooth: hci0: OTP lock is enabled
[ 8.356302] Bluetooth: hci0: API lock is enabled
[ 8.356303] Bluetooth: hci0: Debug lock is disabled
[ 8.356303] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 8.356304] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38
[ 8.356356] Bluetooth: hci0: DSM reset method type: 0x00
[ 8.384587] Bluetooth: hci0: Found device firmware: intel/ibt-0040-0041.sfi
[ 8.384594] Bluetooth: hci0: Boot Address: 0x100800
[ 8.384595] Bluetooth: hci0: Firmware Version: 151-42.23
[ 8.410926] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 8.410929] Bluetooth: BNEP filters: protocol multicast
[ 8.410932] Bluetooth: BNEP socket layer initialized
[ 9.826880] Bluetooth: hci0: Waiting for firmware download to complete
[ 9.828291] Bluetooth: hci0: Firmware loaded in 1409866 usecs
[ 9.828453] Bluetooth: hci0: Waiting for device to boot
[ 9.844275] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[ 9.844286] Bluetooth: hci0: Device booted in 15599 usecs
[ 9.844527] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0040-0041.ddc
[ 9.847301] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 9.850222] Bluetooth: hci0: Firmware timestamp 2023.42 buildtype 1 build 73111
[ 9.923220] Bluetooth: MGMT ver 1.22
[ 23.700866] Bluetooth: RFCOMM TTY layer initialized
[ 23.700875] Bluetooth: RFCOMM socket layer initialized
[ 23.700878] Bluetooth: RFCOMM ver 1.11
This is from my running system not the live disk I said I would try in the previous post
Live TW disk doesn’t have bluetooth functionality
Does that mean that after boot up, when Bluetooth not works, Enable Bluetooth does not have the check mark? (And once the check mark is set it works)
Does this maybe help?
Thanks, that fixed it, I’ve never had to mess with that config file.
In summary :
nano ~/.config/bluedevilglobalrc
Change [Adapters] xx:xx:xx:xx:xx:xx_powered=false to
Adapters] xx:xx:xx:x:xx:xx_powered=true
I also added [Global] launchState=enable at the top, but unsure if necessary.
1 Like