Closed Bug 379623 Opened 17 years ago Closed 14 years ago

Clicking Delete or Junk does not allways close the message

Categories

(Thunderbird :: Mail Window Front End, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: u49640, Unassigned)

References

(Blocks 1 open bug)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
Build Identifier: 2.0

Sometimes (I havent found the pattern yet), Thunderbird does not move to the next message after deleting/marking as Junk a Message.

I havent found a pattern when this happens, but i have seen it several times.

The view is set to two panes (no message), message is opened in a separate full-screen window.

Clicking on delete/Junk still shows the message.

After manually closing the window, the message is moved (correctly) to trash/Junk.

Reproducible: Sometimes

Steps to Reproduce:
1.
2.
3.
I have the same problem. No pattern that I can find, but restarting Thunderbird will generally fix it.  

Clicking on Next goes to the next message and the previous action (delete or junk) processed correctly
I have almost same problem. Delete message from the message window (full window) and it doesn't disappear and move to next message in folder as it should. HOWEVER if the program is closed and restarted, the message deleted disappears, and when the Delete key or keyboard subsitute (Alt-E, del) is used next to delete another message, that message disappears from message window and Thunderbird moves to the next message in folder.
Reproducible about half the time for no apparent reason. 
The probem is somehow related to message filters. I think it started when migrating from one release to another (not sure which ones).  The problem disappeared when I deleted all of my message filters and reentered them. Same function, no more problems.  
Assignee: mscott → nobody
do you also see this with beta 1?
 http://www.mozillamessaging.com/en-US/thunderbird/early_releases/
(backup your profile first)
Whiteboard: closeme 2009-01-10
Still happens with latest official release, haven't tried the beta versions. I'm using:
version 2.0.0.18 (20081105)
Testing of beta would be helpful.

I'm not finding any other open bugs like this, which is surprising
Component: General → Mail Window Front End
QA Contact: general → front-end
Whiteboard: closeme 2009-01-10
Version: unspecified → 2.0
I have found this problem happens when I have newly downloaded messages. I have never seen the problem if I start Thunderbird and have no new messages. When I have new messages, however, the problem occurs only sometimes. As others have commented, the problem will go away after restarting Thunderbird (assuming no more new messages are downloaded after the restart :-)
I have exactly the same problem in Ubuntu 8.10.

This is the bug report I opened in launchpad:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/325691

This seems to be a duplicate of 427712 and 381265 (or the other way around)
(In reply to comment #4)
> do you also see this with beta 1?
>  http://www.mozillamessaging.com/en-US/thunderbird/early_releases/
> (backup your profile first)

Reporter (and others) could you try to see if it still happens with
http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-comm-1.9.1/ ?

In new beta release you can set ON option "close message window on delete"
reporter here:

I stopped using thunderbird since i switched to OSX due to missing SpotLight & Time Machine support, so i wont be able to test it
>In new beta release you can set ON option "close message window on delete"

Except on latest it work, as we have bug 498141
Blocks: junktracker
I am now using 3.0.4 and the problem has disappeared! Thanks developers! You can report this as RESOLVED
WFM per comment #14, as it worked in 3.0 and 2.x is a stability and security release branch.

Matthias, Paul and Allen B., freel free to reopen it if I'm wrong.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.