Bug 630191 - [abrt] thunderbird-3.0.6-1.fc12: Process /usr/lib64/thunderbird-3.0/thunderbird-bin was killed by signal 6 (SIGABRT)
Summary: [abrt] thunderbird-3.0.6-1.fc12: Process /usr/lib64/thunderbird-3.0/thunderbi...
Keywords:
Status: CLOSED DUPLICATE of bug 543165
Alias: None
Product: Fedora
Classification: Fedora
Component: thunderbird
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:0826435cbda3b21a7e808ad3977...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-04 00:43 UTC by Daniel S Spicer
Modified: 2018-04-11 10:58 UTC (History)
2 users (show)

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

Attachments (Terms of Use)
File: backtrace (36.53 KB, text/plain)
2010-09-04 00:43 UTC, Daniel S Spicer 		no flags Details
Interesting part of the thread backtrace where crash happened. (9.70 KB, text/plain)
2010-09-17 17:06 UTC, Matěj Cepl 		no flags Details
View All

Description Daniel S Spicer 2010-09-04 00:43:25 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/thunderbird-3.0/thunderbird-bin
component: thunderbird
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/thunderbird-3.0/thunderbird-bin
kernel: 2.6.32.21-166.fc12.x86_64
package: thunderbird-3.0.6-1.fc12
rating: 4
reason: Process /usr/lib64/thunderbird-3.0/thunderbird-bin was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
time: 1283558679
uid: 500

How to reproduce
-----
1.closed the application
2.
3.
Comment 1 Daniel S Spicer 2010-09-04 00:43:28 UTC 
Created an attachment (id=443013)
File: backtrace
Comment 5 Matěj Cepl 2010-09-17 17:22:59 UTC 
Created attachment 448072 [details]
Interesting part of the thread backtrace where crash happened.
Comment 6 Matěj Cepl 2010-09-23 15:17:06 UTC 

*** This bug has been marked as a duplicate of bug 543165 ***
Note You need to log in before you can comment on or make changes to this bug.