Bluetooth freezing in MATE

Every once in awhile I keep getting this error in MATE on Fedora 39, when connecting to Bluetooth and I have no clue what its telling me to fix.

The system will freeze for about 1 1/2 and then this error pops up:
What is it wanting fixed?
How do I fix it?

Screenshot at 2024-04-13 11-03-11

Thanks!

Does it look like, [2.4] [Bug] Turning on/off adapter (via status menu) doesn't change status switch and devices list · Issue #2318 · blueman-project/blueman · GitHub

thanks

| Joe Walker grumpey Paranoid Panda
April 14 |

  • | - |

Does it look like, [2.4] [Bug] Turning on/off adapter (via status menu) doesn’t change status switch and devices list · Issue #2318 · blueman-project/blueman · GitHub

thanks

Hi Joe,

No, my problem happens when I try to connect to my headphones.

Tia.

During or after the problem occurs can you take a look at:
systemctl status blue\*
systemctl --user status blue\*
journalctl -b -u blue\*
journalctl --user -b -u blue\*

It may also be useful to look at a short period of the full journal right after the problem happens.
journalctl --since -5m
journalctl --user --since -5m

| Joe Walker grumpey Paranoid Panda
April 15 |

  • | - |

During or after the problem occurs can you take a look at:
systemctl status blue\*
systemctl --user status blue\*
journalctl -b -u blue\*
journalctl --user -b -u blue\*

It may also be useful to look at a short period of the full journal right after the problem happens.
journalctl --since -5m
journalctl --user --since -5m

Hi Joe,

Okay I will have to wait until it happens again, before I can get the log for you.

Do you need the logs for all 6 commands or just 1?

Thanks!

If you are doing this right after it happens:
the first two systemctl commands and the last two journalctl commands.

Thanks

Okay it just happened!

Command 1: systemctl status blue*

bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: active (running) since Thu 2024-04-11 14:44:55 CDT; 6 days ago
Docs: man:bluetoothd(8)
Main PID: 1098 (bluetoothd)
Status: “Running”
Tasks: 1 (limit: 19002)
Memory: 1.8M
CPU: 9.404s
CGroup: /system.slice/bluetooth.service
└─1098 /usr/libexec/bluetooth/bluetoothd

Apr 17 15:16:57 ThinkCentre bluetoothd[1098]: /org/bluez/hci0/dev_00_11_67_11_1F_C0/sep1/fd24: fd(42) ready
Apr 17 15:17:51 ThinkCentre bluetoothd[1098]: /org/bluez/hci0/dev_00_11_67_11_1F_C0/sep1/fd25: fd(42) ready
Apr 17 15:18:04 ThinkCentre bluetoothd[1098]: Failed to disconnect device: Not Powered (0x0f)
Apr 17 15:18:04 ThinkCentre bluetoothd[1098]: Failed to disconnect device: Not Powered (0x0f)
Apr 17 15:18:17 ThinkCentre bluetoothd[1098]: /org/bluez/hci0/dev_00_11_67_11_1F_C0/sep1/fd26: fd(42) ready
Apr 17 15:18:46 ThinkCentre bluetoothd[1098]: src/service.c:btd_service_connect() a2dp-source profile connect failed for 40:F6:BC:EA:6>
Apr 17 15:18:46 ThinkCentre bluetoothd[1098]: /org/bluez/hci0/dev_40_F6_BC_EA_6D_33/sep2/fd27: fd(40) ready
Apr 17 15:19:20 ThinkCentre bluetoothd[1098]: Disconnecting failed: already disconnected
Apr 17 15:19:25 ThinkCentre bluetoothd[1098]: /org/bluez/hci0/dev_00_11_67_11_1F_C0/sep1/fd29: fd(42) ready
Apr 17 15:19:43 ThinkCentre bluetoothd[1098]: /org/bluez/hci0/dev_00_11_67_11_1F_C0/sep1/fd30: fd(42) ready

● bluetooth.target - Bluetooth Support
lines 1-26

● bluetooth.target - Bluetooth Support
Loaded: loaded (/usr/lib/systemd/system/bluetooth.target; static)
Active: active since Thu 2024-04-11 14:44:55 CDT; 6 days ago
Docs: man:systemd.special(7)

Apr 11 14:44:55 ThinkCentre systemd[1]: Reached target bluetooth.target - Bluetooth Support.
lines 6-31/31 (END)

Command 2:

chris@ThinkCentre:~$ systemctl --user status blue*
● bluetooth.target - Bluetooth
Loaded: loaded (/usr/lib/systemd/user/bluetooth.target; static)
Active: active since Thu 2024-04-11 15:11:21 CDT; 6 days ago
Docs: man:systemd.special(7)

Apr 11 15:11:21 ThinkCentre systemd[1747]: Reached target bluetooth.target - Bl>
lines 1-6/6 (END)

chris@ThinkCentre:~$ journalctl --since -5m
Apr 17 15:19:43 ThinkCentre bluetoothd[1098]: /org/bluez/hci0/dev_00_11_67_11_1>
Apr 17 15:19:43 ThinkCentre wireplumber[2108]: RFCOMM receive command but modem>
Apr 17 15:19:44 ThinkCentre wireplumber[2108]: RFCOMM receive command but modem>
Apr 17 15:19:44 ThinkCentre audit[166772]: SECCOMP auid=1000 uid=1000 gid=1000 >
Apr 17 15:19:44 ThinkCentre audit[166772]: SECCOMP auid=1000 uid=1000 gid=1000 >
Apr 17 15:19:44 ThinkCentre audit[166772]: SECCOMP auid=1000 uid=1000 gid=1000 >
Apr 17 15:19:44 ThinkCentre audit[166772]: SECCOMP auid=1000 uid=1000 gid=1000 >
Apr 17 15:19:47 ThinkCentre kernel: pcieport 0000:00:1c.0: AER: Correctable err>
Apr 17 15:19:47 ThinkCentre kernel: pcieport 0000:00:1c.0: PCIe Bus Error: seve>
Apr 17 15:19:47 ThinkCentre kernel: pcieport 0000:00:1c.0: device [8086:a295]>
Apr 17 15:19:47 ThinkCentre kernel: pcieport 0000:00:1c.0: [ 0] RxErr >
Apr 17 15:19:54 ThinkCentre audit[171845]: ANOM_ABEND auid=1000 uid=1000 gid=10>
Apr 17 15:19:54 ThinkCentre kernel: mate-notificati[171845]: segfault at 7fe9ce>
Apr 17 15:19:54 ThinkCentre kernel: Code: 01 00 00 00 4c 89 ce 48 89 e5 e8 1a e>
Apr 17 15:19:54 ThinkCentre audit: BPF prog-id=772 op=LOAD
Apr 17 15:19:54 ThinkCentre audit: BPF prog-id=773 op=LOAD
Apr 17 15:19:54 ThinkCentre audit: BPF prog-id=774 op=LOAD
Apr 17 15:19:54 ThinkCentre audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295>
Apr 17 15:19:54 ThinkCentre systemd[1]: Started systemd-coredump@31-172354-0.se>
Apr 17 15:19:54 ThinkCentre rtkit-daemon[1110]: Successfully made thread 169693>
Apr 17 15:19:55 ThinkCentre systemd-coredump[172355]: [🡕] Process 171845 (mate->

Module libnodoka.so from >
lines 1-23…skipping…
Apr 17 15:19:43 ThinkCentre bluetoothd[1098]: /org/bluez/hci0/dev_00_11_67_11_1F_C0/sep1/fd30: fd(42) ready
Apr 17 15:19:43 ThinkCentre wireplumber[2108]: RFCOMM receive command but modem not available: AT+CHLD=?
Apr 17 15:19:44 ThinkCentre wireplumber[2108]: RFCOMM receive command but modem not available: AT+CCWA=1
Apr 17 15:19:44 ThinkCentre audit[166772]: SECCOMP auid=1000 uid=1000 gid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0>
Apr 17 15:19:44 ThinkCentre audit[166772]: SECCOMP auid=1000 uid=1000 gid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0>
Apr 17 15:19:44 ThinkCentre audit[166772]: SECCOMP auid=1000 uid=1000 gid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0>
Apr 17 15:19:44 ThinkCentre audit[166772]: SECCOMP auid=1000 uid=1000 gid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0>
Apr 17 15:19:47 ThinkCentre kernel: pcieport 0000:00:1c.0: AER: Correctable error message received from 0000:00:1c.0
Apr 17 15:19:47 ThinkCentre kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Apr 17 15:19:47 ThinkCentre kernel: pcieport 0000:00:1c.0: device [8086:a295] error status/mask=00000001/00002000
Apr 17 15:19:47 ThinkCentre kernel: pcieport 0000:00:1c.0: [ 0] RxErr (First)
Apr 17 15:19:54 ThinkCentre audit[171845]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0>
Apr 17 15:19:54 ThinkCentre kernel: mate-notificati[171845]: segfault at 7fe9cee36fb5 ip 00007fee5320f441 sp 00007ffd9104e748 error 4 >
Apr 17 15:19:54 ThinkCentre kernel: Code: 01 00 00 00 4c 89 ce 48 89 e5 e8 1a e0 ff ff 5d 85 c0 0f 95 c0 0f b6 c0 c3 f3 0f 1e fa 48 85>
Apr 17 15:19:54 ThinkCentre audit: BPF prog-id=772 op=LOAD
Apr 17 15:19:54 ThinkCentre audit: BPF prog-id=773 op=LOAD
Apr 17 15:19:54 ThinkCentre audit: BPF prog-id=774 op=LOAD
Apr 17 15:19:54 ThinkCentre audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='u>
Apr 17 15:19:54 ThinkCentre systemd[1]: Started systemd-coredump@31-172354-0.service - Process Core Dump (PID 172354/UID 0).
Apr 17 15:19:54 ThinkCentre rtkit-daemon[1110]: Successfully made thread 169693 of process 169668 (/usr/libexec/webkit2gtk-4.1/WebKitW>
Apr 17 15:19:55 ThinkCentre systemd-coredump[172355]: [🡕] Process 171845 (mate-notificati) of user 1000 dumped core.

Module libnodoka.so from rpm mate-notification-daemon-1.26.1-2.fc39.x86_64
Module libdconfsettings.so from rpm dconf-0.40.0-9.fc39.x86_64
Module libgvfscommon.so from rpm gvfs-1.52.2-1.fc39.x86_64
Module libgvfsdbus.so from rpm gvfs-1.52.2-1.fc39.x86_64

Command 3:
chris@ThinkCentre:~$ journalctl --user --since -5m
Apr 17 15:21:23 ThinkCentre systemd[1747]: Starting blueman-manager.service - B>
Apr 17 15:21:23 ThinkCentre systemd[1747]: Started blueman-manager.service - Bl>
Apr 17 15:21:49 ThinkCentre systemd[1747]: Started dbus-:1.2-org.freedesktop.No>
lines 1-3/3 (END)…skipping…
Apr 17 15:21:23 ThinkCentre systemd[1747]: Starting blueman-manager.service - Bluetooth Manager…
Apr 17 15:21:23 ThinkCentre systemd[1747]: Started blueman-manager.service - Bluetooth Manager.
Apr 17 15:21:49 ThinkCentre systemd[1747]: Started dbus-:1.2-org.freedesktop.Notifications@263.service.
~

~

~

~

~

~

~

~

~

~

~

~

~

~

~

~

~

~

~

~

~

~

~

lines 1-3/3 (END)

Chris

CHRIS@CWM030.COM

Fedora 39 * MATE Desktop * On: Lenovo ThinkCentre M710Q

15 Gigs of Ram 1 TB SSD*

Apr 17 15:19:55 ThinkCentre systemd-coredump[172355]: [🡕] Process 171845 (mate-notificati) of user 1000 dumped core.

Can you check if this core file occurs each time you observe this issue?

Thanks

How?

Thanks!
Chris

CHRIS@CWM030.COM

Fedora 39 * MATE Desktop * On: Lenovo ThinkCentre M710Q
15 Gigs of Ram 1 TB SSD

coredumpctl in a terminal after it happens.

I sent that email on 4/17 and this is what the log shows for that day:

Wed 2024-04-17 15:19:55 CDT 171845 1000 1000 SIGSEGV present /usr/libexec/mate-notification-daemon 1.2M
Wed 2024-04-17 15:25:25 CDT 172541 1000 1000 SIGILL present /opt/vivaldi/vivaldi-bin 1010.6M
Wed 2024-04-17 15:26:43 CDT 173358 1000 1000 SIGSEGV present /usr/libexec/mate-notification-daemon 1.2M
Wed 2024-04-17 15:33:40 CDT 174675 1000 1000 SIGSEGV present /usr/libexec/mate-notification-daemon 637.6K
Wed 2024-04-17 15:35:02 CDT 174224 1000 1000 SIGILL present /opt/vivaldi/vivaldi-bin 522.1M
Wed 2024-04-17 15:35:04 CDT 174925 1000 1000 SIGSEGV present /usr/libexec/mate-notification-daemon 1.2M

Wed 2024-04-17 15:51:59 CDT 176106 1000 1000 SIGSEGV present /usr/libexec/mate-notification-daemon 635.3K

Wed 2024-04-17 18:18:18 CDT 180700 1000 1000 SIGSEGV present /usr/libexec/mate-notification-daemon 637.1K

Thanks!
Chris

CHRIS@CWM030.COM

Fedora 39 * MATE Desktop * On: Lenovo ThinkCentre M710Q
15 Gigs of Ram 1 TB SSD*

That does look like it’s crashing repeatedly. There are
you could open up a terminal and watch:
journalctl -f
or you could do coredumpctl and see if the time correlates to your issue.
It does look like there were some crashes reported in April:
https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&classification=Fedora&component=mate-notification-daemon&product=Fedora&product=Fedora%20EPEL

You may also want to check with the Mate folks to see if there something reported upstream.

journal -f only showed me what happened today.

I had already sent you the coredumpctl, but here it is again:

Tue 2024-04-16 07:41:51 CDT 128853 1000 1000 SIGSEGV present /opt/vivaldi/vivaldi-bin 39.2M
Tue 2024-04-16 09:31:22 CDT 131403 1000 1000 SIGILL present /opt/vivaldi/vivaldi-bin 3.6M
Tue 2024-04-16 09:31:23 CDT 131413 1000 1000 SIGILL present /opt/vivaldi/vivaldi-bin 3.5M
Tue 2024-04-16 09:31:23 CDT 131425 1000 1000 SIGILL present /opt/vivaldi/vivaldi-bin 5.0M
Tue 2024-04-16 09:31:27 CDT 131506 1000 1000 SIGILL present /opt/vivaldi/vivaldi-bin 4.9M
Tue 2024-04-16 09:31:27 CDT 131522 1000 1000 SIGILL present /opt/vivaldi/vivaldi-bin 3.6M
Tue 2024-04-16 09:31:33 CDT 131617 1000 1000 SIGILL present /opt/vivaldi/vivaldi-bin 5.0M
Tue 2024-04-16 09:31:35 CDT 131644 1000 1000 SIGILL present /opt/vivaldi/vivaldi-bin 3.6M
Tue 2024-04-16 09:31:36 CDT 131672 1000 1000 SIGILL present /opt/vivaldi/vivaldi-bin 5.0M
Tue 2024-04-16 09:31:37 CDT 131688 1000 1000 SIGILL present /opt/vivaldi/vivaldi-bin 3.6M
Tue 2024-04-16 10:42:14 CDT 136884 1000 1000 SIGSEGV present /usr/libexec/mate-notification-daemon 636.7K
Tue 2024-04-16 12:12:58 CDT 139870 1000 1000 SIGSEGV present /usr/libexec/mate-notification-daemon 637.4K
Wed 2024-04-17 15:19:55 CDT 171845 1000 1000 SIGSEGV present /usr/libexec/mate-notification-daemon 1.2M
Wed 2024-04-17 15:25:25 CDT 172541 1000 1000 SIGILL present /opt/vivaldi/vivaldi-bin 1010.6M
Wed 2024-04-17 15:26:43 CDT 173358 1000 1000 SIGSEGV present /usr/libexec/mate-notification-daemon 1.2M
Wed 2024-04-17 15:33:40 CDT 174675 1000 1000 SIGSEGV present /usr/libexec/mate-notification-daemon 637.6K
Wed 2024-04-17 15:35:02 CDT 174224 1000 1000 SIGILL present /opt/vivaldi/vivaldi-bin 522.1M
Wed 2024-04-17 15:35:04 CDT 174925 1000 1000 SIGSEGV present /usr/libexec/mate-notification-daemon 1.2M
Wed 2024-04-17 15:51:59 CDT 176106 1000 1000 SIGSEGV present /usr/libexec/mate-notification-daemon 635.3K
Wed 2024-04-17 18:18:18 CDT 180700 1000 1000 SIGSEGV present /usr/libexec/mate-notification-daemon 637.1K
Thu 2024-04-18 07:40:55 CDT 188534 1000 1000 SIGSEGV present /usr/libexec/mate-notification-daemon 1.3M
Thu 2024-04-18 07:54:32 CDT 190521 1000 1000 SIGSEGV present /opt/vivaldi/vivaldi-bin 39.4M
Fri 2024-04-19 13:17:42 CDT 230262 1000 1000 SIGSEGV present /usr/libexec/mate-notification-daemon 637.8K
Fri 2024-04-19 13:20:13 CDT 230569 1000 1000 SIGSEGV present /usr/libexec/mate-notification-daemon 1.2M
Fri 2024-04-19 19:14:52 CDT 243378 1000 1000 SIGSEGV present /usr/libexec/mate-notification-daemon 636.9K
Sat 2024-04-20 10:36:00 CDT 252990 1000 1000 SIGSEGV present /usr/libexec/mate-notification-daemon 636.7K
Sat 2024-04-20 12:37:01 CDT 256286 1000 1000 SIGSEGV present /usr/libexec/mate-notification-daemon 636.7K
Sat 2024-04-20 12:38:07 CDT 256450 1000 1000 SIGSEGV present /usr/libexec/mate-notification-daemon 1.2M
lines 168-193/193 (END)

Thanks,

Chris

CHRIS@CWM030.COM

Fedora 39 * MATE Desktop * On: Lenovo ThinkCentre M710Q

15 Gigs of Ram 1 TB SSD*