Bug 716222

Summary: [abrt] seamonkey-2.0.14-1.fc14: bonobo_x_error_handler: Process /usr/lib/seamonkey-2.0.14/seamonkey-bin was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Joe Robinson <joe_underscore>
Component: seamonkeyAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: caillon, gecko-bugs-nobody, kengert
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:ddb4849a19fb8a13dfc43aee01d51c61e711bc7a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-07 13:17:28 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

Description Joe Robinson 2011-06-23 16:48:16 UTC 
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 34329 bytes
cmdline: /usr/lib/seamonkey-2.0.14/seamonkey-bin
comment: I was using SeaMonkey under another user's login, had left it running, was using Firefox in another Workspace.
component: seamonkey
Attached file: coredump, 211025920 bytes
crash_function: bonobo_x_error_handler
executable: /usr/lib/seamonkey-2.0.14/seamonkey-bin
kernel: 2.6.35.13-92.fc14.i686.PAE
package: seamonkey-2.0.14-1.fc14
rating: 4
reason: Process /usr/lib/seamonkey-2.0.14/seamonkey-bin was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1308844630
uid: 501

How to reproduce
-----
1. Unknown.
2.
3.
Comment 1 Joe Robinson 2011-06-23 16:48:18 UTC 
Created attachment 509573 [details]
File: backtrace
Comment 2 Martin Stransky 2011-12-07 13:17:28 UTC 
We're using mozilla crash reporter now, ABRT is no more used for Firefox/Thunderbird. If you can reliably reproduce the crash (you have a testcase, reproduction steps, etc.) please reopen the bug and attach the reproduction info and assign it directly to me (stransky).

Thanks!