Description of problem: i switched in microsoft teams multiple times between meetings, then pipewire crashed suddenly and caja also Version-Release number of selected component: pipewire-0.3.27-2.fc34 Additional info: reporter: libreport-2.14.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/pipewire.service cmdline: /usr/bin/pipewire-media-session crash_function: impl_node_process executable: /usr/bin/pipewire-media-session journald_cursor: s=6263ccb1764d4ce1b3ab62ddd9f2a2ab;i=259ee;b=8ba2107eeed746ef8d10aaee9747c416;m=219bc5dcc;t=5c296861d9c1b;x=d23ec51cd90bc376 kernel: 5.11.20-300.fc34.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (5 frames) #0 impl_node_process at ../spa/plugins/audioconvert/merger.c:1270 #4 process_node at ../src/pipewire/impl-node.c:1040 #5 node_on_fd_events at ../src/pipewire/impl-node.c:1098 #6 loop_iterate at ../spa/plugins/support/loop.c:308 #7 do_loop at ../src/pipewire/data-loop.c:79
Created attachment 1784366 [details] File: backtrace
Created attachment 1784367 [details] File: core_backtrace
Created attachment 1784368 [details] File: cpuinfo
Created attachment 1784369 [details] File: dso_list
Created attachment 1784370 [details] File: environ
Created attachment 1784371 [details] File: exploitable
Created attachment 1784372 [details] File: limits
Created attachment 1784373 [details] File: maps
Created attachment 1784374 [details] File: mountinfo
Created attachment 1784375 [details] File: open_fds
Created attachment 1784376 [details] File: proc_pid_status
FEDORA-2021-4bd6fdd9d3 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-4bd6fdd9d3
FEDORA-2021-4bd6fdd9d3 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-4bd6fdd9d3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-4bd6fdd9d3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-29223a7ff9 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-29223a7ff9
FEDORA-2021-29223a7ff9 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-29223a7ff9` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-29223a7ff9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-29223a7ff9 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
*** Bug 1971362 has been marked as a duplicate of this bug. ***
*** Bug 1980764 has been marked as a duplicate of this bug. ***
*** Bug 1989805 has been marked as a duplicate of this bug. ***
Similar problem has been detected: when listening music using bluetooth, suddenly this happened. it's not the first time. reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/pipewire.service cmdline: /usr/bin/pipewire-media-session crash_function: impl_node_process executable: /usr/bin/pipewire-media-session journald_cursor: s=8d61c5727cb044589b8d36bc44edf10c;i=108f9;b=595666faf2634be395283fe67666c55c;m=1b62a9c4a;t=5c9c8038378f5;x=4b072f514c071bc8 kernel: 5.14.0-0.rc2.23.fc35.x86_64 package: pipewire-0.3.33-3.fc34 reason: pipewire-media-session killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 2002389 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Crash while using Bluetooth Headset (Samsung Galaxy Buds+) reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/pipewire.service cmdline: /usr/bin/pipewire-media-session crash_function: impl_node_process executable: /usr/bin/pipewire-media-session journald_cursor: s=83bb9a5c63ba49769beae419546185df;i=7bcf;b=89d4d295fec94a439a671f517d5ddfef;m=11d826dc53;t=5cb796bec4008;x=1e01de32d9b6cbfb kernel: 5.13.12-200.fc34.x86_64 package: pipewire-0.3.34-1.fc34 reason: pipewire-media-session killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Can we please re-open this? I am still seeing a similar crash, started with a recent Pipewire version.
as more and more duplicates are reported, i open that again, hope thats ok
Similar problem has been detected: PipeWire crashed on the background while I had my bluetooth headset connected. reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/pipewire.service cmdline: /usr/bin/pipewire-media-session crash_function: impl_node_process executable: /usr/bin/pipewire-media-session journald_cursor: s=0289090f3efe481da2f60fbef8ad9dca;i=3cbe66;b=bd016fbf842a422182f29da1bc75c947;m=b124913e;t=5ccd4a58b7164;x=7ba0fe28feda0646 kernel: 5.13.14-200.fc34.x86_64 package: pipewire-0.3.35-2.fc34 reason: pipewire-media-session killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: suspend/resume reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/pipewire.service cmdline: /usr/bin/pipewire-media-session crash_function: impl_node_process executable: /usr/bin/pipewire-media-session journald_cursor: s=317dd1ba16154a9ba0cc4c620adf07ae;i=172f;b=7d0ac03fcf224c9db439b9b0844a86a0;m=21a69d8ad;t=5ccd499e5ad9d;x=b425041bd6d1d34d kernel: 5.14.7-200.fc34.x86_64 package: pipewire-0.3.37-1.fc34 reason: pipewire-media-session killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I was just playing a youtube video to my bluetooth headphones when I heard it disconnect, and got this notification of a pipewire crash. reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/pipewire.service cmdline: /usr/bin/pipewire-media-session crash_function: impl_node_process executable: /usr/bin/pipewire-media-session journald_cursor: s=632a2e33b1114226a0628e30b5071dc6;i=f924;b=074eef380f244ababf84ea3caf9f33d2;m=909255d07b;t=5ceb256ad8f45;x=e9834679eee1731f kernel: 5.13.12-200.fc34.x86_64 package: pipewire-0.3.38-1.fc34 reason: pipewire-media-session killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. 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 '34'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 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.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days