Jimmy2027
n00b
Joined: 12 May 2020
Posts: 30
|
 Posted: Sat Feb 24, 2024 8:14 am Post subject: 'bluetoothctl' terminated by signal SIGSEGV |
 |
|
Bluetothctl started crashing, when I try to run it I get `'bluetoothctl' terminated by signal SIGSEGV (Address boundary error)`.
Dmesg gives me:
| Quote: |
[90258.178041] bluetoothctl[19163]: segfault at 8 ip 00007ff16296f093 sp 00007ffee7a34660 error 4 in libdbus-1.so.3.38.0[7ff162965000+2b000] likely on CPU 3 (core 4, socket
0)
[90258.178062] Code: 28 00 00 00 48 89 44 24 08 31 c0 48 c7 02 00 00 00 00 e8 80 66 ff ff 31 c9 48 89 e2 48 89 df 89 c6 e8 e1 c1 00 00 85 c0 74 35 <49> 8b 7c 24 08 e8 f3 71
ff ff 48 8b 34 24 49 8b bc 24 e8 00 00 00
[90259.188525] bluetoothctl[19172]: segfault at 8 ip 00007f71fa2de093 sp 00007ffdefdf4b60 error 4 in libdbus-1.so.3.38.0[7f71fa2d4000+2b000] likely on CPU 1 (core 0, socket
0)
[90259.188533] Code: 28 00 00 00 48 89 44 24 08 31 c0 48 c7 02 00 00 00 00 e8 80 66 ff ff 31 c9 48 89 e2 48 89 df 89 c6 e8 e1 c1 00 00 85 c0 74 35 <49> 8b 7c 24 08 e8 f3 71
ff ff 48 8b 34 24 49 8b bc 24 e8 00 00 00
[90260.198484] bluetoothctl[19175]: segfault at 8 ip 00007f4c9772a093 sp 00007ffcf790cbd0 error 4 in libdbus-1.so.3.38.0[7f4c97720000+2b000] likely on CPU 8 (core 16, socket 0)
[90260.198506] Code: 28 00 00 00 48 89 44 24 08 31 c0 48 c7 02 00 00 00 00 e8 80 66 ff ff 31 c9 48 89 e2 48 89 df 89 c6 e8 e1 c1 00 00 85 c0 74 35 <49> 8b 7c 24 08 e8 f3 71
ff ff 48 8b 34 24 49 8b bc 24 e8 00 00 00
[90262.098303] bluetoothctl[19223]: segfault at 8 ip 00007ff781d35093 sp 00007ffd52cf8bb0 error 4 in libdbus-1.so.3.38.0[7ff781d2b000+2b000] likely on CPU 10 (core 20, socket 0)
[90262.098319] Code: 28 00 00 00 48 89 44 24 08 31 c0 48 c7 02 00 00 00 00 e8 80 66 ff ff 31 c9 48 89 e2 48 89 df 89 c6 e8 e1 c1 00 00 85 c0 74 35 <49> 8b 7c 24 08 e8 f3 71
ff ff 48 8b 34 24 49 8b bc 24 e8 00 00 00
...
|
iwctl also doesn't start anymore but active connections still work and rc-status shows that both bluetooth and iwd services are alive and well.
After rebooting it works again until it crashes at some point...
Looking at the dmesg, I seems to be a d-bus issue, but I have no clue as to how to fix it. I'm starting dbus-launch in my .xinitrc:
| Code: |
while true
do
setbg
# update background every 5min
sleep 5m
done &
dunst &
xcompmgr &
dwmblocks &
redshift &
exec ssh-agent dbus-launch --exit-with-session dwm > ~/.dwm.log
|
The dbus service is also running. |
|
Other Things Gentoo
