Bug 227527

Summary: Kmail Authorisation Dialogue Crash
Product: [Unmaintained] kmail Reporter: Paul Crook <paul_crook>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Paul Crook 2010-02-18 15:38:46 UTC
Application that crashed: kmail
Version of the application: 1.12.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-15-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
Updated password on my IMAP account.  Think I succesfully updated kmail password but next time logged in it presented Authorisation Dialogue and what ever I do (correct password, incorrect password, cancel) kmail segfaults with signal 11 and I cannot read my mail.

This is repeatable everytime I try to open kmail.  Rebooting doesn't solve anything.  Problem persitant for at least one week.

using (K)Ubuntu 9.10

I can see many similar reports on the kmail system which might be related bug 225086 for example and possible several other bugs that have been marked duplicates of 184324 but no action.  Some help would be appreciated.

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[Current thread is 1 (Thread 0xb76e0aa0 (LWP 3124))]

Thread 2 (Thread 0xb0eddb70 (LWP 3130)):
#0  0x00c1b422 in __kernel_vsyscall ()
#1  0x00e2ec96 in poll () from /lib/tls/i686/cmov/libc.so.6
#2  0x0479254b in IA__g_poll (fds=0xa868568, nfds=1, timeout=-1) at /build/buildd/glib2.0-2.22.3/glib/gpoll.c:127
#3  0x0478556b in g_main_context_poll (context=0xa8681c0, block=<value optimized out>, dispatch=1, self=0xa781040) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2904
#4  g_main_context_iterate (context=0xa8681c0, block=<value optimized out>, dispatch=1, self=0xa781040) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2586
#5  0x04785863 in IA__g_main_context_iteration (context=0xa8681c0, may_block=1) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2654
#6  0x005db067 in QEventDispatcherGlib::processEvents (this=0x9ffc840, flags=...) at kernel/qeventdispatcher_glib.cpp:329
#7  0x005aec79 in QEventLoop::processEvents (this=0xb0edd244, flags=) at kernel/qeventloop.cpp:149
#8  0x005af0ca in QEventLoop::exec (this=0xb0edd244, flags=...) at kernel/qeventloop.cpp:201
#9  0x004bcb73 in QThread::exec (this=0xa792ae0) at thread/qthread.cpp:487
#10 0x005916ab in QInotifyFileSystemWatcherEngine::run (this=0xa792ae0) at io/qfilesystemwatcher_inotify.cpp:214
#11 0x004bfe32 in QThreadPrivate::start (arg=0xa792ae0) at thread/qthread_unix.cpp:188
#12 0x0376580e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#13 0x00e3c8de in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb76e0aa0 (LWP 3124)):
[KCrash Handler]
#6  QTreeWidgetPrivate::model (this=0xa84c460, item=0xa72e690, expand=false) at ../../include/QtGui/private/../../../src/gui/itemviews/qtreewidget_p.h:223
#7  QTreeWidget::setItemExpanded (this=0xa84c460, item=0xa72e690, expand=false) at itemviews/qtreewidget.cpp:3119
#8  0x0100c74c in QTreeWidgetItem::setExpanded (this=0xa14a3c0) at /usr/include/qt4/QtGui/qtreewidget.h:409
#9  KMail::FolderView::restoreItemStates (this=0xa14a3c0) at ../../kmail/folderview.cpp:388
#10 0x0101352d in KMail::FolderView::reload (this=0xa14a3c0, openFoldersForUpdate=false) at ../../kmail/folderview.cpp:665
#11 0x0127faf8 in KMMainWidget::readConfig (this=0x9da2990) at ../../kmail/kmmainwidget.cpp:601
#12 0x01293342 in KMMainWidget (this=0x9da2990, parent=0x9af62a8, aGUIClient=0x9af62dc, actionCollection=0x9eb30a0, config=0x9afb900) at ../../kmail/kmmainwidget.cpp:233
#13 0x00f9133e in KMMainWin (this=0x9af62a8, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at ../../kmail/kmmainwin.cpp:41
#14 0x011a56e1 in KMKernel::openReader (this=0xbfe75aec, onlyCheck=false) at ../../kmail/kmkernel.cpp:408
#15 0x011a691b in KMKernel::action (this=0xbfe75aec, mailto=false, check=<value optimized out>, to=..., cc=..., bcc=..., subj=..., body=..., messageFile=..., attachURLs=..., customHeaders=...)
    at ../../kmail/kmkernel.cpp:1892
#16 0x011a7f8b in KMKernel::handleCommandLine (this=0xbfe75aec, noArgsOpensReader=true) at ../../kmail/kmkernel.cpp:354
#17 0x0804ae5d in KMailApplication::newInstance (this=0xbfe75bb0) at ../../kmail/main.cpp:84
#18 0x0099b380 in KUniqueApplicationAdaptor::newInstance (this=0x9c8c890, asn_id=..., args=...) at ../../kdeui/kernel/kuniqueapplication.cpp:459
#19 0x0099ba92 in KUniqueApplicationAdaptor::qt_metacall (this=0x9c8c890, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfe7513c) at ./kuniqueapplication_p.moc:75
#20 0x00b747b4 in QDBusConnectionPrivate::deliverCall (this=0x9af8ec0, object=0x9c8c890, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:891
#21 0x00b7595d in QDBusConnectionPrivate::activateCall (this=0x9af8ec0, object=0x9c8c890, flags=337, msg=...) at qdbusintegrator.cpp:796
#22 0x00b76234 in QDBusConnectionPrivate::activateObject (this=0x9af8ec0, node=..., msg=..., pathStartPos=16) at qdbusintegrator.cpp:1347
#23 0x00b764da in QDBusActivateObjectEvent::placeMetaCall (this=0xa068318) at qdbusintegrator.cpp:1464
#24 0x005c05fe in QObject::event (this=0xbfe75bb0, e=0xa068318) at kernel/qobject.cpp:1111
#25 0x005afffb in QCoreApplication::event (this=0xbfe75bb0, e=0xa068318) at kernel/qcoreapplication.cpp:1434
#26 0x05fb19a6 in QApplication::event (this=0xbfe75bb0, e=0xa068318) at kernel/qapplication.cpp:2317
#27 0x05fabf54 in QApplicationPrivate::notify_helper (this=0x9b02b70, receiver=0xbfe75bb0, e=0xa068318) at kernel/qapplication.cpp:4056
#28 0x05fb367c in QApplication::notify (this=0xbfe75bb0, receiver=0xbfe75bb0, e=0xa068318) at kernel/qapplication.cpp:3603
#29 0x00993bfa in KApplication::notify (this=0xbfe75bb0, receiver=0xbfe75bb0, event=0xa068318) at ../../kdeui/kernel/kapplication.cpp:302
#30 0x005b06cb in QCoreApplication::notifyInternal (this=0xbfe75bb0, receiver=0xbfe75bb0, event=0xa068318) at kernel/qcoreapplication.cpp:610
#31 0x005b12b2 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x9ad7fa8) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#32 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9ad7fa8) at kernel/qcoreapplication.cpp:1247
#33 0x005b147d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#34 0x005db3ff in QCoreApplication::sendPostedEvents (s=0x9be71c0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#35 postEventSourceDispatch (s=0x9be71c0) at kernel/qeventdispatcher_glib.cpp:210
#36 0x04781e88 in g_main_dispatch (context=0x9aff180) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:1960
#37 IA__g_main_context_dispatch (context=0x9aff180) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2513
#38 0x04785730 in g_main_context_iterate (context=0x9aff180, block=<value optimized out>, dispatch=1, self=0x9afdd58) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2591
#39 0x04785863 in IA__g_main_context_iteration (context=0x9aff180, may_block=1) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2654
#40 0x005db02c in QEventDispatcherGlib::processEvents (this=0x9ad8180, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#41 0x0604cbe5 in QGuiEventDispatcherGlib::processEvents (this=0x9ad8180, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#42 0x005aec79 in QEventLoop::processEvents (this=0xbfe75a74, flags=) at kernel/qeventloop.cpp:149
#43 0x005af0ca in QEventLoop::exec (this=0xbfe75a74, flags=...) at kernel/qeventloop.cpp:201
#44 0x005b153f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#45 0x05fabdd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#46 0x0804a702 in main (argc=3, argv=0xbfe75d64) at ../../kmail/main.cpp:146

Reported using DrKonqi
Comment 1 Paul Crook 2010-02-18 15:42:32 UTC
Resetting my password back to the original one didn't help.

Looking in kdewallet, under kmail, it appears the account is no longer listed.  Kmail however knows about it as it keeps asking for the password before crashing.
Comment 2 Christophe Marin 2010-03-27 10:03:25 UTC

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