Version-Release number of selected component: wireplumber-0.4.11-1.fc36 Additional info: reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/wireplumber.service cmdline: /usr/bin/wireplumber crash_function: on_got_bus executable: /usr/bin/wireplumber journald_cursor: s=08ba38f3fd0b4581aafb18bbe89fc239;i=48ffc4;b=aefb632e1c594eceb33c057b5c64e201;m=2f3bda97e;t=5e338ff64e5a5;x=94b089b377311de1 kernel: 5.18.9-200.fc36.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #0 on_got_bus at ../lib/wp/dbus.c:65 #1 g_task_return_now at ../gio/gtask.c:1230 #2 complete_in_idle_cb at ../gio/gtask.c:1244 #6 g_main_context_iterate.constprop.0 at ../glib/gmain.c:4211
Created attachment 1895236 [details] File: backtrace
Created attachment 1895237 [details] File: core_backtrace
Created attachment 1895238 [details] File: cpuinfo
Created attachment 1895239 [details] File: dso_list
Created attachment 1895240 [details] File: environ
Created attachment 1895241 [details] File: exploitable
Created attachment 1895242 [details] File: limits
Created attachment 1895243 [details] File: maps
Created attachment 1895244 [details] File: mountinfo
Created attachment 1895245 [details] File: open_fds
Created attachment 1895246 [details] File: proc_pid_status
Created attachment 1895247 [details] File: var_log_messages
*** Bug 2105219 has been marked as a duplicate of this bug. ***
*** Bug 2105431 has been marked as a duplicate of this bug. ***
*** Bug 2105457 has been marked as a duplicate of this bug. ***
*** Bug 2105510 has been marked as a duplicate of this bug. ***
*** Bug 2105600 has been marked as a duplicate of this bug. ***
*** Bug 2105621 has been marked as a duplicate of this bug. ***
*** Bug 2105685 has been marked as a duplicate of this bug. ***
*** Bug 2105695 has been marked as a duplicate of this bug. ***
*** Bug 2105708 has been marked as a duplicate of this bug. ***
*** Bug 2105757 has been marked as a duplicate of this bug. ***
*** Bug 2105871 has been marked as a duplicate of this bug. ***
*** Bug 2105966 has been marked as a duplicate of this bug. ***
*** Bug 2105989 has been marked as a duplicate of this bug. ***
*** Bug 2106052 has been marked as a duplicate of this bug. ***
*** Bug 2106150 has been marked as a duplicate of this bug. ***
*** Bug 2106176 has been marked as a duplicate of this bug. ***
*** Bug 2106233 has been marked as a duplicate of this bug. ***
Similar problem has been detected: After the attached upgrades I logged out of MATE and logged in again. This is when I was notified of the crash. Upgrade breeze-icon-theme-5.96.0-1.fc36.noarch @updates Upgraded breeze-icon-theme-5.94.0-1.fc36.noarch @@System Upgrade flatpak-1.12.7-4.fc36.x86_64 @updates Upgraded flatpak-1.12.7-3.fc36.x86_64 @@System Upgrade flatpak-libs-1.12.7-4.fc36.x86_64 @updates Upgraded flatpak-libs-1.12.7-3.fc36.x86_64 @@System Upgrade flatpak-selinux-1.12.7-4.fc36.noarch @updates Upgraded flatpak-selinux-1.12.7-3.fc36.noarch @@System Upgrade flatpak-session-helper-1.12.7-4.fc36.x86_64 @updates Upgraded flatpak-session-helper-1.12.7-3.fc36.x86_64 @@System Upgrade kf5-filesystem-5.96.0-1.fc36.x86_64 @updates Upgraded kf5-filesystem-5.94.0-1.fc36.x86_64 @@System Upgrade kf5-karchive-5.96.0-1.fc36.x86_64 @updates Upgraded kf5-karchive-5.94.0-1.fc36.x86_64 @@System Upgrade kf5-kauth-5.96.0-1.fc36.x86_64 @updates Upgraded kf5-kauth-5.94.0-1.fc36.x86_64 @@System Upgrade kf5-kcodecs-5.96.0-1.fc36.x86_64 @updates Upgraded kf5-kcodecs-5.94.0-1.fc36.x86_64 @@System Upgrade kf5-kconfig-core-5.96.0-1.fc36.x86_64 @updates Upgraded kf5-kconfig-core-5.94.0-1.fc36.x86_64 @@System Upgrade kf5-kconfig-gui-5.96.0-1.fc36.x86_64 @updates Upgraded kf5-kconfig-gui-5.94.0-1.fc36.x86_64 @@System Upgrade kf5-kconfigwidgets-5.96.0-1.fc36.x86_64 @updates Upgraded kf5-kconfigwidgets-5.94.0-1.fc36.x86_64 @@System Upgrade kf5-kcoreaddons-5.96.0-1.fc36.x86_64 @updates Upgraded kf5-kcoreaddons-5.94.0-1.fc36.x86_64 @@System Upgrade kf5-kcrash-5.96.0-1.fc36.x86_64 @updates Upgraded kf5-kcrash-5.94.0-1.fc36.x86_64 @@System Upgrade kf5-kdbusaddons-5.96.0-1.fc36.x86_64 @updates Upgraded kf5-kdbusaddons-5.94.0-1.fc36.x86_64 @@System Upgrade kf5-kguiaddons-5.96.0-1.fc36.x86_64 @updates Upgraded kf5-kguiaddons-5.94.0-1.fc36.x86_64 @@System Upgrade kf5-ki18n-5.96.0-1.fc36.x86_64 @updates Upgraded kf5-ki18n-5.94.0-1.fc36.x86_64 @@System Upgrade kf5-kimageformats-5.96.0-1.fc36.x86_64 @updates Upgraded kf5-kimageformats-5.94.0-1.fc36.x86_64 @@System Upgrade kf5-knotifications-5.96.0-1.fc36.x86_64 @updates Upgraded kf5-knotifications-5.94.0-1.fc36.x86_64 @@System Upgrade kf5-kservice-5.96.0-1.fc36.x86_64 @updates Upgraded kf5-kservice-5.94.0-2.fc36.x86_64 @@System Upgrade kf5-kwallet-5.96.0-1.fc36.x86_64 @updates Upgraded kf5-kwallet-5.94.0-1.fc36.x86_64 @@System Upgrade kf5-kwallet-libs-5.96.0-1.fc36.x86_64 @updates Upgraded kf5-kwallet-libs-5.94.0-1.fc36.x86_64 @@System Upgrade kf5-kwidgetsaddons-5.96.0-1.fc36.x86_64 @updates Upgraded kf5-kwidgetsaddons-5.94.0-1.fc36.x86_64 @@System Upgrade kf5-kwindowsystem-5.96.0-1.fc36.x86_64 @updates Upgraded kf5-kwindowsystem-5.94.0-1.fc36.x86_64 @@System Upgrade mate-panel-1.26.2-2.fc36.x86_64 @updates Upgraded mate-panel-1.26.2-1.fc36.x86_64 @@System Upgrade mate-panel-libs-1.26.2-2.fc36.x86_64 @updates Upgraded mate-panel-libs-1.26.2-1.fc36.x86_64 @@System Upgrade mate-screensaver-1.26.1-1.fc36.x86_64 @updates Upgraded mate-screensaver-1.26.0-3.fc36.x86_64 @@System Upgrade pluma-plugins-1.26.0-3.fc36.x86_64 @updates Upgraded pluma-plugins-1.26.0-2.fc36.x86_64 @@System Upgrade pluma-plugins-data-1.26.0-3.fc36.noarch @updates Upgraded pluma-plugins-data-1.26.0-2.fc36.noarch @@System reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/wireplumber.service cmdline: /usr/bin/wireplumber crash_function: on_got_bus executable: /usr/bin/wireplumber journald_cursor: s=d9408b528ffa4c31a4e6230886897fe0;i=a6cf;b=f24b177aac994d499c6d40c80a8b3670;m=2c7cd25755;t=5e389a919df86;x=1bc1cf7a37bc5c80 kernel: 5.18.10-200.fc36.x86_64 package: wireplumber-0.4.11-1.fc36 reason: wireplumber killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 2106358 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I plugged USB stick (SanDisk Ultra, 1 partition, 123GB, FAT, /dev/sdb1), opened files application and selected inserted usb stick in the left panel to see it's content. Gnome crashed and after few seconds of the black screen, I was brought again to a login screen (all my open applications gone) reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/wireplumber.service cmdline: /usr/bin/wireplumber crash_function: on_got_bus executable: /usr/bin/wireplumber journald_cursor: s=66501a4e9ceb423bbb8c8bc3d47228eb;i=a2a08;b=91da6bd39b1c45068ed0865b317af083;m=856e664ee;t=5e39ce6505b19;x=76c99150493852df kernel: 5.18.10-200.fc36.x86_64 package: wireplumber-0.4.11-1.fc36 reason: wireplumber killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 2106434 has been marked as a duplicate of this bug. ***
*** Bug 2106495 has been marked as a duplicate of this bug. ***
*** Bug 2106542 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I was playing a game, and after nothing in particular happening, my screen went to black. After some seconds, I was back in GDM, and after signing in I had a fresh desktop session, i.e., my whole desktop session had crashed, taking not only my game but all my other open windows with it too. This has happened to me twice before, but then I was not patient enough to wait for the black screen to go away as I thought my whole computer had crashed entirely, and simply pressed the reset button. In those two cases I don't remember getting an ABRT notification. reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/wireplumber.service cmdline: /usr/bin/wireplumber crash_function: on_got_bus executable: /usr/bin/wireplumber journald_cursor: s=6a65a0bec2ea4d9eb0dc46e090ef08f8;i=30c386;b=cce0f2ce3df143928383a86ef870df42;m=1a775ac7c9;t=5e3a41a6b32ea;x=d3302f384d075f9b kernel: 5.18.10-200.fc36.x86_64 package: wireplumber-0.4.11-1.fc36 reason: wireplumber killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
upstream issue: https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/305
FEDORA-2022-0036020baa has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-0036020baa
FEDORA-2022-0036020baa has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-a540c39ed0 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a540c39ed0
FEDORA-2022-3af8653644 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-3af8653644
*** Bug 2106730 has been marked as a duplicate of this bug. ***
*** Bug 2106778 has been marked as a duplicate of this bug. ***
*** Bug 2106914 has been marked as a duplicate of this bug. ***
*** Bug 2106948 has been marked as a duplicate of this bug. ***
FEDORA-2022-3af8653644 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-3af8653644` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-3af8653644 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-a540c39ed0 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 --refresh --advisory=FEDORA-2022-a540c39ed0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-a540c39ed0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Similar problem has been detected: Started Gnome reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/wireplumber.service cmdline: /usr/bin/wireplumber crash_function: on_got_bus executable: /usr/bin/wireplumber journald_cursor: s=ca158258575a43578e61a751a5e158c4;i=a032;b=0e3ebc7b2f5d4b11973f265f16119a22;m=8c630404;t=5e3c36aaa9719;x=a4196fdba8e4283e kernel: 5.18.11-200.fc36.x86_64 package: wireplumber-0.4.11-1.fc36 reason: wireplumber killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 2107409 has been marked as a duplicate of this bug. ***
FEDORA-2022-3af8653644 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
Similar problem has been detected: I was using Google Meet in Chrome reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/wireplumber.service cmdline: /usr/bin/wireplumber crash_function: on_got_bus executable: /usr/bin/wireplumber journald_cursor: s=1e101c087ff6446e86506aa0e24df16f;i=93b4e;b=4f1011ddfc134efeb50a75244a9418f9;m=57a58c2f9f;t=5e3d31b2e84a5;x=98f884cabe17595 kernel: 5.18.9-200.fc36.x86_64 package: wireplumber-0.4.11-1.fc36 reason: wireplumber killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I don't know what really caused this problem, but this occured on the boot after a regular, weekly update/patching on F36. reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-42.slice/user/session.slice/wireplumber.service cmdline: /usr/bin/wireplumber crash_function: on_got_bus executable: /usr/bin/wireplumber journald_cursor: s=924c099f086c41648dbed26fc5e2d878;i=e7da03;b=ea023a625c634442ab9685cbdeb12067;m=5111735;t=5e36850887add;x=a189184792a80ef8 kernel: 5.18.10-200.fc36.x86_64 package: wireplumber-0.4.11-1.fc36 reason: wireplumber killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 42
*** Bug 2107741 has been marked as a duplicate of this bug. ***
*** Bug 2107814 has been marked as a duplicate of this bug. ***
*** Bug 2105683 has been marked as a duplicate of this bug. ***
*** Bug 2107843 has been marked as a duplicate of this bug. ***
*** Bug 2107846 has been marked as a duplicate of this bug. ***
*** Bug 2107854 has been marked as a duplicate of this bug. ***
*** Bug 2110332 has been marked as a duplicate of this bug. ***
*** Bug 2110917 has been marked as a duplicate of this bug. ***
FEDORA-2022-a540c39ed0 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
*** Bug 2119509 has been marked as a duplicate of this bug. ***