Bug 254928 - akonadi eats resources on login to desktop, system unresponsive
Summary: akonadi eats resources on login to desktop, system unresponsive
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 1.4.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-22 08:38 UTC by gajdos.mirek
Modified: 2017-01-07 21:46 UTC (History)
2 users (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 gajdos.mirek 2010-10-22 08:38:24 UTC
Version:           1.4.0 (using KDE 4.5.1) 
OS:                Linux

After login to desktop, when akonadi starts, it begins to read / write to disk and cpu is used at 100%, I cant do anything, screen refreshes once every 20 seconds or so; i waited several minutes, but nothing changed.

Reproducible: Always

Steps to Reproduce:
Turn on computer, login, wait for akonadi to start.

Actual Results:  
Unusable system.

Expected Results:  
After some workload at start It should stop using harddrive and cpu in that crazy manner.

uname -a
Linux mirek-Latitude-E6410 2.6.35-22-generic #35-Ubuntu SMP Sat Oct 16 20:45:36 UTC 2010 x86_64 GNU/Linux

kubuntu 10.10


Btw, sorry for my english :D
Comment 1 Guilherme Fortunato 2011-04-30 22:51:31 UTC
I can confirm this. Several akonadi_** apps are spawned and, even if you kill them, they reappear. I "fixed" this by removing all the apps from the PATH and selectively copying back the ones needed by kmail to start. Out of 30 akonadi_???, only 7 were needed and kmail does not even complain about mysql/akonadi errors anymore.
Comment 2 Denis Kurz 2016-09-24 20:39:34 UTC
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 3 Denis Kurz 2017-01-07 21:46:11 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.