Bug 1962914

Summary: [abrt] pipewire: _dbus_warn_check_failed(): pipewire-media-session killed by SIGABRT
Product: [Fedora] Fedora Reporter: Emre zede <emre.zede>
Component: pipewireAssignee: Wim Taymans <wtaymans>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 34CC: brunovern.a, chin_chillin, fedora, herman.kramer, jake.owen, joepesco2020, kfarnung, kxra, ricky.tigg, rlledo, steeve.mccauley, waywardpooch, wtaymans
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/228748f0118bdcf713a55ad872dee4d2f1e265b1
Whiteboard: abrt_hash:905e14f1252591a10e2955a409169ca658b638bf;VARIANT_ID=workstation;
Fixed In Version: pipewire-0.3.30-1.fc34 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-06-11 01:15:09 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: backtrace
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Emre zede 2021-05-20 19:05:32 UTC 
Description of problem:
I just logged out. I reopened it. Thanks...

Version-Release number of selected component:
pipewire-0.3.28-1.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: _dbus_warn_check_failed
executable:     /usr/bin/pipewire-media-session
journald_cursor: s=81f65bb9997e417d92a27a3fc80036fb;i=1296d;b=e1a7c08fcde3457abec2355b74210dd6;m=c9c22f30;t=5c2c794cce02d;x=b5a31699fd63b41f
kernel:         5.11.20-300.fc34.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 1 Emre zede 2021-05-20 19:05:37 UTC 
Created attachment 1785321 [details]
File: backtrace
Comment 2 Emre zede 2021-05-20 19:05:38 UTC 
Created attachment 1785322 [details]
File: core_backtrace
Comment 3 Emre zede 2021-05-20 19:05:39 UTC 
Created attachment 1785323 [details]
File: cpuinfo
Comment 4 Emre zede 2021-05-20 19:05:41 UTC 
Created attachment 1785324 [details]
File: dso_list
Comment 5 Emre zede 2021-05-20 19:05:42 UTC 
Created attachment 1785325 [details]
File: environ
Comment 6 Emre zede 2021-05-20 19:05:43 UTC 
Created attachment 1785326 [details]
File: limits
Comment 7 Emre zede 2021-05-20 19:05:44 UTC 
Created attachment 1785327 [details]
File: maps
Comment 8 Emre zede 2021-05-20 19:05:46 UTC 
Created attachment 1785328 [details]
File: mountinfo
Comment 9 Emre zede 2021-05-20 19:05:47 UTC 
Created attachment 1785329 [details]
File: open_fds
Comment 10 Emre zede 2021-05-20 19:05:48 UTC 
Created attachment 1785330 [details]
File: proc_pid_status
Comment 11 waywardpooch 2021-05-21 15:49:34 UTC 
Similar problem has been detected:

When I boot my PC, pipewire works. If I log out, then log back in, pipewire still works. But if, immediately afterward, I log-out/log-in for a second time, pipewire fails, removing my volume slider from the top right of the GNOME panel until I restart my PC.

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: _dbus_warn_check_failed
executable:     /usr/bin/pipewire-media-session
journald_cursor: s=ed7875fe6c9243ec86ee779bb5f63c28;i=bb1a0;b=d138fac8ea0c41fab9422ef39a8de404;m=42c4ea8;t=5c2d874317b65;x=10817f01c9b9f238
kernel:         5.11.21-300.fc34.x86_64
package:        pipewire-0.3.28-1.fc34
reason:         pipewire-media-session killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 12 Rubén 2021-05-22 12:40:33 UTC 
*** Bug 1963334 has been marked as a duplicate of this bug. ***
Comment 13 Francois 2021-05-24 14:00:09 UTC 
*** Bug 1963966 has been marked as a duplicate of this bug. ***
Comment 14 herman.kramer@icu-it.nl 2021-05-26 09:44:06 UTC 
*** Bug 1964891 has been marked as a duplicate of this bug. ***
Comment 15 Kyle Farnung 2021-05-27 03:04:21 UTC 
Similar problem has been detected:

Logged out and back in.

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: _dbus_warn_check_failed
executable:     /usr/bin/pipewire-media-session
journald_cursor: s=08af47c5d95d44b6a4884faaa0191f03;i=1b8100;b=78cdae4d73ca46998b08bc0533d4283d;m=17f7ae7a7;t=5c346d6aa8e14;x=fbb47c34d4d86519
kernel:         5.11.21-300.fc34.x86_64
package:        pipewire-0.3.28-1.fc34
reason:         pipewire-media-session killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 16 ricky.tigg 2021-05-27 14:30:59 UTC 
Similar problem has been detected:

Logout then login in order to apply sysstem language change. On Gnome on Wayland desktop, the icon representing the loud speaker is no longer exhibited.

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: _dbus_warn_check_failed
executable:     /usr/bin/pipewire-media-session
journald_cursor: s=9fcdb24629af4cd28479bbf4690249dd;i=2572;b=5e2694badcb545c58e630640fcf81008;m=45ba3d772;t=5c3505b2d33df;x=2c044ff77d61f141
kernel:         5.12.6-300.fc34.x86_64
package:        pipewire-0.3.28-1.fc34
reason:         pipewire-media-session killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 17 Fedora Update System 2021-06-03 10:35:04 UTC 
FEDORA-2021-4bd6fdd9d3 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-4bd6fdd9d3
Comment 18 Fedora Update System 2021-06-04 01:18:30 UTC 
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.
Comment 19 Fedora Update System 2021-06-09 07:41:53 UTC 
FEDORA-2021-29223a7ff9 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-29223a7ff9
Comment 20 Fedora Update System 2021-06-10 01:19:56 UTC 
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.
Comment 21 Fedora Update System 2021-06-11 01:15:09 UTC 
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.