Bug 163962 - Mail flags lost on restart
Summary: Mail flags lost on restart
Status: RESOLVED DUPLICATE of bug 34190
Alias: None
Product: kmail
Classification: Applications
Component: index (show other bugs)
Version: 1.9.6
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2008-06-13 12:39 UTC by Michael Langerhorst
Modified: 2010-01-26 00:54 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Langerhorst 2008-06-13 12:39:25 UTC 
Version:           1.9.6 (enterprise 0.20070907.709405) (using 3.5.8, Kubuntu (gutsy) 4:3.5.8-0ubuntu3.4)
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.22-14-generic

When I flag Mails in the Income-Folder as "Important (rad flag)" or as "ToDo", these flags get lost after reboot. Is this problem already solved in higher versions?
Comment 1 Thomas McGuire 2008-06-17 18:38:13 UTC 
> Is this problem already solved in higher versions? Is this problem already solved in higher versions? 
I general, yes. Are you using IMAP or POP3?

This problem usually means your index file is destroyed for some reason.
You don't, by chance, have problems with your clock or with incorrect file dates?
Comment 2 Michael Langerhorst 2008-06-18 09:19:46 UTC 
The problem I described, occures approx. every 4 to 10 reboots.

I use only POP3

My clock works fine (with pool.ntp.org).
File dates should be fine but I haven't put very much notice on that issue up to now. I think with online-sync of the clock this problem can not arise (in case that I have it)...?

But if higher versions of kmail don't have that problem any more, it's fine for me. Thanks for your reply.
Comment 3 Michael Leupold 2009-04-04 17:30:36 UTC 
Hi Michael,

did the problems go away with recent versions of KMail?
Comment 4 Björn Ruberg 2010-01-26 00:54:03 UTC 
Sadly no reply. I see this as a duplicate at the moment

*** This bug has been marked as a duplicate of bug 34190 ***