568645 - after some time, cannot drag a message from IMAP inbox to local folder

Status: RESOLVED INCOMPLETE

(Thunderbird :: Folder and Message Lists, defect)

Description

[Jason Purdy]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US) AppleWebKit/533.3 (KHTML, like Gecko) Chrome/5.0.360.5 Safari/533.3
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100423 Thunderbird/3.0.4

After some period of time, I can not drag a message from my INBOX into a local folder. I click on the message, but when I start dragging, nothing happens. The cursor doesn't change and the release on the destination folder does nothing.

If I restart Thunderbird, it fixes itself.

Reproducible: Always

Steps to Reproduce:
1. Run firefox for a while
2. Drag a message out of the INBOX
3. Cursor doesn't change and message isn't moved.
Actual Results:  
The message isn't moved.

Expected Results:  
The message to be filed in the folder where I released the mouse button.

Comment 1

[Jens Müller (:tessarakt)]

I had the same issue once, but I don't remember whether I filed a bug.

Comment 2

[Jens Müller (:tessarakt)]

Maybe 461807, but there's not much info.

Comment 3

[Jens Müller (:tessarakt)]

Seemed to appear here, but no info as well: http://forum.mandriva.com/viewtopic.php?t=127546

Comment 4

[Jens Müller (:tessarakt)]

http://groups.google.com/group/mailing.freebsd.ports-bugs/browse_thread/thread/8601d58e5d3400e5/d34736b129c9c96f?hl=de&ie=UTF-8&oe=utf-8&q=thunderbird+restart+drag+message#d34736b129c9c96f

https://bugzilla.mozilla.org/show_bug.cgi?id=355248

But that was looooong ago ...

Comment 5

[Wayne Mery (:wsmwk)]

Do you still see this issue when using version 5 or 6 (due out a week)?
- If you no longer see the problem, please set status to RESOLVED, and set resolution to WORKSFORME.
- If you still see the problem, please provide updated details, and any additional steps needed to reproduce the problem.

Comment 6

[Joshua Cranmer [:jcranmer]]

RESOLVED INCOMPLETE due to lack of response to previous question. If you feel this change was in error, please respond to this bug with your reasons why.