Bug 278667 - kmail crashes on start
Summary: kmail crashes on start
Status: RESOLVED FIXED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 4.7
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-28 06:44 UTC by Wolfgang Strehlow
Modified: 2016-09-24 20:51 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Wolfgang Strehlow 2011-07-28 06:44:07 UTC 
Version:           unspecified (using KDE 4.7.0) 
OS:                Linux

After installing KDE 4.7.0 with kontact4.7.0-287.1 (suse rpm) kontact crashes on startup.
Error message below

Reproducible: Always

Steps to Reproduce:
start kontact

Actual Results:  
Kontact doesnt start

Expected Results:  
kontact should start

kontact(10210)/libakonadi Akonadi::SpecialCollectionsRequestJobPrivate::resourceScanResult: Failed to request resource "akonadi_maildir_resource_2" : "Unbekannter Fehler. (Fehler beim Einholen der Ressourcen-Sammlung.)" 
kontact(10210)/libakonadi Akonadi::SpecialCollectionsRequestJob::slotResult: Failed SpecialCollectionsRequestJob::slotResult "Unbekannter Fehler. (Fehler beim Einholen der Ressourcen-Sammlung.)"
Comment 1 Laurent Montel 2011-08-09 14:07:21 UTC 
backtrace ?
Comment 2 Wolfgang Strehlow 2011-08-09 18:58:55 UTC 
Not yet.
I made a downgrade to 4.6 immediately because I need the system for the job.
I will do it these days on my notebook, same problem there.
For your information: If I uninstall kmail, kontact works.
Comment 3 Wolfgang Strehlow 2011-08-09 20:14:13 UTC 
I forgot:
How can I do a backtrace when I get the message that Kontact will be closed because of the error. 
Its not a crash where I get the option to do a bachtrace and send a report.
Would be nice if you could tell me what to do 
Thanks.
Comment 4 Denis Kurz 2016-09-24 20:43:53 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.