Bug 639770 - [abrt] seamonkey-2.0.6-1.fc13: Process /usr/lib64/seamonkey-2.0.6/seamonkey-bin was killed by signal 6 (SIGABRT)
Summary: [abrt] seamonkey-2.0.6-1.fc13: Process /usr/lib64/seamonkey-2.0.6/seamonkey-b...
Keywords:
Status: CLOSED DUPLICATE of bug 608297
Alias: None
Product: Fedora
Classification: Fedora
Component: seamonkey
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1c02d95010db8090f3e97b6cbdf...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-04 00:00 UTC by Chris Schanzle
Modified: 2010-11-09 15:17 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 15:17:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (85.25 KB, text/plain)
2010-10-04 00:00 UTC, Chris Schanzle
no flags Details

Description Chris Schanzle 2010-10-04 00:00:19 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/seamonkey-2.0.6/seamonkey-bin -mail
component: seamonkey
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/seamonkey-2.0.6/seamonkey-bin
kernel: 2.6.34.7-56.fc13.x86_64
package: seamonkey-2.0.6-1.fc13
rating: 4
reason: Process /usr/lib64/seamonkey-2.0.6/seamonkey-bin was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
How to reproduce: closed browser window, crash happened seconds later.  will keep submitting helpful reports until this bug gets fixed.
time: 1286150242
uid: 18183

Comment 1 Chris Schanzle 2010-10-04 00:00:22 UTC
Created attachment 451321 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 15:17:28 UTC

*** This bug has been marked as a duplicate of bug 608297 ***

Comment 3 Karel Klíč 2010-11-09 15:17:28 UTC
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 #608297.

Sorry for the inconvenience.


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