program crashes all the time

RESOLVED EXPIRED

Status

Thunderbird
General
--
critical
RESOLVED EXPIRED
13 years ago
13 years ago

People

(Reporter: Rafał Maj, Assigned: Scott MacGregor)

Tracking

({crash})

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050306 Firefox/1.0.1 (Debian package 1.0.1-2)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050306 Firefox/1.0.1 (Debian package 1.0.1-2)


Crashes all the time. Perhaps this is because I recovered my settings from
damaged disk, and perhaps some settings, like for example adress book or
something is corrupted.

raf256@worf:~/$ mozilla-thunderbird
selected locale: en-US
observe:
nothing here: null
observe called
FILE: [xpconnect wrapped nsIFile]DOUBLE-CLICK: 250 --> -1 THRESHOLD: 8 --> -1
/usr/lib/mozilla-thunderbird/run-mozilla.sh: line 451:  9282 Segmentation fault
     "$prog" ${1+"$@"}
raf256@worf:~/$

raf256@worf:~$ mozilla-thunderbird
selected locale: en-US
observe:
nothing here: null
observe called
FILE: [xpconnect wrapped nsIFile]DOUBLE-CLICK: 250 --> -1 THRESHOLD: 8 --> -1
/usr/lib/mozilla-thunderbird/run-mozilla.sh: line 451:  9779 Segmentation fault
     "$prog" ${1+"$@"}
raf256@worf:~$




Reproducible: Always

Steps to Reproduce:
1. start thunderbird 
2. compose a new message and send it
3. compose a new message and start typing int the From: field




Perhaps this bug concerns only me, since I recovered Thunderbird settings by
restoring ~/.* files from damaged old HDD, and some files might been corrupted.

In any way this shpouldnt probably crash so badly (so warning/info would be nice).

Perhaps I can send my entire settings folder for Thunderbird developer.
disable extensions? Perhaps this thread is helpful:
http://mozdev.org/pipermail/quotecolors/2004-November/000035.html
Severity: blocker → critical
Keywords: crash
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.