Red Hat Bugzilla – Bug 619669
abrt 1.1.1 cannot submit bug report for signal 11 in xulrunner 1.9.2
Last modified: 2015-02-01 17:52:32 EST
Description of problem:
Version-Release number of selected component (if applicable):
Has happened only once
Steps to Reproduce:
Can't report because stack trace is unusable. After running debuginfo-install xulrunner, stack trace is still unusable.
Should be able to submit bug report
This bug causing the crash resembles #619597: same program seems to be crashing, same kernel. But I'm getting a Signal 11, SIGSEGV not an ABRT as in the aforementioned bug.
Here is what I got by copying to the clipboard and pasting:
Latest Crash: Sat 31 Jul 2010 11:56:47 PM
Command: /usr/lib/xulrunner-1.9.2/plugin-container /home/jones/.mozilla/plugins/libflashplayer.so 2495 plugin
Reason: Process /usr/lib/xulrunner-1.9.2/plugin-container was killed by signal 11 (SIGSEGV)
this is not a bug in plugin-container but in libflashplayer.so the problem is that libflashplayer.so is a 3rd party closed source program and has no debuginfo to install and thus making the backtrace unusable. This component is blacklisted in next ABRT release, so it won't bother you anymore.
The crash occurred again today. I have not yet found a newer release of my current abrt-1.1.2-fc13. While I was still in in Add/Remove software window, I also visited the abrt webpage, and found a ticket echoing my experience, but with eclipse. The ticket is at
In order to follow progress on this problem, I tried to set the status to Open/NextRelease. However, the only choice I was offered was Assigned, so I've set it there, and will watch for the next release.
In the meamtime, I wouldn't mind a official patch to the blacklist that would cause flagging to myself without filing a report. That way, I'd have an additional way to catch bugs in flash. Meanwhile, with no changes, I'll have abrt delete the occasional useless bug reports.
Thanks for your help.
Got a crash in Skype today. Obviously, Skype should be blacklisted too. However, abrt suggests running the useless command "debug-install skype", which searches only the configured repositories, and not the skype website. I doubt Skype makes a debugging version available.
(In reply to comment #4)
> Got a crash in Skype today. Obviously, Skype should be blacklisted too.
> However, abrt suggests running the useless command "debug-install skype", which
> searches only the configured repositories, and not the skype website. I doubt
> Skype makes a debugging version available.
Skype is not a Fedora package and is ignored in the default configuration, but there is a minor bug in abrt-1.1.13 config (gpg check is disabled) which makes abrt to catch crashes even in non-Fedora packages. this is fixed in 1.1.13-2 which is in the testing repo, you can try:
$ yum update abrt --enablerepo=updates-testing
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. 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 WONTFIX if it remains open with a Fedora
'version' of '13'.
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 prior to Fedora 13's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 13 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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.
The process we are following is described here:
Haven't had this bug lately. Closing.