[SOLVED] bluetoothd crashes after attempt to reconnect in -current
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
bluetoothd crashes after attempt to reconnect in -current
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.
However, my system did not go to sleep/hybernate. The screen was just locked out, but otherwise the system was fully active. The laptop was on AC power and the inactivity was of just a few minutes.
Unfortunately, even after the latest updates and the reversal of elogind to 252, I'm still experiencing this issue. I now have to keep open a root terminal just for restarting bluetoothd after crashing.
UPDATE: After some thinking it seems that the culprit is bluez. I'm downgrading to 5.73 to see if this fixes the issue. I didn't want to use 5.74 since it lasted only two days and then it was replaced by 5.75. Let's see what happens.
Last edited by sombragris; 04-20-2024 at 05:17 PM.
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,646
Rep:
Quote:
Originally Posted by sombragris
Thanks for the info. This is consistent with my experience. I will wait for the fix, since my patching abilities are not that good.
Meanwhile, I can confirm that:
The issue still persists here after the latest -current changes; and
reverting to bluez-5.73 makes the issue disappear.
Therefore, barring an upcoming update, I respectfully request for bluez to be reverted to 5.73 until a suitable fix appears. Thanks!!
In case you want to try the patch follow the following steps:
Go to the github page concerning the bug. In the second last message you see the commit hash with the fix. Click it, then in the URL bar of your browser add ".patch" and you will get the patch in unified diff format. The URL should read https://github.com/bluez/bluez/commi...234c6dea.patch
cd to the downloaded bluez folder, copy or move the downloaded patch in this folder
Edit the bluez.SlackBuild. I would suggest you add a line right after the line "cd $PKGNAM-$VERSION || exit 1". Make the line look like "patch -p1 < b94f1be656f34ea1363f5566ef63b847234c6dea.patch"
Execute the SlackBuild, the package will be put in /tmp.
So far Bluetooth reconnect works again and no segfaults were apparent so far after upgrading to the patched bluez. So I'm marking this tentatively as solved.
Thank you Pat. Also thank you a lot @titopoquito for your instrctions regarding patching. I had no opportunity to apply them but they are very easy to follow and approachable.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.