Bug 1316044

Summary: [abrt] pulseaudio: core_free(): pulseaudio killed by SIGABRT
Product: Red Hat Enterprise Linux 7 Reporter: Lubomir Rintel <lrintel>
Component: pulseaudioAssignee: Wim Taymans <wtaymans>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.3CC: lrintel, tpelka, wtaymans
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:fc02a22596b4dbb56222edfa32ba254a963aaba8
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-12-15 07:40:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: machineid
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
File: sosreport.tar.xz none

Description Lubomir Rintel 2016-03-09 10:19:17 UTC
Description of problem:
No idea.
This was just a clean RHEL-7.3 graphical server snapshot install in KVM, did nothing special.
Just isolated graphical.target and logged in GNOME.

Version-Release number of selected component:
pulseaudio-6.0-7.el7

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        /usr/bin/pulseaudio --start --log-target=syslog
crash_function: core_free
executable:     /usr/bin/pulseaudio
global_pid:     13276
kernel:         3.10.0-357.el7.x86_64
runlevel:       N 5
type:           CCpp
uid:            42

Truncated backtrace:
Thread no. 1 (2 frames)
 #2 core_free at pulsecore/core.c:179
 #3 pa_core_unref at pulsecore/core.h:202

Comment 1 Lubomir Rintel 2016-03-09 10:19:20 UTC
Created attachment 1134434 [details]
File: backtrace

Comment 2 Lubomir Rintel 2016-03-09 10:19:21 UTC
Created attachment 1134435 [details]
File: cgroup

Comment 3 Lubomir Rintel 2016-03-09 10:19:22 UTC
Created attachment 1134436 [details]
File: core_backtrace

Comment 4 Lubomir Rintel 2016-03-09 10:19:23 UTC
Created attachment 1134437 [details]
File: dso_list

Comment 5 Lubomir Rintel 2016-03-09 10:19:25 UTC
Created attachment 1134438 [details]
File: environ

Comment 6 Lubomir Rintel 2016-03-09 10:19:26 UTC
Created attachment 1134439 [details]
File: limits

Comment 7 Lubomir Rintel 2016-03-09 10:19:27 UTC
Created attachment 1134440 [details]
File: machineid

Comment 8 Lubomir Rintel 2016-03-09 10:19:29 UTC
Created attachment 1134441 [details]
File: maps

Comment 9 Lubomir Rintel 2016-03-09 10:19:30 UTC
Created attachment 1134442 [details]
File: open_fds

Comment 10 Lubomir Rintel 2016-03-09 10:19:32 UTC
Created attachment 1134443 [details]
File: proc_pid_status

Comment 11 Lubomir Rintel 2016-03-09 10:19:33 UTC
Created attachment 1134444 [details]
File: var_log_messages

Comment 12 Lubomir Rintel 2016-03-09 10:20:06 UTC
Created attachment 1134445 [details]
File: sosreport.tar.xz

Comment 14 Lubomir Rintel 2016-03-09 10:52:13 UTC
Another user experienced a similar problem:

No idea.
This was just a clean RHEL-7.3 graphical server snapshot install in KVM, did nothing special.
Just isolated graphical.target and logged in GNOME.

reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        /usr/bin/pulseaudio --start --log-target=syslog
crash_function: core_free
event_log:      
executable:     /usr/bin/pulseaudio
global_pid:     13276
kernel:         3.10.0-357.el7.x86_64
package:        pulseaudio-6.0-7.el7
reason:         pulseaudio killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            42

Comment 15 Wim Taymans 2016-03-29 10:05:22 UTC
I can't seem to reproduce this in a VM. Is there anything strange about the configuration of the VM? what audio device is selected?

Could you, in a terminal the VM, do something like:

pulseaudio -k && pulseaudio -vvvvv >log 2>&1

and attach the log here?

Comment 17 RHEL Program Management 2020-12-15 07:40:27 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.