this is not the issue, but this is:
press Fn+ the bluetooth key once and check, if nothing press it again and check
it was probably related to kernel … so unless you wont to downgrade it and test if it was really a kernel update …
BT key was one of my first ideas - bu there isn´t one… There’s only an antenna (I’ve tried and it’s for WIFI).
As for the Kernel downgrade, isn’t booting from another kernel the same effect? If so, already did it.
Downgraded it to 5.15 and 5.4 - and also upgraded it to 5.19. All the same.
thats not a downgrade, downgrade would be from kernel: 5.15.60-1 to 5.15.58-1 for example …
try these:
bluetoothctl power on
sudo rfkill block bluetooth
sudo rfkill unblock bluetooth
sudo systemctl restart bluetooth.service
post output from these if any
$ bluetoothctl power on
[CHG] Controller 5C:CD:5B:6A:10:89 Class: 0x007c010c
Changing power on succeeded
(but still the same)
the other cmds did not generated outputs… (the service restart did made the icon blink, but still the same)
Do you think I should try the kernel downgrade? I really don’t mind using an older kernel…
check if there was an bluez update:
cat /var/log/pacman.log | grep bluez
cat /var/log/pacman.log | grep bluez
[2021-04-01T11:03:03-0300] [ALPM] upgraded bluez (5.55-1 -> 5.56-1)
[2021-04-01T11:03:03-0300] [ALPM] upgraded bluez-libs (5.55-1 -> 5.56-1)
[2021-04-14T14:59:12-0300] [ALPM] upgraded bluez (5.56-1 -> 5.56-2)
[2021-04-14T14:59:12-0300] [ALPM] upgraded bluez-libs (5.56-1 -> 5.56-2)
[2021-04-19T18:50:58-0300] [ALPM] upgraded bluez (5.56-2 -> 5.58-1)
[2021-04-19T18:50:58-0300] [ALPM] upgraded bluez-libs (5.56-2 -> 5.58-1)
[2021-07-14T21:50:50-0300] [ALPM] upgraded bluez (5.58-1 -> 5.60-1)
[2021-07-14T21:50:50-0300] [ALPM] upgraded bluez-libs (5.58-1 -> 5.60-1)
[2021-09-10T20:36:18-0300] [ALPM] upgraded bluez (5.60-1 -> 5.61-1)
[2021-09-10T20:36:18-0300] [ALPM] upgraded bluez-libs (5.60-1 -> 5.61-1)
[2021-12-07T11:26:14-0300] [ALPM] upgraded bluez (5.61-1 -> 5.62-1)
[2021-12-07T11:26:14-0300] [ALPM] upgraded bluez-libs (5.61-1 -> 5.62-1)
[2022-01-25T19:21:25-0300] [ALPM] upgraded bluez (5.62-1 -> 5.63-1)
[2022-01-25T19:21:25-0300] [ALPM] upgraded bluez-libs (5.62-1 -> 5.63-1)
[2022-03-06T17:58:03-0300] [ALPM] upgraded bluez (5.63-1 -> 5.63-2)
[2022-03-06T17:58:03-0300] [ALPM] upgraded bluez-libs (5.63-1 -> 5.63-2)
[2022-04-15T10:48:35-0300] [ALPM] upgraded bluez (5.63-2 -> 5.64-2)
[2022-04-15T10:48:35-0300] [ALPM] upgraded bluez-libs (5.63-2 -> 5.64-2)
[2022-06-16T12:28:49-0300] [ALPM] installed bluez-utils (5.64-2)
[2022-08-25T23:11:01-0300] [ALPM] upgraded bluez (5.64-2 -> 5.65-2)
[2022-08-25T23:11:01-0300] [ALPM] upgraded bluez-libs (5.64-2 -> 5.65-2)
[2022-08-25T23:11:01-0300] [ALPM] upgraded bluez-utils (5.64-2 -> 5.65-2)
[2022-09-01T13:52:13-0300] [ALPM] reinstalled bluez (5.65-2)
[2022-09-01T13:53:12-0300] [PACMAN] Running 'pacman -Sy bluez'
[2022-09-01T13:53:16-0300] [ALPM] reinstalled bluez (5.65-2)
[2022-09-01T14:47:59-0300] [PACMAN] Running 'pacman -S bluez bluez-utils blueman'
[2022-09-01T14:48:01-0300] [ALPM] reinstalled bluez (5.65-2)
[2022-09-01T14:48:01-0300] [ALPM] reinstalled bluez-utils (5.65-2)
It looks like this may be it… Or am I super confident?
so if downgrading i would donwgrade this bluez package instead of kernel, but first try this:
edit again the grub file like you did above and add another parameter:
usbcore.autosuspend=-1
save it and update grub again:
sudo update-grub
reboot and see if it helped
1 Like
That did it!! 
It’s working!
TKS so much!!
youre welcome, and you dont have to mess with downgrading
1 Like
Hey @brahma , can you believe it stopped working again?
After rebooting, it started all over with the exact same behaviour… I read all your tips to try to figure out by my own, but I really don’t know ehat to do.
Grub is still with that same change you suggested.
did you were modifying grub?
check if the parameter is the same…
post output again from this:
systemctl status bluetooth
sudo dmesg | grep blue
journalctl -b0 -p5 --no-pager | grep blue
No updates, no changes. Just a reboot.
$ systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
Active: active (running) since Tue 2022-09-06 18:22:53 -03; 16h ago
Docs: man:bluetoothd(8)
Main PID: 2923 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 57459)
Memory: 1.0M
CPU: 357ms
CGroup: /system.slice/bluetooth.service
└─2923 /usr/lib/bluetooth/bluetoothd
set 06 18:22:53 manjaro2am bluetoothd[2923]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/sbc_xq_512
set 06 18:22:53 manjaro2am bluetoothd[2923]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/sbc_xq_552
set 06 18:22:53 manjaro2am bluetoothd[2923]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/sbc_xq_552
set 06 18:22:53 manjaro2am bluetoothd[2923]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down
set 06 18:22:55 manjaro2am bluetoothd[2923]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down
set 06 18:23:03 manjaro2am bluetoothd[2923]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down
set 06 18:23:23 manjaro2am bluetoothd[2923]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down
set 06 18:23:25 manjaro2am bluetoothd[2923]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down
set 06 18:23:31 manjaro2am bluetoothd[2923]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down
set 06 18:28:10 manjaro2am bluetoothd[2923]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down
$ sudo dmesg | grep blue
[ 16.403465] audit: type=1130 audit(1662499345.195:118): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=blueman-mechanism comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 44.920295] audit: type=1131 audit(1662499373.712:126): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 44.953551] audit: type=1130 audit(1662499373.745:127): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 113.007840] audit: type=1131 audit(1662499441.655:142): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=blueman-mechanism comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 361.783104] audit: type=1130 audit(1662499690.433:166): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=blueman-mechanism comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 391.825317] audit: type=1131 audit(1662499720.477:167): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=blueman-mechanism comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
$ journalctl -b0 -p5 --no-pager | grep blue
set 06 18:22:13 manjaro2am systemd[1112]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
set 06 18:22:22 manjaro2am pulseaudio[1535]: Could not find org.bluez.BatteryProviderManager1.RegisterBatteryProvider(), is bluetoothd started with experimental features enabled (-E flag)?
set 06 18:22:24 manjaro2am bluetoothd[1112]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down
set 06 18:22:25 manjaro2am kernel: audit: type=1130 audit(1662499345.195:118): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=blueman-mechanism comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
set 06 18:22:25 manjaro2am bluetoothd[1112]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down
set 06 18:22:26 manjaro2am daemon/bluetooth[2193]: adapter.go:186: failed to stop discovery for adapter manjaro2am [5C:CD:5B:6A:10:89]: Resource Not Ready
set 06 18:22:36 manjaro2am bluetoothd[1112]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down
set 06 18:22:37 manjaro2am daemon/bluetooth[2193]: adapter.go:186: failed to stop discovery for adapter manjaro2am [5C:CD:5B:6A:10:89]: Resource Not Ready
set 06 18:22:53 manjaro2am sudo[2913]: myara : TTY=pts/0 ; PWD=/home/myara ; USER=root ; COMMAND=/usr/bin/systemctl restart bluetooth.service
set 06 18:22:53 manjaro2am dbus-daemon[855]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.50" (uid=1000 pid=1535 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.26" (uid=0 pid=1112 comm="/usr/lib/bluetooth/bluetoothd")
set 06 18:22:53 manjaro2am dbus-daemon[855]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.50" (uid=1000 pid=1535 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.26" (uid=0 pid=1112 comm="/usr/lib/bluetooth/bluetoothd")
set 06 18:22:53 manjaro2am systemd[2923]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
set 06 18:22:53 manjaro2am kernel: audit: type=1131 audit(1662499373.712:126): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
set 06 18:22:53 manjaro2am kernel: audit: type=1130 audit(1662499373.745:127): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
set 06 18:22:53 manjaro2am pulseaudio[1535]: Could not find org.bluez.BatteryProviderManager1.RegisterBatteryProvider(), is bluetoothd started with experimental features enabled (-E flag)?
set 06 18:22:53 manjaro2am daemon/bluetooth[2193]: bluetooth.go:715:
set 06 18:22:53 manjaro2am bluetoothd[2923]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down
set 06 18:22:54 manjaro2am daemon/bluetooth[2193]: adapter.go:262: failed to start discovery for adapter manjaro2am [5C:CD:5B:6A:10:89]: Resource Not Ready
set 06 18:22:54 manjaro2am daemon/bluetooth[2193]: adapter.go:186: failed to stop discovery for adapter manjaro2am [5C:CD:5B:6A:10:89]: No discovery started
set 06 18:22:55 manjaro2am bluetoothd[2923]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down
set 06 18:22:56 manjaro2am daemon/bluetooth[2193]: adapter.go:186: failed to stop discovery for adapter manjaro2am [5C:CD:5B:6A:10:89]: Resource Not Ready
set 06 18:23:03 manjaro2am bluetoothd[2923]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down
set 06 18:23:04 manjaro2am daemon/bluetooth[2193]: adapter.go:186: failed to stop discovery for adapter manjaro2am [5C:CD:5B:6A:10:89]: Resource Not Ready
set 06 18:23:23 manjaro2am bluetoothd[2923]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down
set 06 18:23:24 manjaro2am daemon/bluetooth[2193]: adapter.go:186: failed to stop discovery for adapter manjaro2am [5C:CD:5B:6A:10:89]: No discovery started
set 06 18:23:25 manjaro2am bluetoothd[2923]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down
set 06 18:23:26 manjaro2am daemon/bluetooth[2193]: adapter.go:186: failed to stop discovery for adapter manjaro2am [5C:CD:5B:6A:10:89]: Resource Not Ready
set 06 18:23:31 manjaro2am bluetoothd[2923]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down
set 06 18:23:32 manjaro2am daemon/bluetooth[2193]: adapter.go:186: failed to stop discovery for adapter manjaro2am [5C:CD:5B:6A:10:89]: Resource Not Ready
set 06 18:24:01 manjaro2am kernel: audit: type=1131 audit(1662499441.655:142): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=blueman-mechanism comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
set 06 18:25:36 manjaro2am sudo[4137]: myara : TTY=pts/0 ; PWD=/home/myara ; USER=root ; COMMAND=/usr/lib/bluetooth/bluetoothd -n -d:
set 06 18:25:39 manjaro2am sudo[4144]: myara : TTY=pts/0 ; PWD=/home/myara ; USER=root ; COMMAND=/usr/lib/bluetooth/bluetoothd -n -d
set 06 18:25:39 manjaro2am bluetoothd[4145]: src/main.c:main() Unable to get on D-Bus
set 06 18:28:10 manjaro2am kernel: audit: type=1130 audit(1662499690.433:166): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=blueman-mechanism comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
set 06 18:28:10 manjaro2am bluetoothd[2923]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down
set 06 18:28:11 manjaro2am daemon/bluetooth[2193]: adapter.go:186: failed to stop discovery for adapter manjaro2am [5C:CD:5B:6A:10:89]: Resource Not Ready
set 06 18:28:40 manjaro2am kernel: audit: type=1131 audit(1662499720.477:167): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=blueman-mechanism comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Grub (no changes - at least none made manually):
its the same power down issue …
why do you have modified both the cmdline linux default and the cmdline linux in your grub?
Sorry for taking long… Kids at home today.
Didn’t got your question?
Was it about the grub picture? If so, just because it was edited on Notepadqq…
Oh, got you now… One of them was already like that when you originally suggested the change. I kept it unchanged.