Summary: | mail status doesn't change from unread to read | ||
---|---|---|---|
Product: | [Applications] kmail | Reporter: | Hermann J. Beckers <hj.beckers> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | CC: | kollix |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Mandrake RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Hermann J. Beckers
2004-10-19 20:25:34 UTC
Hermann, thanks for reporting. The behavior you describe is not reproducible here. Unfortunately Mandrake ships an altered version of KMail, so it's hard to tell if it is something they changed that is causing this. Can you maybe give us a few more data points? Does it work with some folders? How about mbox folders? > ------- Additional Comments From adam kde org 2004-10-23 19:20 ------- ... > Can you maybe give us a few more data points? I started KMai from commandline. Whenever I switch to a new folder/message, the following message appears on standard/error-out: "QGDict::hashKeyString: Invalid null key" Even deleted messages (moved to Mülleimer/trash-bin) get a status of un-read. > Does it work with some folders? How about mbox folders? No, there is no difference. > > Can you maybe give us a few more data points? > > I started KMai from commandline. Whenever I switch to a new folder/message, > the following message appears on standard/error-out: > > "QGDict::hashKeyString: Invalid null key" Hm. > Even deleted messages (moved to Mülleimer/trash-bin) get a status of > un-read. That smells of index unavailability or permissions problems with the index files. > > Does it work with some folders? How about mbox folders? > > No, there is no difference. Newly created folders behave the same way? Permissions are ok, in your mail directory? No response. closing. If problem still occurs with current KDE 4.3, please reopen. |