Closed
Bug 552331
Opened 14 years ago
Closed 14 years ago
Fails to close completely if Window close x top right is pressed
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: chris, Unassigned)
Details
(Whiteboard: [add-on: SpamFighter])
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.1.8) Gecko/20100202 Firefox/3.5.8 (.NET CLR 3.5.30729) Build Identifier: 3.0.3 If I close the program with File > Exit it works fine. If I use the windows x to close the program, the window shut downs but the process continues to run and has to be cancelled with the Windows Task Manager Reproducible: Always Steps to Reproduce: 1. as described 2. 3. Expected Results: the program shut shut down completely and the process should stop running If you don't notice this you can end up with many copies of the program running
Comment 1•14 years ago
|
||
Ok XP right ? Have you tried safe mode? (see https://support.mozillamessaging.com/en-US/kb/Safe+Mode for more information)
Reporter | ||
Comment 2•14 years ago
|
||
Thanks for your help. I tried safe mode and it seems to close properly. I then disabled the add ons I am using, the one that seems to be the problem is SpamFighter. I will try and report this to them thanks for your help Chris
Updated•14 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
Whiteboard: [add-on: SpamFighter]
The 3.1.2 upgrade broke my spamfighter. I showed no spamfighter toolbar and could not send mail. Thunderbird just hung when trying to send any mail. Uninstalled spamfighter and could send mail normally. Also even before the upgrade spamfighter would not transfer deleted spam to the spamfighter folder so deleted mail could not be viewed. Too bad spamfighter worked great on outlook express.
Comment 4•14 years ago
|
||
(In reply to comment #3) > Uninstalled spamfighter and could send mail normally. Notify the author of spamfighter please !
I did notify Spamfighter of the problem with the 3.1.2 upgrade issue.
You need to log in
before you can comment on or make changes to this bug.
Description
•