Bug 332637

Summary:	kmail encounters fatal error at start
Product:	[Applications] kmail2	Reporter:	Kwanza.Pili
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED WORKSFORME
Severity:	grave	CC:	kdenis
Priority:	NOR
Version:	4.12.3
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Kwanza.Pili 2014-03-26 16:21:10 UTC

kmail fails at startup due to some communication problem with akonadi. I have reset/cleaned up all items related to akonadi without any success. I can add agents to akonadi without a problem, and akonadi claim that they are ready.. Here is a log of the errors kmail emits:
-----
kmail2(2878)/libakonadi: Unable to obtain agent type for default resource agent configuration  "/usr/share/kde4/apps/akonadi/firstrun/defaultaddressbook" 
kmail2(2878)/libakonadi: Unable to obtain agent type for default resource agent configuration  "/usr/share/kde4/apps/akonadi/firstrun/defaultcalendar" 
kmail2(2878)/libakonadi: Unable to obtain agent type for default resource agent configuration  "/usr/share/kde4/apps/akonadi/firstrun/defaultnotebook" 
kmail2(2878) KDirWatch::removeDir: doesn't know "/home/kwanza/.kde4/share/apps/messageviewer/themes/" 
kmail2(2878) KDirWatch::removeDir: doesn't know "/usr/share/kde4/apps/messageviewer/themes/" 
kmail2(2878)/libakonadi Akonadi::DefaultResourceJobPrivate::resourceCreateResult: "Unable to obtain agent type ''." 
kmail2(2878)/libakonadi Akonadi::SpecialCollectionsRequestJob::slotResult: Failed SpecialCollectionsRequestJob::slotResult "Cannot connect to the Akonadi service. (Unable to obtain agent type ''.)" 
kmail2(2878) MailCommon::Kernel::emergencyExit: "The Email program encountered a fatal error and will terminate now.
The error was:
Unable to obtain agent type ''." 
kmail2(2878)/libakonadi Akonadi::DefaultResourceJobPrivate::resourceCreateResult: "Unable to obtain agent type ''." 
kmail2(2878)/libakonadi Akonadi::SpecialCollectionsRequestJob::slotResult: Failed SpecialCollectionsRequestJob::slotResult "Cannot connect to the Akonadi service. (Unable to obtain agent type ''.)" 
kmail2(2878) MailCommon::Kernel::emergencyExit: "The Email program encountered a fatal error and will terminate now.
The error was:
Unable to obtain agent type ''."
kmail2(2878)/libakonadi Akonadi::SpecialCollectionsRequestJobPrivate::resourceScanResult: Failed to request resource "" : "Cannot connect to the Akonadi service. (Unable to obtain agent type ''.)" 
kmail2(2878)/libakonadi Akonadi::DefaultResourceJobPrivate::resourceCreateResult: "Unable to obtain agent type ''." 
kmail2(2878)/libakonadi Akonadi::SpecialCollectionsRequestJob::slotResult: Failed SpecialCollectionsRequestJob::slotResult "Cannot connect to the Akonadi service. (Unable to obtain agent type ''.)" 
kmail2(2878) MailCommon::Kernel::emergencyExit: "The Email program encountered a fatal error and will terminate now.
The error was:
Unable to obtain agent type ''." 
kmail2(2878)/libakonadi Akonadi::SpecialCollectionsRequestJobPrivate::resourceScanResult: Failed to request resource "" : "Cannot connect to the Akonadi service. (Unable to obtain agent type ''.)" 
kmail2(2878)/libakonadi Akonadi::DefaultResourceJobPrivate::resourceCreateResult: "Unable to obtain agent type ''." 
kmail2(2878)/libakonadi Akonadi::SpecialCollectionsRequestJob::slotResult: Failed SpecialCollectionsRequestJob::slotResult "Cannot connect to the Akonadi service. (Unable to obtain agent type ''.)" 
kmail2(2878) MailCommon::Kernel::emergencyExit: "The Email program encountered a fatal error and will terminate now.
The error was:
Unable to obtain agent type ''." 
kmail2(2878)/libakonadi Akonadi::SpecialCollectionsRequestJobPrivate::resourceScanResult: Failed to request resource "" : "Cannot connect to the Akonadi service. (Unable to obtain agent type ''.)" 
kmail2(2878)/libakonadi Akonadi::DefaultResourceJobPrivate::resourceCreateResult: "Unable to obtain agent type ''." 
kmail2(2878)/libakonadi Akonadi::SpecialCollectionsRequestJob::slotResult: Failed SpecialCollectionsRequestJob::slotResult "Cannot connect to the Akonadi service. (Unable to obtain agent type ''.)" 
kmail2(2878) MailCommon::Kernel::emergencyExit: "The Email program encountered a fatal error and will terminate now.
The error was:
Unable to obtain agent type ''." 
kmail2(2878)/libakonadi Akonadi::SpecialCollectionsRequestJobPrivate::resourceScanResult: Failed to request resource "" : "Cannot connect to the Akonadi service. (Unable to obtain agent type ''.)" 
kmail2(2878)/libakonadi Akonadi::DefaultResourceJobPrivate::resourceCreateResult: "Unable to obtain agent type ''." 
kmail2(2878)/libakonadi Akonadi::SpecialCollectionsRequestJob::slotResult: Failed SpecialCollectionsRequestJob::slotResult "Cannot connect to the Akonadi service. (Unable to obtain agent type ''.)" 
kmail2(2878) MailCommon::Kernel::emergencyExit: "The Email program encountered a fatal error and will terminate now.
The error was:
Unable to obtain agent type ''." 
kmail2(2878)/libakonadi Akonadi::SpecialCollectionsRequestJobPrivate::resourceScanResult: Failed to request resource "" : "Cannot connect to the Akonadi service. (Unable to obtain agent type ''.)" 
unnamed app(2876): Communication problem with  "kmail2" , it probably crashed. 
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" " 
----


Reproducible: Always

Steps to Reproduce:
1. Run kmail
2.
3.
Actual Results:  
Fatal error encountered. The program exits

Expected Results:  
Load kmail/kontact  showing emails or configuration options

I use the MySQL plugin for akonadi

Comment 1 Kwanza.Pili 2014-03-30 22:56:29 UTC

Not sure that kmail2 is worth fixing unless the fatal dependency on akonadi is removed. I suspect akonadi is the culprit - not sure if it has any benefits at all. So for those who need a quick resolution to this bug, I found the following "fix":
- I reverted to kdepim v3.5.10 - this provides kmail without any akonadi dependency
- Remove akonadi-runtime; it will also require that kdepim4 goes with associated  kmail, kalarm, etc.

Pity, kmail2 had such promise

Comment 2 Denis Kurz 2016-09-24 18:16:12 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.

Comment 3 Kwanza.Pili 2016-09-26 08:40:36 UTC

I can confirm that the bug does not occur in Frameworks5.

Comment 4 Denis Kurz 2016-09-26 17:51:12 UTC

Awesome, thanks for reporting back.