Bug 224552 - HRID MODIFY/LSUB/... after CREATE failed
Summary: HRID MODIFY/LSUB/... after CREATE failed
Status: RESOLVED FIXED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Kevin Ottens
URL:
Keywords: akonadi-ports-regression
Depends on:
Blocks: 223438
  Show dependency treegraph
 
Reported: 2010-01-28 01:01 UTC by Dennis Schridde
Modified: 2012-03-16 11:52 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dennis Schridde 2010-01-28 01:01:05 UTC
Version:           4.4_rc2 / 4.3.95 (using Devel)
Compiler:          gcc 4.4.2 Gentoo 4.4.2 p1.0
OS:                Linux
Installed from:    Compiled sources

This is what the debugger says when I do a sync-all on the imap resource:
68 CREATE "" 141 (MIMETYPE (message/rfc822 inode/directory) REMOTEID "/" CACHEPOLICY (INHERIT true))
68 NO Invalid collection name
69 ROLLBACK
69 OK Rollback completed
70 HRID LSUB ((-152 "/INBOX") (-153 "imap://.../") (0 "")) 0 (RESOURCE akonadi_imap_resource_1) ()
70 NO Hierarchical RID does not specify a unique collection

Assuming that CREATE "" creates the root directory of this resource, subscribing to any folders in the failed-to-be-created directory must fail for obvious reasons.
Comment 1 Dennis Schridde 2010-03-27 12:40:27 UTC
Now on Kubuntu 10.04_beta1 / KDE 4.4.1 I get a similar issue when trying to
synchronise the akonadi_imap_resource (after fixing up the database creation
manually, see launchpad-bug #448705):
 [/usr/bin/akonadi_imap_resource] akonadi_imap_resource_0(9320)
ImapResource::onIdleCollectionFetchDone: CollectionFetch for mail box "INBOX"
failed. error= 103 , errorString= "Unknown error. (Hierarchical RID does not
specify a unique collection)"

( https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/448705 )
Comment 3 Dennis Schridde 2010-03-27 12:46:40 UTC
akonadi-server 1.3.1-0ubuntu1
Comment 4 Dennis Schridde 2010-03-27 12:54:35 UTC
Log created via akonadiconsole on Kubuntu 10.04_beta1 / akonadi-server 1.3.1-0ubuntu1:

0 LOGIN "akonadi_imap_resource_0" 
0 OK User logged in 
1 RESSELECT "akonadi_imap_resource_0" 
1 OK akonadi_imap_resource_0 selected 
2 HRID LSUB ((-4 "/INBOX") (-5 "imap://$USER@$HOST/") (0 "")) 0 (RESOURCE akonadi_imap_resource_0) () 
2 NO Hierarchical RID does not specify a unique collection 
3 BEGIN 
3 OK Begin completed 
4 LSUB 0 INF (RESOURCE akonadi_imap_resource_0) (ANCESTORS 1) 
4 OK List completed 
5 CREATE "$HOST/$USER" 0 (MIMETYPE (inode/directory) REMOTEID "imap://$USER@$HOST/" AccessRights "" noselect "1" CACHEPOLICY (INHERIT false INTERVAL 5 CACHETIMEOUT 60 SYNCONDEMAND true LOCALPARTS (ENVELOPE HEAD))) 
* 12 0 (NAME "$HOST/$USER" MIMETYPE (inode/directory) REMOTEID "imap://$USER@$HOST/" RESOURCE "akonadi_imap_resource_0" CACHEPOLICY (INHERIT false INTERVAL 5 CACHETIMEOUT 60 SYNCONDEMAND true LOCALPARTS (ENVELOPE HEAD)) AccessRights "" noselect "1") 
5 OK CREATE completed 
6 CREATE "" 12 (MIMETYPE (message/rfc822 inode/directory) REMOTEID "/" CACHEPOLICY (INHERIT true)) 
6 NO Invalid collection name 
7 ROLLBACK 
7 OK Rollback completed 
8 HRID LSUB ((-14 "/INBOX") (-15 "imap://$USER@$HOST/") (0 "")) 0 (RESOURCE akonadi_imap_resource_0) () 
8 NO Hierarchical RID does not specify a unique collection 
9 HRID MODIFY ((-13 "/INBOX") (-8 "imap://$USER@$HOST/") (0 "")) MIMETYPE (message/rfc822 inode/directory) NAME "INBOX" REMOTEID "/INBOX" ENTITYDISPLAY "(\"Posteingang\" \"mail-folder-inbox\" \"\" ())" collectionannotations "/vendor/kolab/folder-type mail" 
9 NO Hierarchical RID does not specify a unique collection 


The general-log in akonadiconsole also logs:
AgentBase(akonadi_imap_resource_0): Unknown error. (Invalid collection name)
Comment 5 Stefan Vater 2012-02-21 18:27:17 UTC
Hi,

there is a patch for a similar, if not the same, problem in bug 258342. Please check if that solves your problem and report it here!

Stefan
Comment 6 Dennis Schridde 2012-02-21 20:03:38 UTC
I have not experienced the issue in a while. But then I have neither looked at the inner workings of Akonadi in a while either. It appears to be more or less working in KDE 4.8.0 - there are several bugs and error messages, but they do not seem to be much of a hindrance. Suggesting RESOLVED/FIXED if you are confident about the patch you mentioned, or CLOSED/WORKSFORME otherwise.
Comment 7 Kevin Ottens 2012-03-16 11:52:19 UTC
Marking as fixed.