when I diconnect my bluetooth headset I get the following error: Jan 14 10:28:27 localhost kernel: Bluetooth: hci0: SCO packet for unknown connection handle 257 Jan 14 10:28:29 localhost bluetoothd[16233]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107) Jan 14 10:28:29 localhost /usr/libexec/gdm-x-session[271868]: corrupted size vs. prev_size Jan 14 10:28:29 localhost /usr/libexec/gdm-x-session[271584]: (II) event17 - OpenComm2 by Shokz (AVRCP): device removed Jan 14 10:28:29 localhost acpid[1552]: input device has been disconnected, fd 22 Jan 14 10:28:29 localhost /usr/libexec/gdm-x-session[271584]: (II) config/udev: removing device OpenComm2 by Shokz (AVRCP) Jan 14 10:28:29 localhost /usr/libexec/gdm-x-session[271584]: (**) Option "fd" "69" Jan 14 10:28:29 localhost /usr/libexec/gdm-x-session[271584]: (II) UnloadModule: "libinput" Jan 14 10:28:29 localhost /usr/libexec/gdm-x-session[271584]: (II) systemd-logind: releasing fd for 13:81 Jan 14 10:28:29 localhost /usr/libexec/gdm-x-session[271584]: (EE) systemd-logind: failed to release device: Device not taken Jan 14 10:28:29 localhost systemd[1]: Started systemd-coredump@180-286075-0.service. Jan 14 10:28:29 localhost dbus-daemon[1554]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.20572" (uid=1000 pid=271556 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.1910" (uid=0 pid=16233 comm="/usr/libe> Jan 14 10:28:29 localhost pipewire-pulse[271557]: mod.protocol-pulse: 69: sink not ready: sample:0 map:0 volume:0 Jan 14 10:28:29 localhost pipewire-pulse[271557]: mod.protocol-pulse: 69: source not ready: sample:0 map:0 volume:0 Jan 14 10:28:29 localhost systemd-coredump[286077]: Removed old coredump core.bt-adapter.1000.7b9e0790a6634f659c7d475228ca81e2.270698.1736843941000000.zst. Jan 14 10:28:29 localhost systemd-coredump[286077]: [🡕] Process 271868 (mate-volume-con) of user 1000 dumped core. Stack trace of thread 271868: #0 0x00007f3e0b2934bc __pthread_kill_implementation (libc.so.6 + 0x854bc) #1 0x00007f3e0b244932 raise (libc.so.6 + 0x36932) #2 0x00007f3e0b230464 abort (libc.so.6 + 0x22464) #3 0x00007f3e0b287908 __libc_message (libc.so.6 + 0x79908) #4 0x00007f3e0b29c35a malloc_printerr (libc.so.6 + 0x8e35a) #5 0x00007f3e0b29cc4e unlink_chunk.constprop.0 (libc.so.6 + 0x8ec4e) #6 0x00007f3e0b29f5b2 _int_malloc (libc.so.6 + 0x915b2) #7 0x00007f3e0b2a005f __libc_malloc (libc.so.6 + 0x9205f) #8 0x00007f3e0b43f0c9 g_malloc (libglib-2.0.so.0 + 0x5f0c9) #9 0x00007f3e0b457f99 g_slice_alloc (libglib-2.0.so.0 + 0x77f99) #10 0x00007f3e0b433936 g_list_prepend (libglib-2.0.so.0 + 0x53936) #11 0x00007f3e0b42d577 g_key_file_add_group (libglib-2.0.so.0 + 0x4d577) #12 0x00007f3e0b42e88f g_key_file_flush_parse_buffer (libglib-2.0.so.0 + 0x4e88f) #13 0x00007f3e0b42ecc5 g_key_file_parse_data (libglib-2.0.so.0 + 0x4ecc5) #14 0x00007f3e0b42ef81 g_key_file_load_from_fd (libglib-2.0.so.0 + 0x4ef81) #15 0x00007f3e0b42f276 g_key_file_load_from_file (libglib-2.0.so.0 + 0x4f276) #16 0x00007f3e0ba4136e insert_theme (libgtk-3.so.0 + 0x1b736e) #17 0x00007f3e0ba41659 ensure_valid_themes (libgtk-3.so.0 + 0x1b7659) #18 0x00007f3e0ba43070 real_choose_icon (libgtk-3.so.0 + 0x1b9070) #19 0x00007f3e0ba43768 choose_icon (libgtk-3.so.0 + 0x1b9768) #20 0x00007f3e0ba3dc9e ensure_surface_for_gicon (libgtk-3.so.0 + 0x1b3c9e) #21 0x00007f3e0ba3e277 gtk_icon_helper_load_surface (libgtk-3.so.0 + 0x1b4277) #22 0x00007f3e0bc1c810 gtk_status_icon_update_image.isra.0 (libgtk-3.so.0 + 0x392810) #23 0x00000000004068e2 update_icon (mate-volume-control-status-icon + 0x68e2) #24 0x0000000000407181 gvc_stream_status_icon_set_control (mate-volume-control-status-icon + 0x7181) #25 0x0000000000407854 update_icon_input (mate-volume-control-status-icon + 0x7854) #26 0x00007f3e0b537260 g_closure_invoke (libgobject-2.0.so.0 + 0x16260) #27 0x00007f3e0b549826 signal_emit_unlocked_R.isra.0 (libgobject-2.0.so.0 + 0x28826) #28 0x00007f3e0b550516 g_signal_emit_valist (libgobject-2.0.so.0 + 0x2f516) #29 0x00007f3e0b550682 g_signal_emit (libgobject-2.0.so.0 + 0x2f682) #30 0x00007f3e0b53afb4 g_object_dispatch_properties_changed (libgobject-2.0.so.0 + 0x19fb4) #31 0x00007f3e0b53dd01 g_object_notify_by_pspec (libgobject-2.0.so.0 + 0x1cd01) Sometimes mate asks if it should reload the volume control, but sometimes not.
It could be related to https://github.com/mate-desktop/mate-media/issues/167
CC: (none) => geiger.david68210
new libmatemixer-1.26.1-1.mga9 in Core/Updates_testing repo should fix this issue!
thx. I'll check that.
I can confirm the new version prevents the crash. Tested on 2 PCs.
Setting bug fields, so more of QA can test this, and get advisory. Assuming tests was on x86_64, setting it OK so. Waiting a bit before validating if someone wants to check more and on 32 bit.
Source RPM: mate-media => libmatemixerWhiteboard: (none) => MGA9-64-OKAssignee: bugsquad => qa-bugsCC: (none) => fri
Packages in 9/Core/Updates_testing: ====================== libmatemixer0-1.26.1-1.mga9 lib64matemixer0-1.26.1-1.mga9 libmatemixer-devel-1.26.1-1.mga9 lib64matemixer-devel-1.26.1-1.mga9 matemixer-backend-pulse-1.26.1-1.mga9 matemixer-backend-alsa-1.26.1-1.mga9 matemixer-backend-oss-1.26.1-1.mga9 From SRPMS libmatemixer-1.26.1-1.mga9.src.rpm
Keywords: (none) => advisory
mga9, x64 Using pulseaudio here. Have not been able to reproduce this problem before or after the bluetooth connection is made and later closed. Volume control via the panel and mouse-wheel scrolling. Clean update of the 64-bit packages. Afterwards bluetooth and audio continued to function normally using the panel applet as before. Bluetooth audio disconnected by switching off the external audio device. Are you in a position to run this yourself Marc? That would be the acid test.
CC: (none) => tarazed25
Yes, that is what I tested. I've already switched to pipewire and using the pulseaudio component. Before this update, the mixer crashed sometimes after disconnection. After the update it stays and is still functional
Same situation - or about - as Len: I have no bluetooth headset, so connected my smartphone, had volume control open in MATE, transfered a small file to the smartphone that was accepted. So pretty sure the connection was active. At the smartphone interrupted the connection, nothing happened on the volume control. Not further persuing this as I cann't confirm the update would resolve a problem which does not exist for me.
CC: (none) => herman.viaene
x86_64 mate paired to bluetooth sound bar. played a media stream -ok unpowered sound bar - mate volume no issue repair soundbar, restart media stream and disconnect via system tray app - no issue with vol control apply update: lib64matemixer0-1.26.1-1.mga9 matemixer-backend-pulse-1.26.1-1.mga9 unpair and remove bluetooth device. re-pair device and start a new stream. disconnect bluetooth device and mate volume disappears from system tray. NOT OK for me!
CC: (none) => westel
Keywords: (none) => feedbackWhiteboard: MGA9-64-OK => (none)
note: unable to test i586 as the bluetooth device will not pair. ( same hardware as x86_64)
Thats unfortunate i586 do not work. Is it expected to have problen on i586, or is this a new bug?
(In reply to Ben McMonagle from comment #10) > x86_64 mate > > paired to bluetooth sound bar. > played a media stream -ok > unpowered sound bar - mate volume no issue > repair soundbar, restart media stream and disconnect via system tray app - > no issue with vol control > > apply update: > > lib64matemixer0-1.26.1-1.mga9 > matemixer-backend-pulse-1.26.1-1.mga9 > > unpair and remove bluetooth device. > re-pair device and start a new stream. > > disconnect bluetooth device and mate volume disappears from system tray. > > NOT OK for me! I don't know if is wise test on the fly with this kind of updates at less need to close and open the session again could you give it other try, thank you
Yes, please test after restarting the desktop session. (or rebooting)
(In reply to Morgan Leijström from comment #14) > Yes, please test after restarting the desktop session. > (or rebooting) yes, I rebooted the system, but no joy
and today, being a different day. x86_64 works fine. unable to force a crash while streaming to the sound bar.
an as it is again a different day: i686 system - paired bluetooth sound bar without issue. attempt to re-create issue - works fine. update packages: (medium "QA Testing (32-bit)") libmatemixer0 1.26.1 1.mga9 i586 matemixer-backend-pulse 1.26.1 1.mga9 i586 reboot steam to bluetooth soundbar without issue. attempt to force issue - unable to.
Whiteboard: (none) => MGA9-64-OK | MGA9-32-OK
CC: (none) => andrewsfarmKeywords: feedback => (none)
Maddening sometimes, isn't it, Ben? Validating.
CC: (none) => sysadmin-bugsKeywords: (none) => validated_update
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2025-0007.html
Status: NEW => RESOLVEDResolution: (none) => FIXED