Bug 322741 - adding a large maildir to fresh akonadi setup never results in visible mail
Summary: adding a large maildir to fresh akonadi setup never results in visible mail
Status: RESOLVED FIXED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Maildir Resource (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-23 17:07 UTC by Chet Murthy
Modified: 2013-08-05 18:16 UTC (History)
1 user (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Chet Murthy 2013-07-23 17:07:18 UTC 
On Ubuntu Precise x86
ii  akonadi-server                                1.7.2-0ubuntu1                
ii  kontact                                       4:4.8.5-0ubuntu0.1            

(1) delete all akonadi-related files from various KDE dot-directories, also migratorrc files per a post I found

(2) reboot

(3) restart akonadi

(4) add a maildir with 30k message in 4 folders (<10k msgs per folder)

(5) click on one of the folders, wait, wait, wait, wait

Generally, it seems that akonadi can't deal with large mailboxes -- neither in POP, IMAP, nor local Maildir.



Reproducible: Always

Steps to Reproduce:
1.delete all akonadi-related files from various KDE dot-directories, also migratorrc files per a post I found
2.reboot
3.restart akonadi
4. add a maildir with 30k message in 4 folders (<10k msgs per folder)
5.click on one of the folders, wait, wait, wait, wait

It isn't even obvious how to debug.

Actual Results:  
I sit there in kmail, waiting for the message-list to display. Ditto in akonadiconsole.  Stopping/starting akonadi doesn't seem to help.


Expected Results:  
I should have seen my mail, yes?
Comment 1 Laurent Montel 2013-07-24 10:08:28 UTC 
you use a very old kontact package/akonadi package.
we will release in some days 4.11/1.10.1
so try with new packages.
Comment 2 Chet Murthy 2013-08-05 18:16:11 UTC 
OK, I've upgraded to 4:4.10.5-0ubuntu0.1 (Ubuntu Raring), and the original bug seems to have been resolved.  I have a new one, and will open a new ticket.