Version: (using KDE KDE 3.2.3) Installed from: Mandrake RPMs OS: Linux bugs 66057, 69829 and 71596 are similiar, but the solutions don't apply. I have this problem since I activated "mark messages as read after X seconds" (X = 10), but since then I switched back, but the problem remains. I can correct the status using "mark all messages as read" from the folder menu. I have some folders in maildir-format (1 message - 1 file) and in those folders under .Mail the messages are missing the ":2S"-suffix, which marks (I think) read messages.
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.