Bluetooth gets disabled after unlocking of screen

See Lock screen and wifi are broken
basically, when I lock the screen and unlock it, I get "No bluetooth adapters found". Manually starting bluetooth gives me:

bluetoothd[3069]: src/main.c:parse_config() parsing /etc/bluetooth/main.conf
bluetoothd[3069]: src/main.c:parse_config() Key file does not have key “DiscoverableTimeout” in group “General”
bluetoothd[3069]: src/main.c:parse_config() Key file does not have key “AlwaysPairable” in group “General”
bluetoothd[3069]: src/main.c:parse_config() Key file does not have key “PairableTimeout” in group “General”
bluetoothd[3069]: src/main.c:parse_config() Key file does not have key “Privacy” in group “General”
bluetoothd[3069]: src/main.c:parse_config() Key file does not have key “JustWorksRepairing” in group “General”
bluetoothd[3069]: src/main.c:parse_config() Key file does not have key “Name” in group “General”
bluetoothd[3069]: src/main.c:parse_config() Key file does not have key “Class” in group “General”
bluetoothd[3069]: src/main.c:parse_config() Key file does not have key “DeviceID” in group “General”
bluetoothd[3069]: src/main.c:parse_config() Key file does not have key “ReverseServiceDiscovery” in group “General”
bluetoothd[3069]: src/main.c:parse_config() Key file does not have key “Cache” in group “GATT”
bluetoothd[3069]: src/main.c:parse_config() Key file does not have key “KeySize” in group “GATT”
bluetoothd[3069]: src/main.c:parse_config() Key file does not have key “ExchangeMTU” in group “GATT”
bluetoothd[3069]: src/main.c:parse_config() Key file does not have key “Channels” in group “GATT”
D-Bus setup failed: Connection ":1.321" is not allowed to own the service "org.bluez" due to security policies in the configuration file
bluetoothd[3069]: Unable to get on D-Bus

inxi -Fzzz:

System:    Host: robotic Kernel: 5.4.28-1-MANJARO x86_64 bits: 64 Desktop: KDE Plasma 5.18.3 Distro: Manjaro Linux 
Machine:   Type: Laptop System: LENOVO product: 2325S3E v: ThinkPad X230 serial: <filter> 
           Mobo: LENOVO model: 2325S3E serial: <filter> UEFI [Legacy]: LENOVO v: G2ET92WW (2.52 ) date: 02/22/2013 
Battery:   ID-1: BAT0 charge: 17.7 Wh condition: 17.8/25.9 Wh (69%) 
CPU:       Topology: Dual Core model: Intel Core i5-3320M bits: 64 type: MT MCP L2 cache: 3072 KiB 
           Speed: 1578 MHz min/max: 1200/3300 MHz Core speeds (MHz): 1: 1272 2: 1248 3: 1290 4: 1243 
Graphics:  Device-1: Intel 3rd Gen Core processor Graphics driver: i915 v: kernel 
           Display: x11 server: X.Org 1.20.8 driver: modesetting resolution: 1920x1200~60Hz 
           OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile v: 4.2 Mesa 19.3.5 
Audio:     Device-1: Intel 7 Series/C216 Family High Definition Audio driver: snd_hda_intel 
           Sound Server: ALSA v: k5.4.28-1-MANJARO 
Network:   Device-1: Intel 82579LM Gigabit Network driver: e1000e 
           IF: enp0s25 state: down mac: <filter> 
           Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi 
           IF: wlp3s0 state: up mac: <filter> 
Drives:    Local Storage: total: 122.99 GiB used: 32.53 GiB (26.4%) 
           ID-1: /dev/sda vendor: Toshiba model: THNSNF128GCSS size: 119.24 GiB 
           ID-2: /dev/sdb type: USB model: General UDisk size: 3.75 GiB 
Partition: ID-1: / size: 116.87 GiB used: 32.53 GiB (27.8%) fs: ext4 dev: /dev/sda1 
Sensors:   System Temperatures: cpu: 82.0 C mobo: 0.0 C 
           Fan Speeds (RPM): cpu: 4632 
Info:      Processes: 229 Uptime: 2h 11m Memory: 7.48 GiB used: 3.22 GiB (43.1%) Shell: zsh inxi: 3.0.37 

Oh, turns out I wasn't running bluetoothd as sudo after login. new error: https://hastebin.com/fuzumutuhe.cs

note that the respective errors, with/without sudo, come up even before lock. strange.
a solution to this might be to change the lock manager to the one used in xfce (since xfce works) but I dont know how.

another pattern:

  • Super+L locks the screen but does not turn the screen off-Bluetooth works here.
  • Fn+L also turns off the screen after locking it - this is where the problem happens

Check TLP settings, or check this

1 Like

Will try when I get time. thank you :slight_smile:

fail,no change
i used

VENDOR="0a5c"
PRODUCT="21e6"

since lsusb said Bus 001 Device 005: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad] as the only bluetooth related thing. full lsusb:

Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 006: ID 5986:02d2 Acer, Inc 
Bus 001 Device 005: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad]
Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF advanced mode)
Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

yes, i rebooted

How would i check tlp settings?

I think you can install tlpui package and check things with it and do the required changes.

Whoa, this is a lot-not sure which one to do

Look at the USB and where is connected the bluetooth. Or at Radio and Radio wizard. You should be able to tweak things ... but since i don't use that i can't give direct indications.
Maybe also this will help, and instead sleep, is just lock, so you will have to change that.

That's for boot, bluetooth works on boot, just not after lock, I'll still check it out.

will see what i can do

wait could this be relevant
image

1 Like

So do you suggest I try toggling it?

Yes, that is what i would do. :slight_smile: That was my :+1: for. You can always toggle back if has no positive effect.

1 Like

no effect, even after reboot. should I toggle back or is it safe to leave it there?

After countless debugging help from @tbg and @bogdancovaciu I found the culprit!!
It is the bluetooth autoenable setting :confused:
The problem is that I want it to be enabled on boot, so I may log in with my bluetooth keyboard.
Any suggestions?

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by