RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1316044 - [abrt] pulseaudio: core_free(): pulseaudio killed by SIGABRT
Summary: [abrt] pulseaudio: core_free(): pulseaudio killed by SIGABRT
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pulseaudio
Version: 7.3
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Wim Taymans
QA Contact: Desktop QE
URL:
Whiteboard: abrt_hash:fc02a22596b4dbb56222edfa32b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-09 10:19 UTC by Lubomir Rintel
Modified: 2022-12-14 13:38 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-15 07:40:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
File: backtrace (10.97 KB, text/plain)
2016-03-09 10:19 UTC, Lubomir Rintel
no flags Details
File: cgroup (179 bytes, text/plain)
2016-03-09 10:19 UTC, Lubomir Rintel
no flags Details
File: core_backtrace (1.26 KB, text/plain)
2016-03-09 10:19 UTC, Lubomir Rintel
no flags Details
File: dso_list (6.03 KB, text/plain)
2016-03-09 10:19 UTC, Lubomir Rintel
no flags Details
File: environ (1.09 KB, text/plain)
2016-03-09 10:19 UTC, Lubomir Rintel
no flags Details
File: limits (1.29 KB, text/plain)
2016-03-09 10:19 UTC, Lubomir Rintel
no flags Details
File: machineid (135 bytes, text/plain)
2016-03-09 10:19 UTC, Lubomir Rintel
no flags Details
File: maps (29.59 KB, text/plain)
2016-03-09 10:19 UTC, Lubomir Rintel
no flags Details
File: open_fds (185 bytes, text/plain)
2016-03-09 10:19 UTC, Lubomir Rintel
no flags Details
File: proc_pid_status (1.03 KB, text/plain)
2016-03-09 10:19 UTC, Lubomir Rintel
no flags Details
File: var_log_messages (4.25 KB, text/plain)
2016-03-09 10:19 UTC, Lubomir Rintel
no flags Details
File: sosreport.tar.xz (5.88 MB, application/octet-stream)
2016-03-09 10:20 UTC, Lubomir Rintel
no flags Details

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.


Note You need to log in before you can comment on or make changes to this bug.