Open
Bug 411122
Opened 18 years ago
Updated 5 years ago
Junk log does not clear
Categories
(SeaMonkey :: MailNews: Account Configuration, defect)
SeaMonkey
MailNews: Account Configuration
Tracking
(Not tracked)
NEW
People
(Reporter: ok34, Unassigned)
Details
User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.8.1.11) Gecko/20071129 SeaMonkey/1.1.7 (PmW)
Build Identifier: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.8.1.11) Gecko/20071129 SeaMonkey/1.1.7 (PmW)
When I want to clear the junk mail log (Edit | Preferences | Mail & Newsgroups | Junk Mail | Show Log | Clear Log | Close | OK) the junk mail log remains unchanged.
Reproducible: Always
Steps to Reproduce:
1.(Edit | Preferences | Mail & Newsgroups | Junk Mail | Show Log | Clear Log | Close | OK)
2.(Edit | Preferences | Mail & Newsgroups | Junk Mail | Show Log)
Actual Results:
The log remains totally unchanged.
Expected Results:
The log should be gone.
I could not find an e-mail category (MailNews) to put this bug in. It's not really "main mail window" nor "offline". So I marked this one "General".
| Reporter | ||
Comment 1•18 years ago
|
||
Update: The bug seems to be size-related. Since I could not clear my junk log, it grew and grew in size, and all of a sudden I could clear it. Now it's small again - but once again I cannot clear it...
Comment 2•18 years ago
|
||
Problem could be re-produced today, with long running(a few days) Seamonkey.
When problem occurred on Seamonkey 1.1.7, following error message was issued.
> Error: uncaught exception: [Exception... "Component returned failure code:
> 0x80520015 (NS_ERROR_FILE_ACCESS_DENIED) [nsIFile.remove]"
> nsresult: "0x80520015 (NS_ERROR_FILE_ACCESS_DENIED)"
> location: "JS frame :: chrome://messenger/content/junkLog.js :: clearLog :: line 65" data: no]
Confirming.
AFAIR, my junk log could be cleared in the past, if just after restart of Seamonkey and if no mail download occurred when start up.
And, AFAIR, this problem occurred on Thunderbird (1.5 & 2.0) too.
Cause is possibly Bug 231923 (...log.html is not closed once opened)
WORKAROUND: Terminate Seamonkey, and delete junklog.html manually.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 3•17 years ago
|
||
Can you reproduce with SeaMonkey v2.0a1pre ?
Assignee: general → mail
Component: General → MailNews: Account Manager
OS: All → OS/2
QA Contact: general
Hardware: Other → PC
Version: unspecified → SeaMonkey 1.1 Branch
Comment 4•17 years ago
|
||
I still get the same error as in comment 2 with Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.9.1b2pre) Gecko/20081022 SeaMonkey/2.0a2pre, but as it's reproducible (sometimes) on other OSs I set OS=All, at least after a line was added to it in the current session. (If I don't open MailNews at all before I try then I can clear the log without problems.)
It's a bit weird, because all sysinfo tools tell me that this file isn't specifically locked, even after it was written to, so it should be possible to remove it without problems... I wonder, however, if the file should be somehow closed before trying to remove it, the *File::Remove() functions don't seem to do that.
OS: OS/2 → All
Hardware: PC → All
Version: SeaMonkey 1.1 Branch → Trunk
Comment 5•16 years ago
|
||
I could reproduce this with SeaMonkey 2.0 on Win XP.
According to procexp+procmon, the file junklog.html is kept open after first use. Then Clear Log tries to delete an open file. This fails with a sharing violation on Windows and OS/2. On Linux & friends, the file delete should work but further log entries will probably be written to the old (now hidden) filedesc until next restart.
Workaround: Restart SeaMonkey, Clear Log before first message is retrieved.
You need to log in
before you can comment on or make changes to this bug.
Description
•