Description of problem: No idea. I left Mednafen running in the background and when I came back a few minutes later, Mednafen was frozen and I had this ABRT notification popping up. Version-Release number of selected component: pipewire-pulseaudio-0.3.20-1.fc33 Additional info: reporter: libreport-2.14.0 backtrace_rating: 3 cgroup: 0::/user.slice/user-1000.slice/user/pipewire-pulse.service cmdline: /usr/bin/pipewire-pulse executable: /usr/bin/pipewire-pulse journald_cursor: s=5b2bc4fb951a483aad9e29dd9471266b;i=10aa0;b=ba8da956f72041498971dc1827967882;m=1aff570de;t=5b9bc6e470e30;x=1a75c51a74747762 kernel: 5.10.9-201.fc33.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #0 ?? #1 pw_stream_destroy at ../src/pipewire/stream.c:1316 #2 stream_free at ../src/modules/module-protocol-pulse/pulse-server.c:902 #3 do_delete_stream at ../src/modules/module-protocol-pulse/pulse-server.c:2065 #4 handle_packet at ../src/modules/module-protocol-pulse/pulse-server.c:4830 #5 do_read at ../src/modules/module-protocol-pulse/pulse-server.c:4979 #6 on_client_data at ../src/modules/module-protocol-pulse/pulse-server.c:5024 #7 loop_iterate at ../spa/plugins/support/loop.c:308 #8 pw_main_loop_run at ../src/pipewire/main-loop.c:158
Created attachment 1750672 [details] File: backtrace
Created attachment 1750673 [details] File: core_backtrace
Created attachment 1750674 [details] File: cpuinfo
Created attachment 1750675 [details] File: dso_list
Created attachment 1750676 [details] File: environ
Created attachment 1750677 [details] File: exploitable
Created attachment 1750678 [details] File: limits
Created attachment 1750679 [details] File: maps
Created attachment 1750680 [details] File: mountinfo
Created attachment 1750681 [details] File: open_fds
Created attachment 1750682 [details] File: proc_pid_status
Created attachment 1750683 [details] File: var_log_messages
Yeah I can fully reproduce this by leaving Mednafen open in the background, even if paused (in-game, not the emulation itself). It seems to crash on random functions, so no pattern here besides leaving Mednafen open and expecting pipewire-pulse to segfault, although it takes a while.
FEDORA-2021-f394ea10e9 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-f394ea10e9
FEDORA-2021-d6d23603c6 has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-d6d23603c6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-d6d23603c6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-d6d23603c6 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.