Bug 272099 - Local Kmail folders empty after upgrading to 4.6 beta5
Summary: Local Kmail folders empty after upgrading to 4.6 beta5
Status: RESOLVED DUPLICATE of bug 271913
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Migration (show other bugs)
Version: 4.6
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-30 23:31 UTC by Leon Maurer
Modified: 2011-05-10 21:33 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Look at all those empty folders. There should be thousands of emails in them. (28.11 KB, image/png)
2011-04-30 23:31 UTC, Leon Maurer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Leon Maurer 2011-04-30 23:31:02 UTC
Created attachment 59471 [details]
Look at all those empty folders. There should be thousands of emails in them.

Version:           4.6 beta4 (using KDE 4.6.2) 
OS:                Linux

(This is really for Kontact 4.5.95, which I think is 4.6 beta5, but I didn't seen that listed in the "Application Version" pulldown menu.)

Like it says, I upgraded to 4.6 beta5 from a stable version, and the emails I had stored locally don't show up. See the attached image. The KMail Folders akonadi resource seems to be set to the correct folder (~/.kde/share/apps/kmail/mail), and that folder still has ~3GB of emails in it. Everything else transfered smoothly.

Reproducible: Always
Comment 1 Leon Maurer 2011-05-01 01:50:42 UTC
I've found a strange fix:

You can see in my earlier attachment that KMail shows zero messages in the trash. However, when I moved a message to the trash, all of a sudden I could see the other messages that had been in the trash but weren't previously visible.

I can do the same with the other folders; after I move a message in to them, the previously invisible messages become visible.
Comment 2 Andre Woebbeking 2011-05-10 21:33:07 UTC

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