You are not logged in.
System:
```
charmer@home-archer
-------------------
OS: Arch Linux x86_64
Kernel: 5.12.11-arch1-1
Shell: bash 5.1.8
Resolution: 2560x1600
DE: GNOME 40.2
WM: Mutter
CPU: AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx (8) @ 2.100GHz
GPU: AMD ATI 03:00.0 Picasso
Memory: 1467MiB / 14935MiB
```
Driver for bluetooth runs well:
```
07:47:17 charmer@home-archer ~ → lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 13d3:56ba IMC Networks Integrated Camera
Bus 003 Device 002: ID 0cf3:e300 Qualcomm Atheros Communications QCA61x4 Bluetooth 4.0
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2717:5001 Xiaomi Inc. MI wireless mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
```
No rfkill to bluetooth:
```
07:49:18 charmer@home-archer ~ → rfkill list
0: ideapad_wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
1: ideapad_bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
2: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
3: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
```
Systemd's log about bluetooth when login without doing anything:
```
07:48:04 charmer@home-archer ~ → sudo systemctl status bluetooth
[sudo] charmer 的密码:
○ bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; disabled; vendor preset: >
Active: inactive (dead)
Docs: man:bluetoothd(8)
```
Only error related to bluetooth:
```
07:51:14 charmer@home-archer ~ → sudo journalctl -b 0 | grep bluez
6月 18 19:42:24 home-archer dbus-daemon[366]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.58' (uid=1000 pid=1038 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo")
6月 18 19:42:24 home-archer dbus-daemon[366]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
6月 18 19:42:24 home-archer pulseaudio[1038]: GetManagedObjects() failed: org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.service not found.
6月 18 19:42:25 home-archer dbus-daemon[366]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.70' (uid=1000 pid=1178 comm="geary --gapplication-service ")
6月 18 19:42:25 home-archer dbus-daemon[366]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
6月 18 19:43:16 home-archer dbus-daemon[879]: [session uid=1000 pid=879] Activating via systemd: service name='org.bluez.obex' unit='dbus-org.bluez.obex.service' requested by ':1.82' (uid=1000 pid=1576 comm="gnome-control-center bluetooth ")
6月 18 19:43:16 home-archer dbus-daemon[879]: [session uid=1000 pid=879] Successfully activated service 'org.bluez.obex'
```
Situation:
Cannot toggle bluetooth in the gnome-control-center, and when login the bluetooth did not start, but I can start bluetooth by `systemd` manually.
When start gnome-control-center in terminal and switch to bluetooth panel, the log show:
```
(gnome-control-center:2963): Bluetooth-WARNING **: 19:53:21.886: Failed to register object:
```
Don't know how to fix this after browsing many website : (, and i don't know if it's a bug...
Last edited by OliverDD (2021-06-24 12:03:55)
Offline
What is your bluez version?
Offline
bluez-5.59-2
systemd 248 (248.3-2-arch)
+PAM +AUDIT -SELINUX -APPARMOR -IMA +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +XKBCOMMON +UTMP -SYSVINIT default-hierarchy=unified
gnome-control-center 40.0
Offline
Does downgrading to 5.58 help?
If not, try this gnome-control-center patch https://gitlab.gnome.org/GNOME/gnome-co … /996.patch
Offline
5.58 does not help
, thanks for replying. The second way seems reasonable, I would give it a try.
Offline
Weirdly enough, I had the same issue for the longest time, ever since the 5.9 kernel if I remember correctly, and I don't know what update did it, but it started working correctly again these days. It may sound like stupid advice, but check if updating your system helps.
and the universe said I love you
and the universe said the light you seek is within you
and the universe said you are not alone
and the universe said I love you because you are love
Offline
Supposedly bluez-5.59-2 fixes this but in his case, both are broken. So I suggested the gnome control center patch.
Offline
I always had this problem with GNOME personally. You probably know this already but I will just bring it up to any other newbie passing by having trouble with their gnome bluetooth utility.
So the best replicable and reliable solution that I have is for turning on bluetooth when on gnome is :
systemctl restart bluetooth
systemctl restart bluetoothdoing it 2 times always ensures that bluetooth will be turned on and then the gnome bluetooth utility can be used normally, even for shutting down the bluetooth service. (Yes doing the command once gave me unreliable result suprisingly enough)
Offline
Thanks for replying! It's bugs in gnome-control-center or bluez, to someone who browsing solution for this issue:
1. wait for updates of the bluez/gnome-control-center. And in the gap time, you can start the bluetooth manually by systemd.
2. install the patch given by @hussam in #4
I would close this topic. And I would like to wait for the merging of that patch ![]()
Thanks for reply, and have a good weekend.
Offline