Bug 579736 - [abrt] crash in thunderbird-3.0.4-1.fc12: Process /usr/lib/thunderbird-3.0/thunderbird-bin was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in thunderbird-3.0.4-1.fc12: Process /usr/lib/thunderbird-3.0/th...
Keywords:
Status: CLOSED DUPLICATE of bug 543165
Alias: None
Product: Fedora
Classification: Fedora
Component: thunderbird
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a9979c43b4562930fbc8af522d8...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-06 12:27 UTC by Trevor Mettam
Modified: 2018-04-11 16:58 UTC (History)
7 users (show)

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

Attachments (Terms of Use)
File: backtrace (35.64 KB, text/plain)
2010-04-06 12:27 UTC, Trevor Mettam 		no flags Details
Part of the thread where crash happened (1.85 KB, text/plain)
2010-09-23 10:36 UTC, Matěj Cepl 		no flags Details
View All

Description Trevor Mettam 2010-04-06 12:27:32 UTC 
abrt 1.0.8 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/thunderbird-3.0/thunderbird-bin
comment: Random crash whilst closing Thunderbird.
component: thunderbird
executable: /usr/lib/thunderbird-3.0/thunderbird-bin
kernel: 2.6.32.10-90.fc12.i686
package: thunderbird-3.0.4-1.fc12
rating: 4
reason: Process /usr/lib/thunderbird-3.0/thunderbird-bin was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
Comment 1 Trevor Mettam 2010-04-06 12:27:36 UTC 
Created attachment 404691 [details]
File: backtrace
Comment 2 Stefano Bianchi 2010-04-22 08:36:03 UTC 

How to reproduce
-----
1. Close the thunderbird window
2.
3.
Comment 3 Matěj Cepl 2010-09-23 10:36:02 UTC 
Created attachment 449170 [details]
Part of the thread where crash happened
Comment 4 Matěj Cepl 2010-09-23 11:15:08 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.