After installing newest T-bird version, it would not start.

RESOLVED INCOMPLETE

Status

--
critical
RESOLVED INCOMPLETE
13 years ago
11 years ago

People

(Reporter: davy, Assigned: mscott)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1

I tried to upgrade version 1.0.7 repeatedly, also downloaded newest version again (2nd time, just in case), rebooted more than once, but neither allowing the installer program to start T-bird nor using my desktop shortcut starts the new version.  Fortunately, I saved the older version and have reloaded it.  I will try Opera now and wait for a less buggy Thunderbird version.  Incidentally, I have used Netscape products since the very first ones.

Reproducible: Always

Steps to Reproduce:
1. Start Thunderbird
2.
3.

Actual Results:  
NONE

Workaround:
Reload V. 1.0.7 and download Opera to try it out.  I am reluctant to delete Thunderbird's Pr

Reproducible: Always

Steps to Reproduce:
1.Start latest version of Thunderbird
2.
3.

Actual Results:  
T-bird won't start.


Nothing else was running but Zone Alarm, Spybot-SD and AVG free edition.

Comment 1

13 years ago
Created attachment 222148 [details]
errror file generated from trying to open thunderbird

Comment 2

13 years ago
I use the Thunderbird latest nightly builds and yesterday (15/05/2006) I recieved an update - 1.9:2006.50506 I now cannot open thunderbird even after rebooting. To reproduce start Thunderbird. Result is an error message stating "Thund~1.exe has encountered a problem and needs to close. We are sorry for the inconvenience." An error file is attached.
=> incomplete due to no response
if you still see this problem please comment
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.