Bug 300276 - cannot boot computer --constant akonadi-mail-handler crashes, one after t6he other
Summary: cannot boot computer --constant akonadi-mail-handler crashes, one after t6he ...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-18 19:41 UTC by Matt Clark
Modified: 2017-01-07 22:04 UTC (History)
0 users

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 Matt Clark 2012-05-18 19:41:57 UTC
The crashes began when I installed suse 11.4.  When executing ANY program akonadi** would crash, occasionally, at first, then (with upgrades to 11.4) 2, then 4,5,6 times interfering with execution of the program, sometimes hanging up the computer.  As of yesterday it won't allow kde desktop to boot at all, and will report akonadi** crashed again over and over as many times as I will dismiss akanodi**.  I am only up now because I chose to report the bug, and the program called up firefox.   Akanodi** is not a program, it is a hidden virus.  I cannot live with this mess and am going to have to do something different soon.   Other than firefox, nothing else will execute.

Reproducible: Always

Steps to Reproduce:
1.Attempt to boot computer (hard or soft)
2.
3.
Actual Results:  
See above description

Expected Results:  
KDE used to boot and produce my desktop.
Comment 1 Denis Kurz 2016-09-24 20:45:41 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 22:04:41 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.