Summary: | Emails being composed are no longer autosaved, and lost on Kmail/Kontact shutdown. | ||
---|---|---|---|
Product: | [Unmaintained] kmail | Reporter: | P B <kde.bugs> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | balazs, bjoern, gree, leo, matej, renard, sibskull |
Priority: | NOR | ||
Version: | 1.13.1 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
P B
2010-03-12 16:41:27 UTC
Strange. I had a kmail crash recently and the mail draft in a composer window had been completly restored on restart. Running 4.4.0 here, so I cannot confirm. *** Bug 232666 has been marked as a duplicate of this bug. *** P B, it may be another much more minor problem. Can you please try to reproduce it (e.g. start composing, than killing kmail after a while) and then navigate into $HOME/.kde4/share/apps/autosave/ folder and check if composed message is here? (in mbox format) For me it seems that autosaving works correctly, but kmail forgets to open autosaved messages upon crash. Matěj My KDEHOME is .kde/ rather than .kde4/, and also, the folder I think corresponding to what you're talking about was in .kde/share/apps/kmail/autosave And furthermore, it wasn't mbox format, but Maildir. But, yes, lo and behold, there were the missing drafts. I created another email just now, closed Kontact, looked in the directory, and there it was. Restarted Kontact, but nothing was restored. Same here with kmail 1.13.5, the mails are in the autosave/cur folder but doesn't get opened when kmail (kontact) is restarted. I confirm too. KMail does not open mail but autosaved mail are in .kde/share/apps/kmail/autosave/cur/xxxx In my case the autosaved emails are where they should be and running kmail from konsole spits this out: kmail(30147) KMKernel::recoverDeadLetters: Unable to open autosave file "1281943446.29825.1hPE6" Considering this as confirmed now. Has anyone an idea why these files cannot be opened? Can you do it with a text editor? (In reply to comment #8) > Considering this as confirmed now. Has anyone an idea why these files cannot be > opened? Can you do it with a text editor? Yes, I can open them with a text editor without a problem. The file is 600 and owned by my user. This bug is solved for me in 1.13.5 (KDEPIM 4.4.6). I confirm. The bug is gone since 4.4.6 Very good. One less. |