Bug 305269 - Cannot see new top-level IMAP folders
Summary: Cannot see new top-level IMAP folders
Status: RESOLVED FIXED
Alias: None
Product: kmail2
Classification: Applications
Component: folders (show other bugs)
Version: 4.9.1
Platform: Gentoo Packages Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 314466 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-08-16 15:44 UTC by Karl-Johan Karlsson
Modified: 2015-09-10 14:08 UTC (History)
12 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Karl-Johan Karlsson 2012-08-16 15:44:38 UTC
With the fix of bug 303248 in KMail 4.9.0, I can now create new top-level IMAP folders, and they appear in the server's filesystem and in other IMAP clients running against the same server (which is Dovecot 2.1.9 on Linux). However, I cannot see them in KMail. I have tried doing "Update folder and its subfolders" on the account, enabling server-side subscriptions and selecting the folder, restarting KMail, restarting Akonadi ("akonadictl restart"). Nothing makes the new top-level folders show up in the folder list. New folders created under an existing folder appear immediately.

Reproducible: Always

Steps to Reproduce:
1. Right-click an IMAP account.
2. Select "Add Folder...".
3. Enter a name.
4. Click "OK".
Actual Results:  
The folder is created on the IMAP server. It does not appear in the KMail folder list.

Expected Results:  
The new folder should show up in the KMail folder list, on the same level in the tree as "Inbox" and all the other top-level folders.
Comment 1 Franz Trischberger 2012-09-07 09:29:15 UTC
Same here with kde-4.9.1. Gentoo downstream bug:
https://bugs.gentoo.org/show_bug.cgi?id=434156

I also tried to simply create new folder via the webinterface - they don't show up in kmail, even when I sunbscribe to it.
Comment 2 Myriam Schweingruber 2012-09-10 01:47:44 UTC
Setting status to confirmed.
Comment 3 Bernd Oliver Sünderhauf 2012-11-24 22:38:06 UTC
I can confirm this for KDE 4.9.3 on Chakra.

Seems to be a case of "one bug covering others", because sometimes the folder isn't even created on the IMAP server. But that will be easier to triage as soon as this one here has been fixed.
Comment 4 Henri 2013-02-05 18:22:14 UTC
Same here with Mint 13 & 14 Kde 4.9.5.
Comment 5 Henri 2013-02-05 18:25:08 UTC
*** Bug 314466 has been marked as a duplicate of this bug. ***
Comment 6 Andreas Hartmetz 2013-02-23 20:39:55 UTC
I can confirm this with the latest KDE and kdepim compiled from git. I've created a folder "Mesa-dev" for a new mailing list subscription. No amount of synchronizing could make it appear, and there was an error from MySQL about a duplicate entry "Mesa-dev" in the collections table.
So I ran akonadiconsole and looked at the collections table. All other folders, for example "kde-devel", had storage locations like "/kde-devel". But Mesa-devel had "iMesa-dev"! I changed it to "/Mesa-dev", restarted Akonadi and KMail and I could finally see the folder.
See also: bug 306390 for more weirdness involving the letter "i".
Comment 7 Andreas Hartmetz 2013-02-23 20:51:54 UTC
I have reproduced this bug again while reproducing bug 306390, using a folder called "aiiiiiiiii". Here are the relevant Akonadi error messages with some context:

akonadi_maildispatcher_agent(11171) OutboxQueue::Private::addIfComplete: Item 734341 is queued to be sent manually.
akonadi_imap_resource_4(11169)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
akonadi_nepomuk_feeder(11174) Akonadi::NepomukFeederAgent::checkMigration:
akonadi_imap_resource_2(11168)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
Error during executing query "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6)" :  "Duplicate entry '342-a' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Error during insertion into table "CollectionTable" "Duplicate entry '342-a' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement" 
akonadi_mixedmaildir_resource_1(11173) KMIndexReader::readHeader: DIRTY!
akonadi_mixedmaildir_resource_1(11173) KMIndexReader::readHeader: Index File sizeOfLong is 4 while sizeof(long) is 8 !
akonadi_nepomuk_feeder(11174) FindUnindexedItemsJob::itemsRetrieved: Akonadi Query took(ms):  12876
akonadi_nepomuk_feeder(11174) FindUnindexedItemsJob::itemsRetrieved: copy took(ms):  171
akonadi_mixedmaildir_resource_1(11173)/akonadiresource (maildir): "NO [LRCONFLICT] Resource akonadi_mixedmaildir_resource_1 tries to modify item 632988 ({31bf5901-6977-480b-aace-4c495bb9a4ae}) (in collection 110) with dirty payload, aborting STORE.
" 
akonadi_nepomuk_feeder(11174) FindUnindexedItemsJob::retrieveIndexedNepomukResources:
akonadi_imap_resource_4(11169)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
akonadi_imap_resource_2(11168)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
Error during executing query "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6)" :  "Duplicate entry '342-a' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Error during insertion into table "CollectionTable" "Duplicate entry '342-a' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement" 
akonadi_nepomuk_feeder(11174) FindUnindexedItemsJob::retrieveIndexedNepomukResources: Nepomuk Query took(ms):  78769
akonadi_nepomuk_feeder(11174) FindUnindexedItemsJob::retrieveIndexedNepomukResources: Found  413  unindexed items.
akonadi_nepomuk_feeder(11174) FeederQueue::itemHeadersReceived: 9
Comment 8 András Manţia 2013-03-28 21:45:46 UTC
Git commit d8fd7a28e7d6d8a89dd398311d423118ff529718 by Andras Mantia.
Committed on 28/03/2013 at 22:45.
Pushed by amantia into branch 'KDE/4.10'.

1) Fix creation of new toplevel folders (and all its subfolder): it used to generate a broken remote id and separtor ("i") causing weird problems.
2) Make sure toplevel imap folders are shown immediately, without a need to sync the account (workarounds an ETM bug 291143)
3) Warn the user if creating a folder failed on server-side and remove the folder locally. Otherwise if creation failed, it was impossible to create again a folder with the same name,
as it was already a folder with that name in the akonadi cache...
4) Make sure deleting folder "foo" doesn't deleted all folders starting with "foo" as it did before.
5) Just fix folder deletion. :) It could fail in certain cases.
6) Fix and adapt the tests.

Reporters of closed bugs: if you can still see the bug in 4.10.2, please reopen and state the details.

REVIEW: 109276
FIXED-IN: 4.10.2291143291143
Related: bug 312435, bug 301088, bug 292418, bug 305987, bug 291143

M  +6    -1    resources/imap/addcollectiontask.cpp
M  +1    -1    resources/imap/changecollectiontask.cpp
M  +16   -0    resources/imap/imapresource.cpp
M  +7    -0    resources/imap/imapresource.h
M  +11   -8    resources/imap/removecollectionrecursivetask.cpp
M  +1    -0    resources/imap/removecollectionrecursivetask.h
M  +10   -0    resources/imap/resourcetask.cpp
M  +2    -0    resources/imap/resourcetask.h
M  +4    -1    resources/imap/tests/dummyresourcestate.cpp
M  +7    -5    resources/imap/tests/testremovecollectiontask.cpp

http://commits.kde.org/kdepim-runtime/d8fd7a28e7d6d8a89dd398311d423118ff529718
Comment 9 Karl-Johan Karlsson 2013-04-12 19:02:25 UTC
I'm still seeing this bug on KDE 4.10.2, built from source on Gentoo, and I've rebooted after I installed it. Specifically to your patch, I'm running:

[I] kde-base/kdepim-runtime
     Available versions:  (4) 4.4.11.1-r1^t 4.10.1^t{tbz2} (~)4.10.2^t{tbz2}
       {aqua debug google kolab}
     Installed versions:  4.10.2(4)^t{tbz2}(10:51:10 2013-04-08)(-aqua -debug -google -kolab)

Procedure:
1. Right-click the IMAP server in the folder tree.
2. Select "Add Folder...".
3. As name, enter "Test".
4. Click "OK".

Results:
The new folder, correctly populated with Maildir subfolders, appears in the IMAP server's file system.
The new folder does not appear in KMail's folder tree.
Right-clicking the server in IMAP server in the folder tree and selecting "Update folder and its subfolders" makes no difference.
Exiting KMail, restarting Akonadi with "akonadictl stop", "akonadictl status" until everything is in state "stopped", "akonadictl start", and restarting KMail makes no difference.
Using another IMAP client to move an unread mail into the new folder makes no difference.
The only place in KMail I can see the new folder is if I right-click the IMAP server in the folder tree and select "Serverside Subscriptions...". I have server-side subscriptions turned off, and toggling it makes no difference.
Attempting to create the folder again gives this error message: "Could not create folder: Could not create collection Test resourceId: 6". This error persist even after I remove the folder on the server.

Using "kdebugdialog" to enable everything matching "kdepim" and "kmail" gives only the following output on creating a folder ("Test2" instead of "Test", since I can't create a new "Test" even after removing it on the server):

akonadi_imap_resource_0(17320)/kdepimlibs (kimap) AddCollectionTask::doStart: New folder:  "Test2"
kmail2(17355) KMKernel::instanceStatusChanged: A Resource started to synchronize, starting a mail check.
Error during executing query "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6)" :  "columns parentId, name are not unique Unable to fetch row"
akonadi_imap_resource_0(17320)/kdepimlibs (kimap) RetrieveCollectionMetadataTask::doStart: ".Test2"
kmail2(17355) KMKernel::slotProgressItemCompletedOrCanceled: Last resource finished syncing, mail check done
kmail2(17355) KMKernel::instanceStatusChanged: A Resource started to synchronize, starting a mail check.
kmail2(17355) KMKernel::slotProgressItemCompletedOrCanceled: Last resource finished syncing, mail check done
kmail2(17355) AkonadiSender::doSendQueued: Sending queued message with custom transport: ""

That "Error during executing query" message is probably not related, since it appears periodically in the terminal where Akonadi and KMail were started, regardless of actions taken in KMail.
Comment 10 Thomas Pfeiffer 2013-04-19 20:35:26 UTC
Same here: The two top-level IMAP folders I created both cannot be seen, and akonadiserver.error contains
Error during executing query "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6)" :  "Duplicate entry '13-Stefan' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement" 
Error during executing query "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6)" :  "Duplicate entry '320-KDE eV' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"

"Stefan" and "KDE eV" are the names of the folders which are not shown.
Comment 11 S. Bryant 2013-11-27 12:57:51 UTC
This may be related to bug #266666.
Comment 12 Martin Steigerwald 2015-09-10 10:35:51 UTC
Hello. This this still happen with KDEPIM 4.14 and latest Akonadi 1.13 or even KDEPIM/Akonadi 15.08 if you can get it already. Thanks and greetings from KDE Randa Meetings, Martin
Comment 13 Andreas Hartmetz 2015-09-10 14:08:26 UTC
This is fixed in kdepim/kf5 at least - although I can't create top-level folders in my GMail account at all anymore (I seem to remember a commit to that effect, it was a deliberate change)... I can create subfolders of toplevel folders in KMail and that works fine.
Toplevel folders ("labels") created in the web interface do show up.