Bug 586793

Summary: [abrt] crash in thunderbird-3.0.4-2.fc13: Process /usr/lib/thunderbird-3.0/thunderbird-bin was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Pavel Alexeev <pahan>
Component: thunderbirdAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: gecko-bugs-nobody, mcepl
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:66cc711921c3322877c2f2e0baab09117ad764a8
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-09-21 09:23:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
Part of the thread where crash happened none

Description Pavel Alexeev 2010-04-28 11:48:13 UTC 
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/thunderbird-3.0/thunderbird-bin
comment: It happened 2 times on letter writing. After it I can't reproduce it more...
component: thunderbird
executable: /usr/lib/thunderbird-3.0/thunderbird-bin
global_uuid: 66cc711921c3322877c2f2e0baab09117ad764a8
kernel: 2.6.33.1-24.fc13.i686
package: thunderbird-3.0.4-2.fc13
rating: 3
reason: Process /usr/lib/thunderbird-3.0/thunderbird-bin was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 Pavel Alexeev 2010-04-28 11:48:17 UTC 
Created attachment 409786 [details]
File: backtrace
Comment 2 Pavel Alexeev 2010-04-28 13:12:40 UTC 
Package: thunderbird-3.0.4-2.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


Comment
-----
This happened 3d times. But I still can't reproduce when I want.
Comment 3 Matěj Cepl 2010-09-21 09:22:25 UTC 
Created attachment 448657 [details]
Part of the thread where crash happened
Comment 4 Matěj Cepl 2010-09-21 09:23:55 UTC 
Thank you for taking the time to report this bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash, because there are not enough debugging symbols loaded (probably abrt failed to load them).

Unfortunately, we cannot use this backtrace.

Closing as INSUFFICIENT_DATA.