User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 Sometimes when I click the Mark button to toggle the read status of a message, it takes a few seconds. On a few occasions this has lead me to believe that I didn't click it properly or the click didn't register, so I clicked it again. When I then notice is that the read status toggles not twice but FOUR times. Note that I use indexing and when I click the button I notice an indexing message in the status bar; perhaps this is related. Reproducible: Always Steps to Reproduce: 0. Select an unread message 1. Click the mark button 2. Click it again without much delay (< 1 sec) Actual Results: Message status changes as follows: 1. UNREAD -> READ 2. READ -> UNREAD 3. UNREAD -> READ 4. READ -> UNREAD Expected Results: Message status changes as follows: 1. UNREAD -> READ 2. READ -> UNREAD

Reproducible easily on Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20100111 Lightning/1.0b2pre Thunderbird/3.0.1 ID:20100111101938.

does this still occur with version 5 or current trunk build? xref https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&emailreporter1=1&emailcc1=1&short_desc=read&field0-0-0=short_desc&bug_severity=blocker&bug_severity=critical&bug_severity=major&bug_severity=normal&bug_severity=minor&type0-0-1=substring&field0-0-1=keywords&type1-0-1=allwordssubstr&classification=Client%20Software&classification=Components&emailtype1=substring&query_format=advanced&short_desc_type=allwords&email1=vseerr&type0-0-0=anywordssubstr&value0-0-0=mark%20change&field1-0-0=short_desc&product=MailNews%20Core&product=Thunderbird&field1-0-1=short_desc&list_id=536544

I just tried this in inbox on 5.0 and it behaved the same as reported: Double click yielded four changes of state. Single click results in one change of state. Thanks

This looks like bug 513235 and/or bug 306739. However, I can no longer reliably reproduce with Thunderbird 5. I believe I have noticed the same effect, though, at times.

David, can you attach a protocol log file to the bug imap:5,timestamp please see https://wiki.mozilla.org/MailNews:Logging