Bug 269068 - Kmail crashes on start
Summary: Kmail crashes on start
Status: RESOLVED DUPLICATE of bug 170191
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: 1.13.5
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-21 18:09 UTC by Rick
Modified: 2011-04-24 14:07 UTC (History)
1 user (show)

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 Rick 2011-03-21 18:09:52 UTC
Application: kmail (1.13.5)
KDE Platform Version: 4.6.1 (4.6.1)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-28-generic x86_64
Distribution: Ubuntu 10.10

-- Information about the crash:
- What I was doing when the application crashed:
Trying to start kmail, I have recently upgraded from KDE 4.5.x to 4.6.1 and kmail hasn't worked since.

I am using Kubuntu Maverick Backports repo for the KDE 4.6.1 packages. Everything is updated to the latest version.

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#6  0x00007fb72281f43b in KMailICalIfaceImpl::readConfig (this=0x26a3c10) at ../../kmail/kmailicalifaceimpl.cpp:1785
#7  0x00007fb722702fbe in KMKernel::setupDBus (this=0x7fff1e676730) at ../../kmail/kmkernel.cpp:227
#8  0x00000000004031d8 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../kmail/main.cpp:141

Reported using DrKonqi
Comment 1 Rick 2011-03-24 00:36:39 UTC
Since this bug made it impossible to use kmail I have completely copied my .kde directory from another machine to fix it.

Removing ~/.kde/share/apps/kmail/ had no effect. And doing a "find ~/.kde/ -iname '*kmail*' -print0 | xargs -0 rm -rf" had no effect either.

I'm not sure what the cause was but I suspect Akonadi since I did get Kmail running after a while but when adding a new mail account it crashed with an akonadi cannot start error.
Comment 2 Christophe Marin 2011-04-24 14:07:07 UTC

*** This bug has been marked as a duplicate of bug 170191 ***