Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#56998 - [bluez-utils] bluetoothctl timeouts

Attached to Project: Arch Linux
Opened by Christian Rebischke (Shibumi) - Monday, 08 January 2018, 02:26 GMT
Task Type Bug Report
Category Packages: Extra
Status Assigned
Assigned To Andreas Radke (AndyRTR)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 2
Private No

Details

When I invoke bluetoothctl I only receive this message: "Waiting to connect to bluetoothd..."
My rfkill output looks like this:

ID TYPE DEVICE SOFT HARD
0 bluetooth tpacpi_bluetooth_sw unblocked unblocked
1 wlan phy0 unblocked unblocked

When i try to start the bluetooth.service nothing happens.
sudo systemctl status bluetooth.service says:

‚óŹ bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; disabled; vendor preset: disabled)
Active: inactive (dead)
Docs: man:bluetoothd(8)


When I strace bluetoothctl you can see that the bluetoothctl command is timeouting:
[...]
poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=5, events=POLLIN}], 3, 0) = 1 ([{fd=4, revents=POLLIN}])
recvmsg(4, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="l\2\1\1\0\0\0\0\7\0\0\0005\0\0\0\6\1s\0\7\0\0\0:1.1386\0"..., iov_len=2048}], msg_iovlen=1, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 72
recvmsg(4, {msg_namelen=0}, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=5, events=POLLIN}], 3, 0) = 0 (Timeout)
poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=5, events=POLLIN}], 3, -1
[...]

When I search through the journal I find this:
Jan 08 02:54:34 motoko dbus-daemon[464]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.


This task depends upon

Comment by Christian Rebischke (Shibumi) - Monday, 08 January 2018, 02:33 GMT
I breakdown the issue...

When I try to invoke bluetoothd manually I get this message:
D-Bus setup failed: Connection ":1.1404" is not allowed to own the service "org.bluez" due to security policies in the configuration file

I have no idea why systemctl status bluetooth didn't show me this message. Seems like there is an issue with the configuration file. Maybe /etc/dbus-1/system.d/bluetooth.conf?
Comment by Tomasz Cebula (tomaszc) - Thursday, 15 February 2018, 16:31 GMT
Maybe it's related to the kernel update from 4.13 to 4.14 or 4.15

You can check this by installing bluez-hid2hci and rebooting the system.
Does systemd-udevd take up 100% CPU?

This problem is described in more detail:
https://bbs.archlinux.org/viewtopic.php?id=232890
https://forum.manjaro.org/t/high-cpu-usage-on-kernel-4-14-and-4-15-from-systemd-udevd-which-seems-to-be-the-synaptic-touchpad-driver/35972
https://dev.solus-project.com/T5224

Maybe:
https://bugs.archlinux.org/task/57286
https://bugzilla.kernel.org/show_bug.cgi?id=197941

Loading...