Bug 2230265

Summary: [abrt] wireplumber: loop_iterate(): wireplumber killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Tim Waugh <twaugh>
Component: wireplumberAssignee: Wim Taymans <wtaymans>
Status: CLOSED EOL QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 38CC: peter.hutterer, twaugh, wtaymans
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/9df06dd5fff90445cc949738550563163a9991e
Whiteboard: abrt_hash:8d3705954e9c91adede42341076aa5f5ef83a100;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-05-28 13:47:18 UTC 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: mountinfo
none
File: exploitable
none
File: os_info
none
File: maps
none
File: open_fds
none
File: cpuinfo
none
File: limits
none
File: core_backtrace
none
File: dso_list
none
File: backtrace
none
File: proc_pid_status
none
File: var_log_messages
none
File: environ none

Description Tim Waugh 2023-08-09 08:23:10 UTC
Version-Release number of selected component:
wireplumber-0.4.14-1.fc38

Additional info:
reporter:       libreport-2.17.11
rootdir:        /
kernel:         6.4.7-200.fc38.x86_64
type:           CCpp
cmdline:        /usr/bin/wireplumber
crash_function: loop_iterate
backtrace_rating: 4
package:        wireplumber-0.4.14-1.fc38
reason:         wireplumber killed by SIGSEGV
journald_cursor: s=d6a1c99bf81a410b85bfca856285f5a4;i=3f296b;b=526415cf610f46e88137b4e00c390bbd;m=16ee29022;t=6026a6adc3dfc;x=b0ffc83ccc497ba7
runlevel:       N 5
uid:            1000
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/wireplumber.service
executable:     /usr/bin/wireplumber

Truncated backtrace:
Thread no. 1 (3 frames)
 #0 loop_iterate at ../spa/plugins/support/loop.c:469
 #1 wp_loop_source_dispatch at ../lib/wp/core.c:42
 #4 g_main_context_iterate.isra.0 at ../glib/gmain.c:4276

Comment 1 Tim Waugh 2023-08-09 08:23:14 UTC
Created attachment 1982516 [details]
File: mountinfo

Comment 2 Tim Waugh 2023-08-09 08:23:15 UTC
Created attachment 1982517 [details]
File: exploitable

Comment 3 Tim Waugh 2023-08-09 08:23:17 UTC
Created attachment 1982518 [details]
File: os_info

Comment 4 Tim Waugh 2023-08-09 08:23:19 UTC
Created attachment 1982519 [details]
File: maps

Comment 5 Tim Waugh 2023-08-09 08:23:21 UTC
Created attachment 1982520 [details]
File: open_fds

Comment 6 Tim Waugh 2023-08-09 08:23:22 UTC
Created attachment 1982521 [details]
File: cpuinfo

Comment 7 Tim Waugh 2023-08-09 08:23:24 UTC
Created attachment 1982522 [details]
File: limits

Comment 8 Tim Waugh 2023-08-09 08:23:25 UTC
Created attachment 1982523 [details]
File: core_backtrace

Comment 9 Tim Waugh 2023-08-09 08:23:27 UTC
Created attachment 1982524 [details]
File: dso_list

Comment 10 Tim Waugh 2023-08-09 08:23:29 UTC
Created attachment 1982525 [details]
File: backtrace

Comment 11 Tim Waugh 2023-08-09 08:23:30 UTC
Created attachment 1982526 [details]
File: proc_pid_status

Comment 12 Tim Waugh 2023-08-09 08:23:32 UTC
Created attachment 1982527 [details]
File: var_log_messages

Comment 13 Tim Waugh 2023-08-09 08:23:34 UTC
Created attachment 1982528 [details]
File: environ

Comment 14 Anthony Byrne 2023-08-10 18:19:48 UTC
I opened Google Meet in Firefox, which attempted to use my USB headset speaker and microphone (connected via ThinkPad  USB-C dock). When I realized I could not say or hear anything in the meeting, I checked the Sound menu in System Preferences and found that many of my audio devices had disappeared. Reconnecting my laptop to the ThinkPad Dock seemed to trigger the wireplumber crash. My problem was solved when wireplumber restarted (i.e., audio devices reappeared). This has happened twice now since updating a few days ago, after never happening before.


reporter:       libreport-2.17.11
type:           CCpp
reason:         wireplumber killed by SIGSEGV
journald_cursor: s=a94c306a37cd4c0f9457247948ac869f;i=30c4ee;b=88336b06180f441c8abe42b7d8bf6222;m=2979f47e1;t=60295637f0d81;x=df90efce84e312dd
executable:     /usr/bin/wireplumber
cmdline:        /usr/bin/wireplumber
cgroup:         0::/user.slice/user-115751.slice/user/session.slice/wireplumber.service
rootdir:        /
uid:            115751
kernel:         6.4.7-200.fc38.x86_64
package:        wireplumber-0.4.14-1.fc38
runlevel:       N 5
backtrace_rating: 4
crash_function: loop_iterate
comment:        I opened Google Meet in Firefox, which attempted to use my USB headset speaker and microphone (connected via ThinkPad  USB-C dock). When I realized I could not say or hear anything in the meeting, I checked the Sound menu in System Preferences and found that many of my audio devices had disappeared. Reconnecting my laptop to the ThinkPad Dock seemed to trigger the wireplumber crash. My problem was solved when wireplumber restarted (i.e., audio devices reappeared). This has happened twice now since updating a few days ago, after never happening before.

Comment 15 Christopher Beland 2023-08-19 19:15:48 UTC
wireplumber has lately been using 100% of CPU, and I've been having trouble playing audio reliably. It crashed this time after I had manually killed the wireplumber process then restarted it with "wireplumber&" from the command line.


reporter:       libreport-2.17.11
comment:        wireplumber has lately been using 100% of CPU, and I've been having trouble playing audio reliably. It crashed this time after I had manually killed the wireplumber process then restarted it with "wireplumber&" from the command line.
crash_function: loop_iterate
cmdline:        wireplumber
executable:     /usr/bin/wireplumber
reason:         wireplumber killed by SIGSEGV
type:           CCpp
kernel:         6.4.10-200.fc38.x86_64
package:        wireplumber-0.4.14-1.fc38
rootdir:        /
runlevel:       N 5
uid:            1000
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-org.gnome.Terminal.slice/vte-spawn-365855e5-819b-4ecc-9f1e-d67966e41d1d.scope
journald_cursor: s=629b355a27de4f8e99f84e8329c89cb7;i=519d34;b=e4da0c598b5b4f389e52af820d36daa6;m=175c9fa36f;t=6034b6b7c232f;x=fae05ba73c1c33f0
backtrace_rating: 4

Comment 16 Christopher Beland 2023-09-03 20:52:04 UTC
Original wireplumber process ate up 100% of CPU, so I killed it and started this one from the command line:

[beland@big-board ~]$ wireplumber
M 16:47:16.536249          wp-device ../lib/wp/device.c:619:wp_spa_device_new_from_spa_factory: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed?
M 16:47:16.536280   script/libcamera libcamera.lua:173:chunk: PipeWire's libcamera SPA missing or broken. libcamera not supported.
W 16:47:17.043636 m-portal-permissio ../modules/module-portal-permissionstore.c:63:wp_portal_permissionstore_plugin_lookup: <WpPortalPermissionStorePlugin:0x561ef2b60770> Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
W 16:47:17.044343 m-portal-permissio ../modules/module-portal-permissionstore.c:63:wp_portal_permissionstore_plugin_lookup: <WpPortalPermissionStorePlugin:0x561ef2b60770> Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
W 16:41:14.320204 m-portal-permissio ../modules/module-portal-permissionstore.c:63:wp_portal_permissionstore_plugin_lookup: <WpPortalPermissionStorePlugin:0x561ef2b60770> Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
Segmentation fault (core dumped)

It worked fine for days, and crashed while I was streaming music from Pandora.


reporter:       libreport-2.17.11
crash_function: loop_iterate
cmdline:        wireplumber
executable:     /usr/bin/wireplumber
reason:         wireplumber killed by SIGSEGV
type:           CCpp
kernel:         6.4.12-200.fc38.x86_64
package:        wireplumber-0.4.14-1.fc38
rootdir:        /
runlevel:       N 5
uid:            1000
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-org.gnome.Terminal.slice/vte-spawn-d661f646-f60e-4c26-9989-d102f4c29ba4.scope
journald_cursor: s=629b355a27de4f8e99f84e8329c89cb7;i=530981;b=334ea8903a1b43738958cc1b1ca395fa;m=2c0e1c6915;t=6047a8ae580f3;x=6af9db3fbe71f1eb
backtrace_rating: 4

Comment 17 Aoife Moloney 2024-05-28 13:47:18 UTC
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.