User-Agent: Opera/9.80 (Windows NT 6.1; U; de) Presto/2.5.22 Version/10.50 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:188.8.131.52) Gecko/20100227 Thunderbird/3.0.3 After a crash of Thunderbird the following error occours for every click in the folder list. after a lot of clicks and error warnings the error moved silently avay, but reappear after the next restart / crash Error: uncaught exception: [Exception... "Component returned failure code: 0x80520006 (NS_ERROR_FILE_TARGET_DOES_NOT_EXIST) [nsIMsgFolder.updateFolder]" nsresult: "0x80520006 (NS_ERROR_FILE_TARGET_DOES_NOT_EXIST)" location: "JS frame :: file:///C:/Program%20Files%20(x86)/Mozilla%20Thunderbird/modules/dbViewWrapper.js :: FolderNotificationHelper_notifyOnLoad :: line 131" data: no] Reproducible: Always Steps to Reproduce: 1. crash thunderbird 2. restart it 3. click on the folderlist Expected Results: moving right into the selected folder and show the emails in it
Did your disk drive fill up? Do you have a really overzealous anti-virus enabled? The error in question is a bizarre error path that should not happen.
Hm, I use ESET Nod32 (64-bit Version) for anti-virus. My drives are not filled up, there is more than enough space left. I saw some old entries in the prefs.js which are left from some addons. i will see wheather the problem occurs again.
do you see your messages once the exceptions go away? Are these real folders you're clicking on, or unified/smart folders?
I recently had a very similar error message when my file system (FAT32) got corrupted during a unclean shutdown. After fixing the file system and restoring the backup everything worked normal again.
NetAndroid ... (In reply to David :Bienvenu from comment #3) > do you see your messages once the exceptions go away? Are these real folders > you're clicking on, or unified/smart folders?
Whiteboard: [closeme 2012-03-01]
RESOLVED INCOMPLETE due to lack of response to last question. If you feel this change was made in error, please respond to this bug with your reasons why.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.