Bug 1979405 - [abrt] pipewire: clear_params(): pipewire-media-session killed by SIGABRT
Summary: [abrt] pipewire: clear_params(): pipewire-media-session killed by SIGABRT
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: pipewire
Version: 34
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Wim Taymans
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:be20347fd0ffa151f38e90df19e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-05 21:57 UTC by Rafal
Modified: 2021-07-22 01:14 UTC (History)
3 users (show)

Fixed In Version: pipewire-0.3.32-1.fc34
Clone Of:
Environment:
Last Closed: 2021-07-22 01:14:13 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (19.65 KB, text/plain)
2021-07-05 21:57 UTC, Rafal 		no flags Details
File: core_backtrace (6.54 KB, text/plain)
2021-07-05 21:58 UTC, Rafal 		no flags Details
File: cpuinfo (2.16 KB, text/plain)
2021-07-05 21:58 UTC, Rafal 		no flags Details
File: dso_list (1.04 KB, text/plain)
2021-07-05 21:58 UTC, Rafal 		no flags Details
File: environ (2.08 KB, text/plain)
2021-07-05 21:58 UTC, Rafal 		no flags Details
File: limits (1.29 KB, text/plain)
2021-07-05 21:58 UTC, Rafal 		no flags Details
File: maps (3.98 KB, text/plain)
2021-07-05 21:58 UTC, Rafal 		no flags Details
File: mountinfo (3.91 KB, text/plain)
2021-07-05 21:58 UTC, Rafal 		no flags Details
File: open_fds (4.04 KB, text/plain)
2021-07-05 21:58 UTC, Rafal 		no flags Details
File: proc_pid_status (1.39 KB, text/plain)
2021-07-05 21:58 UTC, Rafal 		no flags Details
View All

Description Rafal 2021-07-05 21:57:54 UTC 
Version-Release number of selected component:
pipewire-0.3.31-2.fc34

Additional info:
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: clear_params
executable:     /usr/bin/pipewire-media-session
journald_cursor: s=0f059329e5f64249aa28d948a2a40158;i=1ef0a3;b=7765b58bb75e43e1a84a4815ac0c2be5;m=481260d6;t=5c61e896b7e02;x=2efd4314bdd76860
kernel:         5.12.13-300.fc34.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 1 Rafal 2021-07-05 21:57:58 UTC 
Created attachment 1798375 [details]
File: backtrace
Comment 2 Rafal 2021-07-05 21:58:00 UTC 
Created attachment 1798376 [details]
File: core_backtrace
Comment 3 Rafal 2021-07-05 21:58:01 UTC 
Created attachment 1798377 [details]
File: cpuinfo
Comment 4 Rafal 2021-07-05 21:58:03 UTC 
Created attachment 1798378 [details]
File: dso_list
Comment 5 Rafal 2021-07-05 21:58:05 UTC 
Created attachment 1798379 [details]
File: environ
Comment 6 Rafal 2021-07-05 21:58:06 UTC 
Created attachment 1798380 [details]
File: limits
Comment 7 Rafal 2021-07-05 21:58:08 UTC 
Created attachment 1798381 [details]
File: maps
Comment 8 Rafal 2021-07-05 21:58:10 UTC 
Created attachment 1798382 [details]
File: mountinfo
Comment 9 Rafal 2021-07-05 21:58:12 UTC 
Created attachment 1798383 [details]
File: open_fds
Comment 10 Rafal 2021-07-05 21:58:13 UTC 
Created attachment 1798384 [details]
File: proc_pid_status
Comment 11 Fedora Update System 2021-07-20 14:38:52 UTC 
FEDORA-2021-f3a65aee6b has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-f3a65aee6b
Comment 12 Fedora Update System 2021-07-21 01:54:42 UTC 
FEDORA-2021-f3a65aee6b 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-f3a65aee6b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-f3a65aee6b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 13 Fedora Update System 2021-07-22 01:14:13 UTC 
FEDORA-2021-f3a65aee6b has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.