Bug 292679 - 3-4 instances of Local Folders, but just one agent
Summary: 3-4 instances of Local Folders, but just one agent
Status: RESOLVED WORKSFORME
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Maildir Resource (show other bugs)
Version: 4.8
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-28 11:33 UTC by Benjamin M
Modified: 2012-10-13 08:15 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Benjamin M 2012-01-28 11:33:50 UTC
Version:           4.8 (using KDE 4.8.0) 
OS:                Linux

Refer to this thread for all the details: http://forum.kde.org/viewtopic.php?f=215&t=98810&p=212098

In a nutshell, I have 4 nonidentical instances of Local Folders in Kmail now, they share the same core of emails, but only one of them has all my mail and it also is the only one that retained my tags. It is also the one that new messages get sorted into. 
However, one of the 4 (yesterday 3) instances has black text, the others, red. The "real" one has red text. I also notice that I cannot read older emails (i.e. from before the "split") from the "right" Local Folders, only newer ones. If I want to read any of those messages, I need to go to the instance in black.

It seems like that Akonadi is forcing me to run 2 local folders agents. Whenever I delete one, it goes down to 3 instances, but a new agent will be created soon, which takes me back to 4x Local Folders madness. 

Reproducible: Didn't try

Steps to Reproduce:
I have a postgresql backend. I updated to KDE 4.8, starting a new nepomuk database (I think). That's all I did. 

Actual Results:  
See above. 

Expected Results:  
A normal inbox. 

A screenshot can be found in the forum thread linked at the top of the page. The supporter there asked me to file this bug and said the problem might have to do with this line from .xsession-errors (full excerpt at the thread): 

"Cannot connect to agent instance with identifier 'akonadi_maildir_resource_14', error message: 'Could not get owner of name 'org.freedesktop.Akonadi.Resource.akonadi_maildir_resource_14': no such name'"

I have twice now removed a duplicate Local Folders agent, but a new one keeps coming up after a while. It seems like that is part of the problem. It seems to be impossible to remove an agent unless all the config files are there (cf. my first post in above linked thread). (On a side note, it also seems like my contact agents are going rampant. I shoudl't have more than 3, yet there's about 8 listed below.)

Compare my agentsrc and akonadiserverrc:
[Instances]
akonadi_maildispatcher_agent\AgentType=akonadi_maildispatcher_agent
akonadi_kabc_resource_0\AgentType=akonadi_kabc_resource
akonadi_pop3_resource_0\AgentType=akonadi_pop3_resource
akonadi_pop3_resource_1\AgentType=akonadi_pop3_resource
akonadi_pop3_resource_2\AgentType=akonadi_pop3_resource
akonadi_birthdays_resource\AgentType=akonadi_birthdays_resource
akonadi_contacts_resource_2\AgentType=akonadi_contacts_resource
akonadi_kcal_resource_4\AgentType=akonadi_kcal_resource
akonadi_ical_resource_11\AgentType=akonadi_ical_resource
akonadi_vcarddir_resource_0\AgentType=akonadi_vcarddir_resource
akonadi_nepomuk_feeder\AgentType=akonadi_nepomuk_feeder
akonadi_mailfilter_agent\AgentType=akonadi_mailfilter_agent
akonadi_maildir_resource_20\AgentType=akonadi_maildir_resource
akonadi_contacts_resource_6\AgentType=akonadi_contacts_resource
akonadi_ical_resource_12\AgentType=akonadi_ical_resource
akonadi_akonotes_resource_5\AgentType=akonadi_akonotes_resource
akonadi_contacts_resource_7\AgentType=akonadi_contacts_resource
akonadi_contacts_resource_8\AgentType=akonadi_contacts_resource
akonadi_contacts_resource_9\AgentType=akonadi_contacts_resource
akonadi_contacts_resource_10\AgentType=akonadi_contacts_resource
akonadi_contacts_resource_11\AgentType=akonadi_contacts_resource
akonadi_contacts_resource_12\AgentType=akonadi_contacts_resource
akonadi_ical_resource_13\AgentType=akonadi_ical_resource
akonadi_maildir_resource_21\AgentType=akonadi_maildir_resource
akonadi_akonotes_resource_6\AgentType=akonadi_akonotes_resource
akonadi_contacts_resource_13\AgentType=akonadi_contacts_resource
akonadi_ical_resource_14\AgentType=akonadi_ical_resource
akonadi_akonotes_resource_7\AgentType=akonadi_akonotes_resource
akonadi_contacts_resource_14\AgentType=akonadi_contacts_resource
akonadi_ical_resource_15\AgentType=akonadi_ical_resource
akonadi_akonotes_resource_8\AgentType=akonadi_akonotes_resource
akonadi_kabc_resource_1\AgentType=akonadi_kabc_resource
akonadi_ical_resource_16\AgentType=akonadi_ical_resource
akonadi_akonotes_resource_9\AgentType=akonadi_akonotes_resource
akonadi_vcard_resource_3\AgentType=akonadi_vcard_resource

--------
[%General]
Driver=QPSQL

[QPSQL]
StartServer=true
Name=akonadi
Host=/home/alvanx/.local/share/akonadi/socket-alvanx.ichthys
Options=
ServerPath=/usr/bin/pg_ctl
InitDbPath=/usr/bin/initdb

[QMYSQL]
StartServer=true
ServerPath=/usr/sbin/mysqld
Name=akonadi
Host=
User=
Password=
Options="UNIX_SOCKET=/home/alvanx/.local/share/akonadi/socket-alvanx.ichthys/mysql.socket"

[Debug]
Tracer=null
Comment 1 Christophe Marin 2012-01-29 01:21:44 UTC
How did you remove the extra ones ? 

With akonadiconsole ?
Comment 2 Benjamin M 2012-01-29 13:04:03 UTC
precisely. :-)
Comment 3 András Manţia 2012-02-11 13:57:27 UTC
I have a strange feeling this is some weird issue with postgres backend.
Comment 4 Benjamin M 2012-02-11 15:33:41 UTC
Most likely, I think. Unfortunately, I have always had more problems with mysql and sqlite, and postgresql had, previously to this bug, been very good to me. 
I worked around it with a new database. Still have the old stuff backed up though. Btw, this also fixed the duplicating of agents.
Comment 5 Christophe Marin 2012-02-11 20:53:42 UTC
Note: I've never seen this issue (and I use the postgres backend since months)
Comment 6 András Manţia 2012-10-13 08:15:03 UTC
I see you recreated the db and the problem is gone with that. Unfortunately I cannot reproduce this issue, and never heard about if from anybody else. So there must have been some corruption in the database, be it because of migration or because something else (like crashing agents at the wrong time). But this remains a mistrey.
I'll close the report, but feel free to reopen if you run into it again.