Closed Bug 584655 Opened 14 years ago Closed 13 years ago

messages can't be deleted or moved

Categories

(Thunderbird :: Folder and Message Lists, defect)

x86_64
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: jungwirth1m, Unassigned)

Details

(Whiteboard: [closeme 2012-02-21])

Attachments

(2 files)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2.8) Gecko/20100802 Lightning/1.0b2 Thunderbird/3.1.2 No messages can't be deleted or moved to another folder. After a restart of Thunderbird, all works as it should. Problem also existed in earlier builds. Reproducible: Sometimes Steps to Reproduce: I don't know how to exact reproduce it. It seems to happen under the following conditions. Thunderbird runs for longer time, you minimize it several times while receiving messages (slow internet connection) and open folders before messages are completely received. This bug is not related to the following bugs 547958, 579129, 540396.
Attached file Video of the bug
Today, thunderbird got the bug mentioned above directly after start and downloading e-mails. no folder was opened while downloading, nothing minimized. After downloading of mails, i tried to delete a message. Nothing happened.
Do you go offline / online when this happens ?
(In reply to comment #3) > Do you go offline / online when this happens ? the last time the bug happened, i simply opened thunderbird, it received mails. i did nothing. after i opened the folder i couldn't move / delete messages.
Wayne ideas ?
are you over disk quota? attach protocol log file for imap:5 or pop3:5 (depending on your account definition) https://wiki.mozilla.org/MailNews:Logging
Attached file Log-File
Here's the log-file as requested by Wayne Mery. I'm not over disk quota. the bug only occurs only from time to time, so it's probably hard to find.
Nothing (out of the ordinary) in the log file; normal POP session, no messages. Did the inability to delete occur after the attached log was captured, or was operation normal in that case ? Is there anything in the Error Console (Tools->Error) console when a delete fails ? (When you get the "can't delete" problem, "clear" the Error Console, then try the delete to see if new entry is added). For future reference, if bug numbers are preceded by "Bug ", Bugzilla will automatically make them clickable links. For example (as in the description): Bug 547958, Bug 579129, Bug 540396.
I have the same problem, also intermittent. Sometimes when I try to delete I get "The operation failed because an other operation is using the folder. Please wait for that operation to finish and then try again." But most times I get no error message at all, it just doesn't do anything. This is true regardless of how I try and delete (delete button, delete key, right context menu). Either way, nothing appears in the Error Console. Also, when this happens, it is also impossible for me to close alerts for the add-on ReminderFox. If I restart, everything works again, until the next time it doesn't. (I don't know if ReminderFox could be the problem, but since it's intermittent I would have to uninstall ReminderFox and leave it off for a couple of days to figure it out, and then I'd miss all my appointments.)
jungwirth, please reply to comment 8. thanks
Whiteboard: [closeme 2011-12-15]
i created a new log-file till the error occurs, i got something which looks interesting inside the log: 0[b35140]: Clearing server busy in POP3_FREE 0[b35140]: Clearing running protocol in POP3_FREE 0[b35140]: Clearing server busy in OnStopRequest 0[b35140]: Calling ReleaseFolderLock from ~nsPop3Sink 0[b35140]: ReleaseFolderLock haveSemaphore = FALSE
0[b35140]: POP auth: server caps 0x844B3, pref 0x6000, failed 0x0, avail caps 0x4000 0[b35140]: (GSSAPI = 0x100000, CRAM = 0x2000, APOP = 0x4000, NTLM = 0x8000, MSN = 0x10000, PLAIN = 0x1000, LOGIN = 0x800, USER/PASS = 0x400) 0[b35140]: trying auth method 0x4000 0[b35140]: POP APOP 0[b35140]: POP3: Entering state: 6 0[b35140]: POP3: Entering state: 50 0[b35140]: SendPassword() 0[b35140]: APOP login 0[b35140]: Logging suppressed for this command (it probably contained authentication information) 0[b35140]: Entering NET_ProcessPop3 28 0[b35140]: POP3: Entering state: 3 0[b35140]: RECV: +OK 0 messages (0 octets). 0[b35140]: POP3: Entering state: 31 0[b35140]: NextAuthStep() 0[b35140]: login succeeded 0[b35140]: POP3: Entering state: 7 0[b35140]: SEND: STAT 0[b35140]: Entering NET_ProcessPop3 9 0[b35140]: POP3: Entering state: 3 0[b35140]: RECV: +OK 0 0 0[b35140]: POP3: Entering state: 8 0[b35140]: BeginMailDelivery acquiring semaphore 0[b35140]: Calling ReleaseFolderLock from AbortMailDelivery 0[b35140]: ReleaseFolderLock haveSemaphore = TRUE 0[b35140]: POP3: Entering state: 22 0[b35140]: SEND: QUIT 0[b35140]: Entering NET_ProcessPop3 6 0[b35140]: POP3: Entering state: 3 0[b35140]: RECV: +OK 0[b35140]: POP3: Entering state: 40 0[b35140]: POP3: Entering state: 23 0[b35140]: POP3: Entering state: 25 0[b35140]: Clearing server busy in POP3_FREE 0[b35140]: Clearing running protocol in POP3_FREE 0[b35140]: Clearing server busy in OnStopRequest 0[b35140]: Calling ReleaseFolderLock from ~nsPop3Sink 0[b35140]: ReleaseFolderLock haveSemaphore = FALSE
That log looks OK - we're releasing the folder lock. The second time it doesn't do anything because we don't have the semaphore, because the first release freed it.
after the log-file was created, it wasn't possible to delete a message in the folders of thunderbird. the problem got fixed after restart.
It turned out in my case the problem was actually outside of Thunderbird. I was using automatic backup software, and it was locking files as it backed them up (even though I set it not to in the options) and once I turned it off, the problem went away.
No virus scanner running here, and also no backup software.
Charles, thanks for that info. What software are you using?
jungwirth, version 10 comes out soon. can you give it a try?
Whiteboard: [closeme 2011-12-15] → [closeme 2012-02-21]
of course. you mean beta or final?
no problems till now with version 10. did something in the code for handling messages / folders change? will try further.
RESOLVED WORKSFORME per comment 20.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: