Bug 183824 - Fatal Error (SIGABRT) signal 6
Summary: Fatal Error (SIGABRT) signal 6
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-09 20:18 UTC by alex
Modified: 2009-03-19 00:41 UTC (History)
2 users (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 alex 2009-02-09 20:18:29 UTC
Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    I Don't Know

I just opened up KMail, and it asked me for my account passwords - once all done, KMail crashed with this:


Application: KMail (kmail), signal SIGABRT
0x00007f98218c2001 in nanosleep () from /lib/libc.so.6

Thread 1 (Thread 0x7f9826d80750 (LWP 2767)):
[KCrash Handler]
#5  0x00007f98218550c5 in raise () from /lib/libc.so.6
#6  0x00007f98218565e3 in abort () from /lib/libc.so.6
#7  0x00007f98234d40a5 in qt_message_output () from /usr/lib/libQtCore.so.4
#8  0x00007f98234d41c7 in qFatal () from /usr/lib/libQtCore.so.4
#9  0x00007f9825a95767 in KMail::ImapAccountBase::makeConnection () from /usr/lib/libkmailprivate.so.4
#10 0x00007f9825aa6cd8 in KMAcctImap::processNewMail () from /usr/lib/libkmailprivate.so.4
#11 0x00007f9825a2b247 in KMail::AccountManager::processNextCheck () from /usr/lib/libkmailprivate.so.4
#12 0x00007f9825a2bcf2 in KMail::AccountManager::singleCheckMail () from /usr/lib/libkmailprivate.so.4
#13 0x00007f9825a2c161 in KMail::AccountManager::checkMail () from /usr/lib/libkmailprivate.so.4
#14 0x00007f9825bfc0c4 in KMMainWidget::qt_metacall () from /usr/lib/libkmailprivate.so.4
#15 0x00007f98235bdd30 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0x00007f98235c461f in ?? () from /usr/lib/libQtCore.so.4
#17 0x00007f98235b9cf3 in QObject::event () from /usr/lib/libQtCore.so.4
#18 0x00007f98224b34ed in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#19 0x00007f98224b987a in QApplication::notify () from /usr/lib/libQtGui.so.4
#20 0x00007f98268b756b in KApplication::notify () from /usr/lib/libkdeui.so.5
#21 0x00007f98235ac401 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#22 0x00007f98235d3e86 in ?? () from /usr/lib/libQtCore.so.4
#23 0x00007f98235d096d in ?? () from /usr/lib/libQtCore.so.4
#24 0x00007f9819190aa2 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#25 0x00007f981919421d in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#26 0x00007f98191943db in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#27 0x00007f98235d08cf in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#28 0x00007f982253404f in ?? () from /usr/lib/libQtGui.so.4
#29 0x00007f98235aad72 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#30 0x00007f98235aaf05 in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#31 0x00007f98235ad065 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#32 0x00000000004030cb in _start ()
Comment 1 Dario Andres 2009-02-10 13:25:48 UTC
This is probably a duplicate of bug 168662.

If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? 
You need to install the debug symbols packages for KMail or KDEPIM
Thanks :)
Comment 2 alex 2009-02-10 14:17:25 UTC
Ah ok, wasn't aware of that. If I can reproduce it again, I'll do that. 

However, I *think* this bug is related to the KWallet bug where KMail forgets that it is using KWallet. As this crash I had would do it after KMail asked for passwords, though doing the 'fix' for the KWaller+KMail bug appears to have fixed this. 

I'll do some more playing around with it when I get home, and see if I can reproduce again
Comment 3 Christophe Marin 2009-03-09 11:08:55 UTC
No feedback for a month. We will assume the issue is now fixed for you and change this bug status.