Bug 677836 - [abrt] thunderbird-3.1.7-2.fc14: Process /usr/lib/thunderbird-3.1/thunderbird-bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] thunderbird-3.1.7-2.fc14: Process /usr/lib/thunderbird-3.1/thunderbird...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: thunderbird
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:cd6f30baa38b52f65b18cb45a5b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-16 01:31 UTC by Wendell Baker
Modified: 2011-12-07 13:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-07 13:28:18 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (106.78 KB, text/plain)
2011-02-16 01:31 UTC, Wendell Baker 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Wendell Baker 2011-02-16 01:31:44 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/lib/thunderbird-3.1/thunderbird-bin
comment: Again, seems like a timing play accessing multiple imap services at once.
component: thunderbird
executable: /usr/lib/thunderbird-3.1/thunderbird-bin
kernel: 2.6.35.10-74.fc14.i686.PAE
package: thunderbird-3.1.7-2.fc14
rating: 4
reason: Process /usr/lib/thunderbird-3.1/thunderbird-bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1297728317
uid: 500

How to reproduce
-----
1. idle?
2.
3.
Comment 1 Wendell Baker 2011-02-16 01:31:45 UTC 
Created attachment 479001 [details]
File: backtrace
Comment 2 Martin Stransky 2011-12-07 13:28:18 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!
Note You need to log in before you can comment on or make changes to this bug.