Bug 2364618

Summary: [abrt] wireplumber: closure_invoke_notifiers(): wireplumber killed by SIGABRT
Product: [Fedora] Fedora Reporter: Yonatan <yonatan.el.amigo>
Component: wireplumberAssignee: Wim Taymans <wtaymans>
Status: NEW --- QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 42CC: francesco_papini, peter.hutterer, wtaymans, yonatan.el.amigo
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/2f1ec4c82b8567c380c5c8c08b52af5306f288c
Whiteboard: abrt_hash:97da67b310a0f277c83a7613a182542dd39b77c1;VARIANT_ID=;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: proc_pid_status
none
File: maps
none
File: limits
none
File: environ
none
File: open_fds
none
File: mountinfo
none
File: os_info
none
File: cpuinfo
none
File: core_backtrace
none
File: dso_list
none
File: var_log_messages
none
File: backtrace none

Description Yonatan 2025-05-07 00:09:58 UTC
Version-Release number of selected component:
wireplumber-0.5.8-1.fc42

Additional info:
reporter:       libreport-2.17.15
type:           CCpp
reason:         wireplumber killed by SIGABRT
journald_cursor: s=ca335a882dbd403ebb8737e60209e25a;i=3629b8;b=1f2e2eb8343f408d88c650a4230e46fc;m=36e91211d;t=6348071c5b478;x=204f18a6a858aeb
executable:     /usr/bin/wireplumber
cmdline:        /usr/bin/wireplumber
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/wireplumber.service
rootdir:        /
uid:            1000
kernel:         6.14.4-300.fc42.x86_64
package:        wireplumber-0.5.8-1.fc42
runlevel:       N 5
backtrace_rating: 4
crash_function: closure_invoke_notifiers

Truncated backtrace:
Thread no. 1 (29 frames)
 #7 closure_invoke_notifiers at ../gobject/gclosure.c:275
 #9 closure_invalidate_internal at ../gobject/gclosure.c:569
 #10 g_closure_invalidate at ../gobject/gclosure.c:600
 #11 destroy_closure_array at ../gobject/gobject.c:5260
 #12 g_data_set_internal at ../glib/gdataset.c:656
 #14 wp_portal_permissionstore_plugin_disable at ../modules/module-portal-permissionstore.c:207
 #15 wp_plugin_deactivate at ../lib/wp/plugin.c:144
 #17 wp_object_dispose at ../lib/wp/object.c:191
 #19 g_value_unset at ../gobject/gvalue.c:197
 #20 _wplua_gvalue_userdata___gc at ../modules/module-lua-scripting/wplua/userdata.c:60
 #21 precallC at /usr/src/debug/lua-5.4.7-3.fc42.x86_64/src/ldo.c:529
 #22 luaD_precall at /usr/src/debug/lua-5.4.7-3.fc42.x86_64/src/ldo.c:595
 #23 ccall at /usr/src/debug/lua-5.4.7-3.fc42.x86_64/src/ldo.c:635
 #24 luaD_callnoyield at /usr/src/debug/lua-5.4.7-3.fc42.x86_64/src/ldo.c:655
 #25 dothecall at /usr/src/debug/lua-5.4.7-3.fc42.x86_64/src/lgc.c:903
 #26 luaD_rawrunprotected at /usr/src/debug/lua-5.4.7-3.fc42.x86_64/src/ldo.c:144
 #27 luaD_pcall.constprop.0 at /usr/src/debug/lua-5.4.7-3.fc42.x86_64/src/ldo.c:957
 #28 GCTM at /usr/src/debug/lua-5.4.7-3.fc42.x86_64/src/lgc.c:923
 #29 callallpendingfinalizers at /usr/src/debug/lua-5.4.7-3.fc42.x86_64/src/lgc.c:953
 #30 luaC_freeallobjects at /usr/src/debug/lua-5.4.7-3.fc42.x86_64/src/lgc.c:1517
 #31 close_state at /usr/src/debug/lua-5.4.7-3.fc42.x86_64/src/lstate.c:276
 #32 wp_plugin_deactivate at ../lib/wp/plugin.c:144
 #34 wp_object_dispose at ../lib/wp/object.c:191
 #36 glib_autoptr_clear_GObject at /usr/include/glib-2.0/gobject/gobject-autocleanups.h:31
 #37 glib_autoptr_cleanup_GObject at /usr/include/glib-2.0/gobject/gobject-autocleanups.h:31
 #38 wp_registry_clear at ../lib/wp/private/registry.c:176
 #39 wp_core_dispose at ../lib/wp/core.c:401
 #41 daemon_clear at ../src/main.c:54
 #42 glib_auto_cleanup_WpDaemon at ../src/main.c:57


Potential duplicate: bug 2315888

Comment 1 Yonatan 2025-05-07 00:10:01 UTC
Created attachment 2088708 [details]
File: proc_pid_status

Comment 2 Yonatan 2025-05-07 00:10:03 UTC
Created attachment 2088709 [details]
File: maps

Comment 3 Yonatan 2025-05-07 00:10:04 UTC
Created attachment 2088710 [details]
File: limits

Comment 4 Yonatan 2025-05-07 00:10:05 UTC
Created attachment 2088711 [details]
File: environ

Comment 5 Yonatan 2025-05-07 00:10:07 UTC
Created attachment 2088712 [details]
File: open_fds

Comment 6 Yonatan 2025-05-07 00:10:08 UTC
Created attachment 2088713 [details]
File: mountinfo

Comment 7 Yonatan 2025-05-07 00:10:10 UTC
Created attachment 2088714 [details]
File: os_info

Comment 8 Yonatan 2025-05-07 00:10:11 UTC
Created attachment 2088715 [details]
File: cpuinfo

Comment 9 Yonatan 2025-05-07 00:10:12 UTC
Created attachment 2088716 [details]
File: core_backtrace

Comment 10 Yonatan 2025-05-07 00:10:14 UTC
Created attachment 2088717 [details]
File: dso_list

Comment 11 Yonatan 2025-05-07 00:10:15 UTC
Created attachment 2088718 [details]
File: var_log_messages

Comment 12 Yonatan 2025-05-07 00:10:17 UTC
Created attachment 2088719 [details]
File: backtrace

Comment 13 Denis Goddard 2026-01-23 23:12:41 UTC
Seems to happen only as of the latest wireplumber update, and only repro's when VirtualBox has a guest VM running (whether or not that VM has audio output enabled, FWIW)

Happens during BT connect phase


reporter:       libreport-2.17.15
type:           CCpp
reason:         wireplumber killed by SIGABRT
journald_cursor: s=0f18ff1927e74feda16cc0f424f12f8b;i=10724e67;b=60cb632873f64b99ad2d757334820f9a;m=1f3d47480;t=6491604344133;x=b50bbbc4bbf7d047
executable:     /usr/bin/wireplumber
cmdline:        /usr/bin/wireplumber
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/wireplumber.service
rootdir:        /
uid:            1000
kernel:         6.18.5-100.fc42.x86_64
package:        wireplumber-0.5.13-1.fc42
runlevel:       N 5
backtrace_rating: 4
crash_function: closure_invoke_notifiers

Comment 14 Francesco Papini 2026-01-26 10:14:02 UTC
I have the exactly same issue but my case, apparently, is not related to having a VM running or not.

Comment 15 woshi4ndy 2026-01-28 08:03:43 UTC
I connected Jabra headphones via Bluetooth. Started Mozilla Firefox. Opened meet.google.com. Entered the lobby of a meeting. Almost immediately the gnome session crashed forcing me to logout. It has not happened before. This is unique problem in my system. It's connected to crashes that I report previously to this one.


reporter:       libreport-2.17.15
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/wireplumber.service
crash_function: closure_invoke_notifiers
cmdline:        /usr/bin/wireplumber
type:           CCpp
comment:        I connected Jabra headphones via Bluetooth. Started Mozilla Firefox. Opened meet.google.com. Entered the lobby of a meeting. Almost immediately the gnome session crashed forcing me to logout. It has not happened before. This is unique problem in my system. It's connected to crashes that I report previously to this one.
journald_cursor: s=68373cea2a994392a71c5ca630deee6e;i=62b6ed3;b=f1ab43404793430eb582f99896f400c0;m=1311e7a1;t=6496df7132663;x=fa7d43b5b15b2da7
executable:     /usr/bin/wireplumber
rootdir:        /
backtrace_rating: 4
package:        wireplumber-0.5.13-1.fc42
runlevel:       N 5
uid:            1000
kernel:         6.18.6-100.fc42.x86_64
reason:         wireplumber killed by SIGABRT

Comment 16 Fedora Release Engineering 2026-05-06 12:51:27 UTC
This message is a reminder that Fedora Linux 42 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '42'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 42 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.