| Summary: | kmail crash at kde startup | ||
|---|---|---|---|
| Product: | [Unmaintained] kmail | Reporter: | Matthieu Michaud <matthieu> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | alex.merry, z_mikowski |
| Priority: | NOR | ||
| Version: | 1.10.1 | ||
| Target Milestone: | --- | ||
| Platform: | FreeBSD Ports | ||
| OS: | All | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Matthieu Michaud
2008-09-13 21:45:43 UTC
*** Bug 173775 has been marked as a duplicate of this bug. *** I get this on Linux as well. It only happens when KMail is started at login as part of the session, not when I manually start KMail.
I changed the OS to All, since it occurs on at least two and there doesn't seem to be a better option in the list.
Application: KMail (kmail), signal SIGABRT
Thread 1 (Thread 0xb3e37700 (LWP 5933)):
[KCrash Handler]
#6 0xb7f1d424 in __kernel_vsyscall ()
#7 0xb4a4a720 in raise () from /lib/libc.so.6
#8 0xb4a4c058 in abort () from /lib/libc.so.6
#9 0xb56979fb in qt_message_output (msgType=QtFatalMsg, buf=0xbfd37330 "ASSERT: \"!isEmpty()\" in file /home/kde-devel/src/qt-copy/include/QtCore/../../src/corelib/tools/qlist.h, line 252")
at global/qglobal.cpp:2108
#10 0xb5697a5f in qFatal (msg=0xb57e3c98 "ASSERT: \"%s\" in file %s, line %d") at global/qglobal.cpp:2309
#11 0xb5697e81 in qt_assert (assertion=0xb78325cb "!isEmpty()", file=0xb7832580 "/home/kde-devel/src/qt-copy/include/QtCore/../../src/corelib/tools/qlist.h", line=252) at global/qglobal.cpp:1878
#12 0xb7432051 in QList<KMainWindow*>::first (this=0xbfd393e0) at /home/kde-devel/src/qt-copy/include/QtCore/../../src/corelib/tools/qlist.h:252
#13 0xb7501fe0 in KMKernel::mainWin (this=0xbfd3a06c) at /home/kde-devel/src/KDE/kdepim/kmail/kmkernel.cpp:2068
#14 0xb7492c1c in KMail::ImapAccountBase::makeConnection (this=0x9735ad0) at /home/kde-devel/src/KDE/kdepim/kmail/imapaccountbase.cpp:317
#15 0xb749b9d6 in KMAcctImap::makeConnection (this=0x9735ad0) at /home/kde-devel/src/KDE/kdepim/kmail/kmacctimap.cpp:562
#16 0xb749ce6e in KMAcctImap::processNewMail (this=0x9735ad0, interactive=false) at /home/kde-devel/src/KDE/kdepim/kmail/kmacctimap.cpp:278
#17 0xb741f6f9 in KMail::AccountManager::processNextCheck (this=0x9735980, _newMail=false) at /home/kde-devel/src/KDE/kdepim/kmail/accountmanager.cpp:221
#18 0xb741f8db in KMail::AccountManager::singleCheckMail (this=0x9735980, account=0x9735ad0, interactive=false) at /home/kde-devel/src/KDE/kdepim/kmail/accountmanager.cpp:148
#19 0xb7387ed2 in KMAccount::mailCheck (this=0x9735ad0) at /home/kde-devel/src/KDE/kdepim/kmail/kmaccount.cpp:445
#20 0xb738ae53 in KMAccount::qt_metacall (this=0x9735ad0, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfd39844) at /home/kde-devel/build/KDE/kdepim/kmail/kmaccount.moc:144
#21 0xb74859aa in KMail::NetworkAccount::qt_metacall (this=0x9735ad0, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfd39844) at /home/kde-devel/build/KDE/kdepim/kmail/networkaccount.moc:57
#22 0xb7494664 in KMail::ImapAccountBase::qt_metacall (this=0x9735ad0, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfd39844) at /home/kde-devel/build/KDE/kdepim/kmail/imapaccountbase.moc:112
#23 0xb749cd08 in KMAcctImap::qt_metacall (this=0x9735ad0, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfd39844) at /home/kde-devel/build/KDE/kdepim/kmail/kmacctimap.moc:76
#24 0xb57a513d in QMetaObject::activate (sender=0x9afbb20, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3034
#25 0xb57a55cb in QMetaObject::activate (sender=0x9afbb20, m=0xb583ca64, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3107
#26 0xb57e2ce5 in QTimer::timeout (this=0x9afbb20) at .moc/debug-shared/moc_qtimer.cpp:126
#27 0xb57af294 in QTimer::timerEvent (this=0x9afbb20, e=0xbfd39df4) at kernel/qtimer.cpp:263
#28 0xb57a3432 in QObject::event (this=0x9afbb20, e=0xbfd39df4) at kernel/qobject.cpp:1126
#29 0xb4e7a8a1 in QApplicationPrivate::notify_helper (this=0x96832b8, receiver=0x9afbb20, e=0xbfd39df4) at kernel/qapplication.cpp:3809
#30 0xb4e7abb6 in QApplication::notify (this=0xbfd3a118, receiver=0x9afbb20, e=0xbfd39df4) at kernel/qapplication.cpp:3399
#31 0xb7d6dc0b in KApplication::notify (this=0xbfd3a118, receiver=0x9afbb20, event=0xbfd39df4) at /home/kde-devel/src/KDE/kdelibs/kdeui/kernel/kapplication.cpp:307
#32 0xb5790a6f in QCoreApplication::notifyInternal (this=0xbfd3a118, receiver=0x9afbb20, event=0xbfd39df4) at kernel/qcoreapplication.cpp:589
#33 0xb6f8614f in QCoreApplication::sendEvent (receiver=0x9afbb20, event=0xbfd39df4) at ../../../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#34 0xb57c1a5b in QTimerInfoList::activateTimers (this=0x9685eb4) at kernel/qeventdispatcher_unix.cpp:563
#35 0xb57bf408 in timerSourceDispatch (source=0x9685e80) at kernel/qeventdispatcher_glib.cpp:166
#36 0xb46572c1 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#37 0xb465a953 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#38 0xb465ab11 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#39 0xb57be73a in QEventDispatcherGlib::processEvents (this=0x9660888, flags={i = -1076650120}) at kernel/qeventdispatcher_glib.cpp:325
#40 0xb4f1f6f4 in QGuiEventDispatcherGlib::processEvents (this=0x9660888, flags={i = -1076650072}) at kernel/qguieventdispatcher_glib.cpp:204
#41 0xb578da90 in QEventLoop::processEvents (this=0xbfd3a020, flags={i = -1076650012}) at kernel/qeventloop.cpp:149
#42 0xb578dccd in QEventLoop::exec (this=0xbfd3a020, flags={i = -1076649944}) at kernel/qeventloop.cpp:196
#43 0xb579126b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:851
#44 0xb4e7a5ba in QApplication::exec () at kernel/qapplication.cpp:3337
#45 0x0804b6e9 in main (argc=3, argv=0xbfd3a1f4) at /home/kde-devel/src/KDE/kdepim/kmail/main.cpp:146
Oh, and this has only happened to me for about the last month using KDE trunk. And it happens absolutely consistently, every time I log in, except one time when the Akonadi migration tool ran. That time, KMail started fine. $ uname -a Linux mmikowski-desktop 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux After recent kdepim libs update for Kubuntu 8.10 (v4.1.80 - 4.2 beta 1) Kmail Always crashes -- on startup, when started from terminal, when started from krunner, when run in kontact The sad thing, is it seemed quite solid yesterday. === Terminal Output === mmikowski@mmikowski-desktop:~$ kmail mmikowski@mmikowski-desktop:~$ kmail(12691) Sonnet::Loader::loadPlugin: Successfully loaded plugin: "kspell_hspell.desktop" kmail(12691) Sonnet::Loader::loadPlugin: Successfully loaded plugin: "kspell_enchant.desktop" kmail(12691) <unnamed>::UrlHandler::UrlHandler: UrlHandler() (iCalendar) icalerror.c:104: BADARG: Bad argument to function kmail: icalerror.c:106: icalerror_set_errno: Assertion `0' failed. *** KMail got signal 6 (Crashing) KCrash: Application 'kmail' crashing... sock_file=/home/mmikowski/.kde/socket-mmikowski-desktop/kdeinit4__0 === From Crash Handler === Application: KMail (kmail), signal SIGABRT Thread 1 (Thread 0xb3f0f6c0 (LWP 12450)): [KCrash Handler] #6 0xb800c430 in __kernel_vsyscall () #7 0xb4a25880 in raise () from /lib/tls/i686/cmov/libc.so.6 #8 0xb4a27248 in abort () from /lib/tls/i686/cmov/libc.so.6 #9 0xb4a1e72e in __assert_fail () from /lib/tls/i686/cmov/libc.so.6 #10 0xb6d6f18c in icalerror_set_errno () from /usr/lib/libical.so.0 #11 0xb6d6a66e in icalcomponent_get_first_component () from /usr/lib/libical.so.0 #12 0xb6d6a6a7 in icalcomponent_get_first_real_component () from /usr/lib/libical.so.0 #13 0xb6d375f7 in icalclassify_find_attendee () from /usr/lib/libicalss.so.0 #14 0xb6d3783e in icalclassify_reply_accept () from /usr/lib/libicalss.so.0 #15 0xb6d371ec in icalclassify () from /usr/lib/libicalss.so.0 #16 0xb6cb24bd in KCal::ICalFormat::parseScheduleMessage () from /usr/lib/libkcal.so.4 #17 0xb6cc64ad in ?? () from /usr/lib/libkcal.so.4 #18 0xb6cc7be7 in KCal::IncidenceFormatter::formatICalInvitationNoHtml () from /usr/lib/libkcal.so.4 #19 0xb0bbc65c in ?? () from /usr/lib/kde4/kmail_bodypartformatter_text_calendar.so #20 0xb75b5a6f in ?? () from /usr/lib/libkmailprivate.so.4 #21 0xb75b6747 in ?? () from /usr/lib/libkmailprivate.so.4 #22 0xb75b6968 in ?? () from /usr/lib/libkmailprivate.so.4 #23 0xb75c36cb in ?? () from /usr/lib/libkmailprivate.so.4 #24 0xb75b5e80 in ?? () from /usr/lib/libkmailprivate.so.4 #25 0xb740b42f in ?? () from /usr/lib/libkmailprivate.so.4 #26 0xb73f8080 in ?? () from /usr/lib/libkmailprivate.so.4 #27 0xb73f82a0 in ?? () from /usr/lib/libkmailprivate.so.4 #28 0xb7407510 in ?? () from /usr/lib/libkmailprivate.so.4 #29 0xb4e3fa60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #30 0xb4e407e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #31 0xb4e7a7a7 in QTimer::timeout () from /usr/lib/libQtCore.so.4 #32 0xb4e4640e in QTimer::timerEvent () from /usr/lib/libQtCore.so.4 #33 0xb4e3a53f in QObject::event () from /usr/lib/libQtCore.so.4 #34 0xb50ff8ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #35 0xb510772e in QApplication::notify () from /usr/lib/libQtGui.so.4 #36 0xb7e1ec6d in KApplication::notify () from /usr/lib/libkdeui.so.5 #37 0xb4e2ae61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #38 0xb4e58d81 in ?? () from /usr/lib/libQtCore.so.4 #39 0xb4e55520 in ?? () from /usr/lib/libQtCore.so.4 #40 0xb43216f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #41 0xb4324da3 in ?? () from /usr/lib/libglib-2.0.so.0 #42 0xb4324f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #43 0xb4e55478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #44 0xb5199ea5 in ?? () from /usr/lib/libQtGui.so.4 #45 0xb4e2952a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #46 0xb4e296ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #47 0xb4e2bda5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #48 0xb50ff767 in QApplication::exec () from /usr/lib/libQtGui.so.4 #49 0x0804a970 in _start () Michael Mikowski: yours is a different bug - the crash is in a different place and so almost certainly for a different reason, and fixing one won't fix the other. It would probably be more helpful if you filed a separate bug so they could be dealt with separately. My trouble appears to be configuration related. I cleared out all KDE and Akonadi configs and started fresh with 4.2 Beta 1. Now Kmail (and Kontact) launch and stay up, at least for a while :) (hey, it's Beta). If it remains a problem, I will file a separate issue and make sure it goes against the correct kmail version, per comment 5 (thanks Alex). This is the same crash as 173640, and is fixed by the same commit. *** This bug has been marked as a duplicate of bug 173640 *** |