Bug 508598 - Thunderbird appears to randomly seg-fault
Thunderbird appears to randomly seg-fault
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: thunderbird (Show other bugs)
10
All Linux
low Severity medium
: ---
: ---
Assigned To: Gecko Maintainer
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-06-28 21:15 EDT by morgan read
Modified: 2009-06-29 10:30 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-06-29 10:30:01 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
terminal output t'bird crash (5.21 KB, text/plain)
2009-06-28 21:15 EDT, morgan read
no flags Details

  None (edit)
Description morgan read 2009-06-28 21:15:14 EDT
Created attachment 349721 [details]
terminal output t'bird crash

Description of problem:
Use T'bird, then it suddenly dies for no apparent reason.  I recently started running if from gnome terminal and caught the following:
$ thunderbird
/usr/lib/thunderbird-2.0.0.21/run-mozilla.sh: line 131:  3418 Segmentation fault      "$prog" ${1+"$@"}
$

Version-Release number of selected component (if applicable):
Thunderbird 2.0.0.21, Copyright (c) 1998-2009 mozilla.org

How reproducible:
Intermittent

Steps to Reproduce:
1. Run T'bird
2. Wait for fault
3.
  
Actual results:
Seg-fault

Expected results:
No seg-fault

Additional info:
I caught the attached info/back-trace from gnome terminal a little while back, it seems to show some error with syncmlplugin@funambol.com and a reference to "line 131" as above
Comment 1 Matěj Cepl 2009-06-29 10:30:01 EDT
I suspect that this is really bug in the funambol plugin. If you think otherwise, please, reopen this bug with backtrace from gdb (and run debuginfo-install thunderbird before).

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