Bug 174756 - Account settings lost at upgrade time.
Summary: Account settings lost at upgrade time.
Status: RESOLVED DUPLICATE of bug 165320
Alias: None
Product: kmail
Classification: Applications
Component: config compatibility (show other bugs)
Version: 1.10.3
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2008-11-10 01:47 UTC by Ian Turner
Modified: 2009-03-16 14:02 UTC (History)
4 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 Ian Turner 2008-11-10 01:47:14 UTC 
Version:            (using KDE 4.1.2)
OS:                Linux
Installed from:    Ubuntu Packages

After upgrading to Ubuntu 8.10 and restarting KDE, I discovered that all my kmail account settings were lost. Identities (roles) were maintained, but information on sending and receiving servers was no more. Previously configured servers used dimap, and at least some of the messages appear to still be stored in ~/.kde/share/apps/kmail/dimap.

If any other information can be of use, let me know.
Comment 1 Ian Turner 2008-11-10 01:50:39 UTC 
After restarting kmail, it appears that actually only "Receiving" accounts were lost, and that "Sending" accounts remain.
Comment 2 Techwolf 2008-11-13 21:13:04 UTC 
I am having the same problem. Just upgrade my gentoo system to 4.1.2 to 4.1.3 and lost all recieving accounts. Same thing happens when I went from 3.x.x to 4.1.2.
Comment 3 George Kiagiadakis 2008-11-25 00:32:54 UTC 
Did you upgrade from a kde3 version to a kde4 version? or you were using the kde4 version before the upgrade too? Are you sure the ~/.kde/share/config/kmailrc file is preserved? Maybe you were using ~/.kde4 as a settings prefix before and now you are using ~/.kde ?
Comment 4 Ian Turner 2008-11-25 06:12:51 UTC 
My upgrade was from 3.x to 4.1.2; it is quite possible that the kmailrc file was not preserved, though I certainly didn't delete it manually.
Comment 5 Jim Lieb 2008-12-02 00:41:02 UTC 
I have managed to cause this problem on a full filesystem as well. Although I
have not inspected the code itself, it seems that kmail re-writes
~/.kde/share/config/kmailrc with app state such as current message in folder
etc.  If this write fails for any reason, the kmailrc file is corrupted. If
this analysis is true, I strongly suggest that configuration information
that is both persistent and only modified under Settings-> be in kmailrc
and the rest of the semi-persistent data such as current folder state
be somewhere else. This would both reduce the extra I/O overhead and harden
kmail to incidents such as this.  If a local cache/persistent state store
is needed, and it is useful, why not use something like sqlite which is
hardened better than writing a full flat file from walking some internal
copy of everything.
Comment 6 Jaime Torres 2008-12-02 12:14:02 UTC 
@Jim
I've also had the problem with a full filesystem. see bug 175680
Comment 7 Jaime Torres 2009-01-06 13:33:11 UTC 
Except the full filesystem, this bug may be related to bug 165320
Comment 8 Thomas McGuire 2009-03-16 14:02:27 UTC 
> Except the full filesystem, this bug may be related to bug 165320

Right, it is, thanks.

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