Bug 1012141

Created attachment 803048 [details]
File: backtrace

Created attachment 803049 [details]
File: cgroup

Created attachment 803050 [details]
File: core_backtrace

Created attachment 803051 [details]
File: dso_list

Created attachment 803052 [details]
File: environ

Created attachment 803053 [details]
File: limits

Created attachment 803054 [details]
File: maps

Created attachment 803055 [details]
File: open_fds

Created attachment 803056 [details]
File: proc_pid_status

No idea. Logged back in at GDM screen.

reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        /usr/bin/pulseaudio --start
crash_function: core_free
executable:     /usr/bin/pulseaudio
kernel:         3.12.0-0.rc2.git0.2.fc21.x86_64
package:        pulseaudio-4.0-4.gita89ca.fc20
reason:         Process /usr/bin/pulseaudio was killed by signal 6 (SIGABRT)
runlevel:       unknown
type:           CCpp
uid:            1000

I installed and started skype. It came up with a notification, and the system hung up. Killing skype and pulse from a virtual terminal got it working again, and abrt directed me here.

Saw this on startup of a freshly-built F20 VM in virt-manager (doing some pre-Beta testing).

Seeing this bug on startup. I installed this system using beta TC1.

Still seeing this as of Beta TC2.

I'm also seeing other problems with the latest version of pulseaudio after updates.  Among these are problems with audio playback in Skype and crashing to console of lightDM Display Manager.

those items you mention are unrelated to this one (afaict).  

(for others), see bug #1017944 for skype crackling.

Just logged into Cinnamon, and got hit with six errors within a second and a half from pulseaudio while just logging on to a session.

ABRT, as usual, won't let me report them but was kind enough to reference this bug report.

Make that 14 since I last posted the above comment 17.

That count is up to 19 now but so far no more crashes and sound came back on the fourth reboot.

Proposing as a Final blocker per https://fedoraproject.org/wiki/Fedora_20_Final_Release_Criteria#SELinux_and_crash_notifications : "There must be no SELinux denial notifications or crash notifications on boot of or during installation from a release-blocking live image, or at first login after a default install of a release-blocking desktop." Also as a Beta freeze exception, as this is a pretty highly visible issue that looks bad to testers. It's still valid as of latest F20 packages with a newly-built live image, for me.

Fresh install of F20-Alpha.  Same thing.

Discussed at 2013-10-16 freeze exception review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-10-16/f20beta-blocker-review-4.2013-10-16-16.02.log.txt . Accepted as a freeze exception issue: this is a very visible bug that negatively affects perception of F20 Beta. It isn't fatal, though, so the fix may not be accepted late in freeze for safety reasons.

A couple of times now I have had gnome-shell crash out directly after the above pulseaudio crashes.  I'd say that is fatal--at least on my fresh F20-Alpha install.  Of course, abrt won't allow reporting on the issue because a similar gnome-shell crash already has been reported.

"I'd say that is fatal"

a) I haven't ever seen that, and the fact that it happens after the PA crash doesn't mean they're in any way related, and
b) shell crashes aren't usually really fatal because it just respawns itself.

"Of course, abrt won't allow reporting on the issue because a similar gnome-shell crash already has been reported."

So what is the bug #?

Now gone, along with all but one of the pulseaudio crashes.  The gnome-shell crash that occurred during an update also remains (that one is 995785) but the rest are gone from the list.  I had 3 gnome-shell crashes this week.  I had 19 out of 20 pulseaudio crashes that also now are gone.  What is up with that?  How long does abrt hold on to crash info before it no longer displays? What would cause the list of crashes to reset to Monday?

I also found that clicking on the system tab/button does nothing.  Abrt says there are 4 errors sitting there but clicking the button does not display anything.

This is not a forum thread. If you need help with abrt, ask in an appropriate forum. BZ discussion needs to be focused.

Not 100% sure, but have an educated guess that
https://admin.fedoraproject.org/updates/FEDORA-2013-19085/pulseaudio-4.0-7.gitf81e3.fc20

may fix this.

pulseaudio-4.0-7.gitf81e3.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/FEDORA-2013-19085/pulseaudio-4.0-7.gitf81e3.fc20

Happened on first login after upgrade from fc19 to fc20

reporter:       libreport-2.1.8
backtrace_rating: 4
cmdline:        /usr/bin/pulseaudio --start
crash_function: core_free
executable:     /usr/bin/pulseaudio
kernel:         3.11.4-301.fc20.x86_64
package:        pulseaudio-4.0-4.gita89ca.fc20
reason:         Process /usr/bin/pulseaudio was killed by signal 6 (SIGABRT)
runlevel:       N 5
type:           CCpp
uid:            1236200002

pulseaudio-4.0-7.gitf81e3.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

I've just got this crash in pulseaudio-5.0-7.fc20.x86_64 (directed here by abrt).

(In reply to lovyagin from comment #32)
> I've just got this crash in pulseaudio-5.0-7.fc20.x86_64 (directed here by
> abrt).

/me too

reopening

btw, as I don't see any search options at the abrt server, here's the link for the crash record for the version 0:5.0-7.fc20

https://retrace.fedoraproject.org/faf/reports/410607/

just got this with pulseaudio-5.0-25.fc21.x86_64

just got this with pulseaudio-6.0-2.fc21.1.x86_64

Another user experienced a similar problem:

I initiated a logout. After logout I logged back in and I was notified that PulseAudio stopped. Before the logout, I had been using steam (API v017, package version 14317290692), but closed the application window prior to logout (it may have had a background process running). I was also using chrome (Version 42.0.2311.152 64-bit), but I exited that as well (though chrome always has a background process running).

reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        /usr/bin/pulseaudio --start --log-target=syslog
crash_function: core_free
executable:     /usr/bin/pulseaudio
kernel:         3.19.7-200.fc21.x86_64
package:        pulseaudio-6.0-2.fc21.1
reason:         pulseaudio killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000

This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.