Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 621434 - [abrt] crash in xulrunner- raise: Process /usr/lib/xulrunner-1.9.2/plugin-container was killed by signal 6 (SIGABRT)
[abrt] crash in xulrunner- raise: Process /usr/lib/xulrunner-1...
Status: CLOSED DUPLICATE of bug 616689
Product: Fedora
Classification: Fedora
Component: xulrunner (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Gecko Maintainer
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-08-04 23:41 EDT by edatva
Modified: 2010-11-09 08:19 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-09 08:19:06 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (26.16 KB, text/plain)
2010-08-04 23:41 EDT, edatva
no flags Details

  None (edit)
Description edatva 2010-08-04 23:41:09 EDT
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/xulrunner-1.9.2/plugin-container /usr/lib/flash-plugin/libflashplayer.so 19481 plugin
component: xulrunner
crash_function: raise
executable: /usr/lib/xulrunner-1.9.2/plugin-container
global_uuid: af76437fc99ba53ba47e9661103ebd9ff0187912
package: xulrunner-
rating: 4
reason: Process /usr/lib/xulrunner-1.9.2/plugin-container was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
Comment 1 edatva 2010-08-04 23:41:12 EDT
Created attachment 436732 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 08:19:06 EST

*** This bug has been marked as a duplicate of bug 616689 ***
Comment 3 Karel Klíč 2010-11-09 08:19:06 EST
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #616689.

Sorry for the inconvenience.

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