Without using akonadi of kmail or any of those applications but whith the digital clock as part of the default setup in the task bar the following behaviour is encountered: in file .kde4/share/config/akonadi-firstrunrc if find the line defaultaddressbook=akonadi_contacts_resource_113 and the respective files ~/.config/akonadi/agent_config_akonadi_contacts_resource_### and ~/.config/akonadi/agent_config_akonadi_contacts_resource_###_changes.dat with ### from 0 to 113 are created. But what makes this really worse is that for each file a process is started whth the command /usr/bin/akonadi_contacts_resource --identifier akonadi_contacts_resource_###. So, now, I have on my machines more than 100 processes of this type running. These processes are accompanied by /usr/bin/akonadi_control akonadiserver /usr/bin/akonadi_ical_resource --identifier akonadi_ical_resource_0 /usr/bin/akonadi_maildir_resource --identifier akonadi_maildir_resource_0 /usr/bin/akonadi_maildispatcher_agent --identifier akonadi_maildispatcher_agent /usr/bin/akonadi_nepomuk_contact_feeder --identifier akonadi_nepomuk_contact_feeder /usr/sbin/mysqld --defaults-file=~/.local/share/akonadi//mysql.conf --datadir=~/.local/share/akonadi/db_data/ --socket=~/.local/share/akonadi/socket-nahe/mysql.socket akonadictl status returns: -------- Akonadi Control: stopped Akonadi Server: stopped Akonadi Server Search Support: not available --------- Noticably the machines run a standard openSUSE 11.4 out of the box and no konfiguation whatsoever of kmail or any of the akonadi related applications. With a system, that has limited resources, this slows down overall performance considerably. All I found in the discussions was, that some people, who experience this and prefer to disable akonadi alltogether. This was not a problem on openSUSE 11.2 and on another system, which I have at home, where the akonadiserver is up and running, I found only a few of those contact resources. So I guess it could be a result of this 'firstrun'. What happends if the server, which is supposed to do the initialization, does not get propperly running? Or is it a leftover in the configuration dataset which has allready been fixed? Regards
Hi, is this problem still valid? I've seen this happening a few times long time ago, but I believe it is fixed now in KDE>=4.10/Akonadi>=1.10
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!