[Bug 202542] closing Kontact with Kwallet waiting for password for Kmail crashes Kontact

[Gerry Gavigan]

https://bugs.kde.org/show_bug.cgi?id=202542





--- Comment #2 from Gerry Gavigan <gavigan iee org>  2009-08-06 11:29:42 ---
Done, here is the result

Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0xb46d4700 (LWP 6913))]

Thread 2 (Thread 0xaff65b90 (LWP 6914)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb65a6f62 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib/libpthread.so.0
#2  0xb660755c in QWaitCondition::wait (this=0x8c1d2d0, mutex=0x8c1d2cc,
time=30000) at thread/qwaitcondition_unix.cpp:85
#3  0xb65fcb96 in QThreadPoolThread::run (this=0x8c1c6f0) at
concurrent/qthreadpool.cpp:140
#4  0xb6606572 in QThreadPrivate::start (arg=0x8c1c6f0) at
thread/qthread_unix.cpp:188
#5  0xb65a31b5 in start_thread () from /lib/libpthread.so.0
#6  0xb58f83be in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb46d4700 (LWP 6913)):
[KCrash Handler]
#6  0xb6a3a94a in KStringHandler::obscure (str=@0x8435a54) at
/usr/include/QtCore/qstring.h:693
#7  0xb0d8ad7f in ?? () from /usr/lib/libkmailprivate.so.4
#8  0xb0e00653 in ?? () from /usr/lib/libkmailprivate.so.4
#9  0xb0d269f5 in KMail::AccountManager::processNextCheck(bool) () from
/usr/lib/libkmailprivate.so.4
#10 0xb0d274c8 in KMail::AccountManager::singleCheckMail(KMAccount*, bool) ()
from /usr/lib/libkmailprivate.so.4
#11 0xb0d2790c in KMail::AccountManager::checkMail(bool) () from
/usr/lib/libkmailprivate.so.4
#12 0xb0ee4338 in KMMainWidget::slotCheckMail() () from
/usr/lib/libkmailprivate.so.4
#13 0xb0f0c571 in KMMainWidget::qt_metacall(QMetaObject::Call, int, void**) ()
from /usr/lib/libkmailprivate.so.4
#14 0xb6710788 in QMetaObject::activate (sender=0x8b36c40, from_signal_index=4,
to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#15 0xb6711412 in QMetaObject::activate (sender=0x8b36c40, m=0xb67f1908,
local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#16 0xb67165b7 in QSingleShotTimer::timeout (this=0x8b36c40) at
.moc/release-shared/qtimer.moc:76
#17 0xb67166dc in QSingleShotTimer::timerEvent (this=0x8b36c40) at
kernel/qtimer.cpp:298
#18 0xb670b72f in QObject::event (this=0x8b36c40, e=0xbfe390a0) at
kernel/qobject.cpp:1075
#19 0xb5bd07fc in QApplicationPrivate::notify_helper (this=0x80833c0,
receiver=0x8b36c40, e=0xbfe390a0) at kernel/qapplication.cpp:4056
#20 0xb5bd8aee in QApplication::notify (this=0xbfe39378, receiver=0x8b36c40,
e=0xbfe390a0) at kernel/qapplication.cpp:3603
#21 0xb6ce327d in KApplication::notify (this=0xbfe39378, receiver=0x8b36c40,
event=0xbfe390a0) at
/usr/src/debug/kdelibs-4.3.0/kdeui/kernel/kapplication.cpp:302
#22 0xb66fb16b in QCoreApplication::notifyInternal (this=0xbfe39378,
receiver=0x8b36c40, event=0xbfe390a0) at kernel/qcoreapplication.cpp:610
#23 0xb672a5f6 in QTimerInfoList::activateTimers (this=0x80740ac) at
kernel/qcoreapplication.h:213
#24 0xb6726980 in timerSourceDispatch (source=0x8074078) at
kernel/qeventdispatcher_glib.cpp:165
#25 0xb4e999c8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#26 0xb4e9d083 in ?? () from /usr/lib/libglib-2.0.so.0
#27 0xb4e9d241 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#28 0xb67268d8 in QEventDispatcherGlib::processEvents (this=0x8053fb0, flags={i
= -1075604920}) at kernel/qeventdispatcher_glib.cpp:327
#29 0xb5c70cc5 in QGuiEventDispatcherGlib::processEvents (this=0x8053fb0,
flags={i = -1075604872}) at kernel/qguieventdispatcher_glib.cpp:202
#30 0xb66f978a in QEventLoop::processEvents (this=0xbfe392f0, flags={i =
-1075604808}) at kernel/qeventloop.cpp:149
#31 0xb66f9bd2 in QEventLoop::exec (this=0xbfe392f0, flags={i = -1075604744})
at kernel/qeventloop.cpp:201
#32 0xb66fc079 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#33 0xb5bd0677 in QApplication::exec () at kernel/qapplication.cpp:3525
#34 0x0804c04f in main (argc=1, argv=0xbfe39674) at
/usr/src/debug/kdepim-4.3.0/kontact/src/main.cpp:218

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.