Bug 279848 - System freeze within 5 minutes after login
Summary: System freeze within 5 minutes after login
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-10 22:12 UTC by Mathias D
Modified: 2017-09-01 18:23 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 Mathias D 2011-08-10 22:12:18 UTC
Version:           unspecified (using KDE 4.7.0) 
OS:                Linux

I had a reproducable bug, witch cause, that system freeze within 5 minutes after login nearly complete. There was some akonadi processes running. When I killed them, system workes fine and normal. If I dont kill them, system freeze. I played around a little and found out, that, if I delete ~/.config/akonadi problem disapeare. I saved the config files witch was responsable for that error. BTW.: A half year ago, that error was the reason to switch away from kde on that machine. I hope that error was fixed, I switched back. It was not fixed, but now I found out that "workarround". Please let me know, if I can help or if the config files could be useful. I will send them to you. Thank you.

Reproducible: Always

Steps to Reproduce:
Use config files I saved. 

Actual Results:  
System freeze within 5 minutes after login on a dual core amd with 4 gb ram

Expected Results:  
system should work normally

OS: Linux (x86_64) release 3.0.0-rc4
Compiler: gcc
Comment 1 Denis Kurz 2016-09-24 20:31:47 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 2 Denis Kurz 2017-01-07 21:41:42 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.