bluetoothd crashes after attempt to reconnect in -current
by sombragris from LinuxQuestions.org on (#6M4ED)
I got a Bluetooth keyboard that disconnects itself after a period of inactivity.
Someone rang the doorbell at home, I went to see who it was, and when I came back the screen was locked (after the timeout) as usual, but there was no way that my keyboard would reconnect.
After I unlocked Plasma, it became apparent that the Bluetooth daemon was no longer running. After passing Code:/etc/rc.d/rc.bluetooth restart to the root console, I was able to use my keyboard again.
The only clue I got were these two lines at /var/log/messages:
Code:apple 0005:05AC:024F.0009: input,hidraw5: BLUETOOTH HID v1.06 Keyboard [Keychron K10] on 30:24:32:bb:23:ac
bluetoothd[1218]: segfault at 38 ip 00000000004a3ade sp 00007ffffdb33790 error 4 in bluetoothd (deleted)[407000+cb000] likely on CPU 2 (core 2, socket 0)So it seems that the computer goes idle, the Bluetooth keyboard gets disconnected, and when it attempts to reconnect, bluetoothd segfaults.
Did anyone else noticed this issue? Any hints on a workaround?
I began to see this just after the updates of last week.
EDIT: Even after today's update to bluez, the issue persists.
Someone rang the doorbell at home, I went to see who it was, and when I came back the screen was locked (after the timeout) as usual, but there was no way that my keyboard would reconnect.
After I unlocked Plasma, it became apparent that the Bluetooth daemon was no longer running. After passing Code:/etc/rc.d/rc.bluetooth restart to the root console, I was able to use my keyboard again.
The only clue I got were these two lines at /var/log/messages:
Code:apple 0005:05AC:024F.0009: input,hidraw5: BLUETOOTH HID v1.06 Keyboard [Keychron K10] on 30:24:32:bb:23:ac
bluetoothd[1218]: segfault at 38 ip 00000000004a3ade sp 00007ffffdb33790 error 4 in bluetoothd (deleted)[407000+cb000] likely on CPU 2 (core 2, socket 0)So it seems that the computer goes idle, the Bluetooth keyboard gets disconnected, and when it attempts to reconnect, bluetoothd segfaults.
Did anyone else noticed this issue? Any hints on a workaround?
I began to see this just after the updates of last week.
EDIT: Even after today's update to bluez, the issue persists.