Bug 240695 - KMail Crash while startup with Akonadi error
Summary: KMail Crash while startup with Akonadi error
Status: RESOLVED DUPLICATE of bug 185395
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: 1.13.3
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 227913 238176 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-06-04 09:31 UTC by Martin L ü c h e m
Modified: 2010-08-09 00:29 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Log File Test Akonadi (10.42 KB, text/plain)
2010-06-04 09:31 UTC, Martin L ü c h e m 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Martin L ü c h e m 2010-06-04 09:31:35 UTC 
Created attachment 47661 [details]
Log File Test Akonadi

Version:           1.13.3 (using KDE 4.4.3) 
OS:                Linux

Every time I start KMail it will crash after showing Akonadi self test log. I will attach this.

Reproducible: Always

Steps to Reproduce:
1st try to start -> Akonadi error

2nd try to start -> KMail will start



OS: Linux (x86_64) release 2.6.32-3-amd64
Compiler: cc
Comment 1 Nicolas L. 2010-06-04 11:16:50 UTC 

*** This bug has been marked as a duplicate of bug 185395 ***
Comment 2 Martin L ü c h e m 2010-06-04 15:01:36 UTC 
Hi Nicolas,

sorry, but I cannot see what the solution is in the linked bug. Can you in this bug or in the other one describe a bit more detailed waht the solution is.

Thank you for your help!  Martin
Comment 3 Raúl 2010-06-07 12:01:17 UTC 
Martin:

The bug is fixed in the svn repository for akonadi 1.3 branch and trunk. In order to have it fixed I guess the easiest way would be waiting for a next point release (1.3.2) for akonadi, so it will flow through your distro and you will get it.

I don't know when this is planned though.

Regards,
Comment 4 Malte S. Stretz 2010-06-17 10:53:40 UTC 
*** Bug 227913 has been marked as a duplicate of this bug. ***
Comment 5 Kevin Krammer 2010-07-04 22:09:36 UTC 
This is actually a duplicate of bug 236538, which has been fixed and is released with 4.4.5
Comment 6 Björn Ruberg 2010-08-09 00:29:40 UTC 
*** Bug 238176 has been marked as a duplicate of this bug. ***