Bug 173775 - ASSERT in KMKernel::mainWin when starting as part of restored session
Summary: ASSERT in KMKernel::mainWin when starting as part of restored session
Status: RESOLVED DUPLICATE of bug 171002
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-28 18:30 UTC by Alex Merry
Modified: 2009-03-19 00:34 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Merry 2008-10-28 18:30:47 UTC
Version:           r876673 (using Devel)
Compiler:          gcc version 4.3.2 
OS:                Linux
Installed from:    Compiled sources

When KMail starts up as part of a restored session at log in (and not when started from Kickoff, say), it asserts with the following backtrace:

#13 0xb6881290 in KMKernel::mainWin (this=0xbfde866c) at /home/kde-devel/src/KDE/kdepim/kmail/kmkernel.cpp:2070
#14 0xb6812068 in KMail::ImapAccountBase::makeConnection (this=0x8f0a7e8) at /home/kde-devel/src/KDE/kdepim/kmail/imapaccountbase.cpp:317
#15 0xb681ae42 in KMAcctImap::makeConnection (this=0x8f0a7e8) at /home/kde-devel/src/KDE/kdepim/kmail/kmacctimap.cpp:563
#16 0xb681c2e2 in KMAcctImap::processNewMail (this=0x8f0a7e8, interactive=false) at /home/kde-devel/src/KDE/kdepim/kmail/kmacctimap.cpp:279
#17 0xb679f231 in KMail::AccountManager::processNextCheck (this=0x8f220c0, _newMail=false) at /home/kde-devel/src/KDE/kdepim/kmail/accountmanager.cpp:221
#18 0xb679f413 in KMail::AccountManager::singleCheckMail (this=0x8f220c0, account=0x8f0a7e8, interactive=false) at /home/kde-devel/src/KDE/kdepim/kmail/accountmanager.cpp:148
#19 0xb66e0cf2 in KMAccount::mailCheck (this=0x8f0a7e8) at /home/kde-devel/src/KDE/kdepim/kmail/kmaccount.cpp:445
#20 0xb66e3c73 in KMAccount::qt_metacall (this=0x8f0a7e8, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfde7e44) at /home/kde-devel/build/KDE/kdepim/kmail/kmaccount.moc:144
#21 0xb680481e in KMail::NetworkAccount::qt_metacall (this=0x8f0a7e8, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfde7e44) at /home/kde-devel/build/KDE/kdepim/kmail/networkaccount.moc:57
#22 0xb6813ab0 in KMail::ImapAccountBase::qt_metacall (this=0x8f0a7e8, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfde7e44) at /home/kde-devel/build/KDE/kdepim/kmail/imapaccountbase.moc:112
#23 0xb681c17c in KMAcctImap::qt_metacall (this=0x8f0a7e8, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfde7e44) at /home/kde-devel/build/KDE/kdepim/kmail/kmacctimap.moc:76
#24 0xb7eea13d in QMetaObject::activate (sender=0x9268988, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3034
#25 0xb7eea5cb in QMetaObject::activate (sender=0x9268988, m=0xb7f81a64, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3107
#26 0xb7f27ce5 in QTimer::timeout (this=0x9268988) at .moc/debug-shared/moc_qtimer.cpp:126
#27 0xb7ef4294 in QTimer::timerEvent (this=0x9268988, e=0xbfde83f4) at kernel/qtimer.cpp:263
#28 0xb7ee8432 in QObject::event (this=0x9268988, e=0xbfde83f4) at kernel/qobject.cpp:1126
#29 0xb72f88a1 in QApplicationPrivate::notify_helper (this=0x8e55ed0, receiver=0x9268988, e=0xbfde83f4) at kernel/qapplication.cpp:3809
#30 0xb72f8bb6 in QApplication::notify (this=0xbfde8718, receiver=0x9268988, e=0xbfde83f4) at kernel/qapplication.cpp:3399
#31 0xb6fa1eb7 in KApplication::notify (this=0xbfde8718, receiver=0x9268988, event=0xbfde83f4) at /home/kde-devel/src/KDE/kdelibs/kdeui/kernel/kapplication.cpp:307
#32 0xb7ed5a6f in QCoreApplication::notifyInternal (this=0xbfde8718, receiver=0x9268988, event=0xbfde83f4) at kernel/qcoreapplication.cpp:589
#33 0xb7ed95f1 in QCoreApplication::sendEvent (receiver=0x9268988, event=0xbfde83f4) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#34 0xb7f06a5b in QTimerInfoList::activateTimers (this=0x8e58adc) at kernel/qeventdispatcher_unix.cpp:563
#35 0xb7f04408 in timerSourceDispatch (source=0x8e58aa8) at kernel/qeventdispatcher_glib.cpp:166
#36 0xb46fa2c1 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#37 0xb46fd953 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#38 0xb46fdb11 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#39 0xb7f0373a in QEventDispatcherGlib::processEvents (this=0x8e336b0, flags={i = -1075935880}) at kernel/qeventdispatcher_glib.cpp:325
#40 0xb739d6f4 in QGuiEventDispatcherGlib::processEvents (this=0x8e336b0, flags={i = -1075935832}) at kernel/qguieventdispatcher_glib.cpp:204
#41 0xb7ed2a90 in QEventLoop::processEvents (this=0xbfde8620, flags={i = -1075935772}) at kernel/qeventloop.cpp:149
#42 0xb7ed2ccd in QEventLoop::exec (this=0xbfde8620, flags={i = -1075935704}) at kernel/qeventloop.cpp:196
#43 0xb7ed626b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:851
#44 0xb72f85ba in QApplication::exec () at kernel/qapplication.cpp:3337
#45 0x0804b809 in main (argc=3, argv=0xbfde87f4) at /home/kde-devel/src/KDE/kdepim/kmail/main.cpp:146



This happens every time I log in when I had KMail running at logout.  Something appears to be trying to access the first KMainWindow before any have been created.

It happens when it tries to ask for a password, it seems.  Something that may be related is that for one (out of three) of my IMAP accounts, I get asked for the password every time I start KMail despite telling KMail to remember the password.  The other two accounts remember the password without a problem.
Comment 1 Christophe Marin 2008-10-28 18:43:51 UTC

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