Description of problem: Crashed when I resumed the laptop from sleep. Version-Release number of selected component: wireplumber-0.4.5-3.fc35 Additional info: reporter: libreport-2.15.2 backtrace_rating: 4 cmdline: /usr/bin/wireplumber crash_function: spa_bt_quirks_get_features executable: /usr/bin/wireplumber journald_cursor: s=2a1ea6f9af4f486cb63d72db1546e260;i=1b757;b=ea9dfa75d89b4e09afea31b2a46e6a7d;m=14606f90f9;t=5d541ee1d372c;x=dd29488c63af5cf5 kernel: 5.15.12-200.fc35.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #0 spa_bt_quirks_get_features at ../spa/plugins/bluez5/quirks.c:335 #1 device_update_hw_volume_profiles at ../spa/plugins/bluez5/bluez5-dbus.c:1269 #2 interface_added at ../spa/plugins/bluez5/bluez5-dbus.c:3465 #3 interfaces_added at ../spa/plugins/bluez5/bluez5-dbus.c:3509 #4 filter_cb at ../spa/plugins/bluez5/bluez5-dbus.c:3698 #7 dispatch_cb at ../spa/plugins/support/dbus.c:96 #8 loop_iterate at ../spa/plugins/support/loop.c:335 #9 wp_loop_source_dispatch at ../lib/wp/core.c:41 #12 g_main_context_iterate.constprop.0 at ../glib/gmain.c:4175
Created attachment 1849978 [details] File: backtrace
Created attachment 1849979 [details] File: cgroup
Created attachment 1849980 [details] File: core_backtrace
Created attachment 1849981 [details] File: cpuinfo
Created attachment 1849982 [details] File: dso_list
Created attachment 1849983 [details] File: environ
Created attachment 1849984 [details] File: exploitable
Created attachment 1849985 [details] File: limits
Created attachment 1849986 [details] File: maps
Created attachment 1849987 [details] File: mountinfo
Created attachment 1849988 [details] File: open_fds
Created attachment 1849989 [details] File: proc_pid_status
Created attachment 1849990 [details] File: var_log_messages
*** Bug 2039362 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Wake up from sleep reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/wireplumber.service cmdline: /usr/bin/wireplumber crash_function: spa_bt_quirks_get_features executable: /usr/bin/wireplumber journald_cursor: s=ef1ce73eeb814711bdc728d3aa59fcb3;i=140ff;b=bc0815f2af364022982aa1b60e459e92;m=1014ea526;t=5d57d4996733a;x=98a531a1b15c6ca1 kernel: 5.15.11-200.fc35.x86_64 package: wireplumber-0.4.5-3.fc35 reason: wireplumber killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: i have a bluetooth speaker in my home (bose bluetooth soundlink ii, in case it matters) and paired it with my fedora laptop. if it's in range when the laptop wakes from suspend, the crash occurs. in this case i had disconnected it (via gnome settings) before suspend, but wireplumber crashes on wake in either case. reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/wireplumber.service cmdline: /usr/bin/wireplumber crash_function: spa_bt_quirks_get_features executable: /usr/bin/wireplumber journald_cursor: s=6d009d86030847fa895f307fb69f0c87;i=163b63;b=1905f05279ab4798abdad854a7a1d5c6;m=25002852;t=5d5b06cb6aeff;x=e5df092b8b7d0252 kernel: 5.15.14-200.fc35.x86_64 package: wireplumber-0.4.7-2.fc35 reason: wireplumber killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 2041229 has been marked as a duplicate of this bug. ***
Happens to me as well, on every laptop resume from sleep.
*** Bug 2041253 has been marked as a duplicate of this bug. ***
*** Bug 2041256 has been marked as a duplicate of this bug. ***
I'd guess bug #2017984 and bug #2015749 are also related, although the call graph is different.
This is a race condition upon resuming. bluetoothd is restarting right after resume, and wireplumber tries to probe bluetooth adapters in the middle of daemon shut down. This might be a regression since KDE plasma bluetooth applet does not work after resuming, I have to restart either plasma or bluetoothd.
*** Bug 2041481 has been marked as a duplicate of this bug. ***
FEDORA-2022-5e4c355142 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-5e4c355142
Issue is not fixed with pipewire-0.3.43-2.fc35.
It crashes in another place now (gdb) bt #0 0x00007f08d0bd6b98 in spa_bt_device_supports_a2dp_codec () at /usr/lib64/spa-0.2/bluez5/libspa-bluez5.so #1 0x00007f08d0bd6d25 in spa_bt_device_get_supported_a2dp_codecs () at /usr/lib64/spa-0.2/bluez5/libspa-bluez5.so #2 0x00007f08d0bcd699 in set_initial_profile.lto_priv () at /usr/lib64/spa-0.2/bluez5/libspa-bluez5.so #3 0x00007f08d0bd1f70 in impl_init.lto_priv () at /usr/lib64/spa-0.2/bluez5/libspa-bluez5.so #4 0x00007f08e18d2ae1 in load_spa_handle.lto_priv () at /lib64/libpipewire-0.3.so.0 #5 0x00007f08e18d2e54 in pw_load_spa_handle () at /lib64/libpipewire-0.3.so.0 #6 0x00007f08e18ac349 in pw_context_load_spa_handle () at /lib64/libpipewire-0.3.so.0 #7 0x00007f08e1affef6 in wp_spa_device_new_from_spa_factory () at /lib64/libwireplumber-0.4.so.0 #8 0x00007f08d2864b0d in spa_device_new () at /usr/lib64/wireplumber-0.4/libwireplumber-module-lua-scripting.so #9 0x00007f08d27fec32 in luaD_precall () at /lib64/liblua-5.4.so #10 0x00007f08d2810a3a in luaV_execute () at /lib64/liblua-5.4.so #11 0x00007f08d27f4996 in f_call () at /lib64/liblua-5.4.so #12 0x00007f08d27f99f3 in luaD_rawrunprotected () at /lib64/liblua-5.4.so #13 0x00007f08d27fb674 in luaD_pcall () at /lib64/liblua-5.4.so #14 0x00007f08d27f028c in lua_pcallk () at /lib64/liblua-5.4.so #15 0x00007f08d2867b07 in _wplua_pcall () at /usr/lib64/wireplumber-0.4/libwireplumber-module-lua-scripting.so #16 0x00007f08d2867c52 in _wplua_closure_marshal () at /usr/lib64/wireplumber-0.4/libwireplumber-module-lua-scripting.so #17 0x00007f08e1a91c7f in g_closure_invoke () at /lib64/libgobject-2.0.so.0 #18 0x00007f08e1aae106 in signal_emit_unlocked_R () at /lib64/libgobject-2.0.so.0 #19 0x00007f08e1aaf9ca in g_signal_emit_valist () at /lib64/libgobject-2.0.so.0 #20 0x00007f08e1aafbe3 in g_signal_emit () at /lib64/libgobject-2.0.so.0 #21 0x00007f08e1aff9ff in spa_device_event_object_info () at /lib64/libwireplumber-0.4.so.0 #22 0x00007f08d0bd68a9 in emit_device_info.lto_priv () at /usr/lib64/spa-0.2/bluez5/libspa-bluez5.so #23 0x00007f08d0bfa0c7 in device_connected.isra () at /usr/lib64/spa-0.2/bluez5/libspa-bluez5.so #24 0x00007f08d0bddc70 in interfaces_added () at /usr/lib64/spa-0.2/bluez5/libspa-bluez5.so
The developer says this commit may help https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1122
FEDORA-2022-5e4c355142 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-5e4c355142` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-5e4c355142 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/67dcc0d29120572048f71fd40ab924a01ddd42fa This patch, from https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1122, fixes the issue. Please apply it.
FEDORA-2022-5e4c355142 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.