Bug 128463

Summary:	Kmail crashes (SEGV) upon startup
Product:	[Unmaintained] kmail	Reporter:	Rogier <rogier777>
Component:	general	Assignee:	kdepim bugs <pim-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	lordchaica
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Rogier 2006-06-01 22:23:20 UTC

Version:            (using KDE KDE 3.5.2)
Installed from:    Debian testing/unstable Packages
Compiler:          I'm using a debian binary kmail package. If it is of any help: current compiler on my system is (gcc -v): gcc version 4.0.4 20060507 (prerelease) (Debian 4.0.3-3) 
OS:                Linux

I just upgraded my debian testing system. Kmail now crashes on startup.
The previous debian kmail package version was probably kmail-4:3.4.3-1

Backtrace:
-----------------------------------------------------------------------
(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1249597760 (LWP 9721)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xb7bc0528 in KMFolderTree::slotFolderExpanded ()
   from /usr/lib/libkmailprivate.so
#7  0xb7bc7b1b in KMFolderTree::qt_invoke () from /usr/lib/libkmailprivate.so
#8  0xb72c954b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#9  0xb76725b8 in QListView::expanded () from /usr/lib/libqt-mt.so.3
#10 0xb73c4341 in QListViewItem::setOpen () from /usr/lib/libqt-mt.so.3
#11 0xb7bc41e4 in KMFolderTree::addDirectory ()
   from /usr/lib/libkmailprivate.so
#12 0xb7bc46ab in KMFolderTree::reload () from /usr/lib/libkmailprivate.so
#13 0xb7d82cda in KMMainWidget::readConfig () from /usr/lib/libkmailprivate.so
#14 0xb7d83728 in KMMainWidget::KMMainWidget ()
   from /usr/lib/libkmailprivate.so
#15 0xb7b6b399 in KMMainWin::KMMainWin () from /usr/lib/libkmailprivate.so
#16 0xb7ceb03f in KMKernel::mainWin () from /usr/lib/libkmailprivate.so
#17 0xb7ca3f89 in KMail::ImapAccountBase::makeConnection ()
   from /usr/lib/libkmailprivate.so
#18 0xb7ca763f in KMail::ImapAccountBase::readConfig ()
   from /usr/lib/libkmailprivate.so
#19 0xb7cab274 in KMAcctImap::readConfig () from /usr/lib/libkmailprivate.so
#20 0xb7c4ac44 in KMail::AccountManager::readConfig ()
   from /usr/lib/libkmailprivate.so
#21 0xb7cf212d in KMKernel::init () from /usr/lib/libkmailprivate.so
#22 0x0804a02e in ?? ()
#23 0xbfc218f8 in ?? ()
#24 0x00000000 in ?? ()
-----------------------------------------------------------------------
Stdout / stderr:
-----------------------------------------------------------------------
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x82bea98 ): KAccel object already contains an action name "delete"
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x82bea98 ): KAccel object already contains an action name "edit"
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x82bea98 ): KAccel object already contains an action name "display_message"
ERROR: Communication problem with kmail, it probably crashed.
KCrash: Application 'kmail' crashing...
-----------------------------------------------------------------------

Comment 1 Carsten Burghardt 2006-06-01 22:29:12 UTC

Do you have any imap accounts?

Comment 2 Rogier 2006-06-02 09:03:25 UTC

Yes.
a number of them.

Rogier.

Carsten Burghardt wrote:

[bugs.kde.org quoted mail]

Comment 3 Philip Rodrigues 2006-07-20 23:57:44 UTC

*** Bug 131112 has been marked as a duplicate of this bug. ***

Comment 4 Thomas Bettler 2006-08-17 17:45:28 UTC

I experienced a similar behaviour with kontact, but that was related to SPAM filters. Deleting them in the kmailrc solved it.

Comment 5 Tommi Tervo 2006-08-19 13:50:09 UTC


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