Bug 216303

Summary: Kmail crash after clicking "ok" on the "unable to contact server" dialog
Product: [Unmaintained] kmail Reporter: yann jautard <bricofoy>
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 yann jautard 2009-11-26 21:13:21 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:
Lost my internet connexion.
kmail tried to get my message on IMAP server
kmail show message box saying it lost connexion to server

I cliked "ok" ---> crash

everytime this message box appears I got the crash

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

Thread 2 (Thread 0xb1a56b70 (LWP 2561)):
#0  0x00edb422 in __kernel_vsyscall ()
#1  0x02880142 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0x009417e4 in pthread_cond_timedwait () from /lib/tls/i686/cmov/libc.so.6
#3  0x00b89def in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4
#4  0x00b7e9ae in ?? () from /usr/lib/libQtCore.so.4
#5  0x00b88e32 in ?? () from /usr/lib/libQtCore.so.4
#6  0x0287b80e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7  0x009347ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb7850aa0 (LWP 2033)):
[KCrash Handler]
#6  0x02ab5f4d in KIO::Slave::deref() () from /usr/lib/libkio.so.5
#7  0x02ab6af6 in KIO::Slave::gotInput() () from /usr/lib/libkio.so.5
#8  0x02ab8ee3 in KIO::Slave::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5
#9  0x00c8f263 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#10 0x00c8fec2 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#11 0x029c0f97 in KIO::Connection::readyRead() () from /usr/lib/libkio.so.5
#12 0x029c2d5e in ?? () from /usr/lib/libkio.so.5
#13 0x029c2e8e in KIO::Connection::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5
#14 0x00c87f0b in QMetaCallEvent::placeMetaCall(QObject*) () from /usr/lib/libQtCore.so.4
#15 0x00c895fe in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#16 0x04022f54 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#17 0x0402a67c in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#18 0x00460bfa in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#19 0x00c796cb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#20 0x00c7a2b2 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#21 0x00c7a47d in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4
#22 0x00ca43ff in ?? () from /usr/lib/libQtCore.so.4
#23 0x01ebbe78 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#24 0x01ebf720 in ?? () from /lib/libglib-2.0.so.0
#25 0x01ebf853 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#26 0x00ca402c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#27 0x040c3be5 in ?? () from /usr/lib/libQtGui.so.4
#28 0x00c77c79 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#29 0x00c780ca in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#30 0x00c7a53f in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#31 0x04022dd7 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#32 0x0804a702 in _start ()

This bug may be a duplicate of or related to bug 211727

Reported using DrKonqi
Comment 1 Christophe Marin 2009-11-27 01:32:16 UTC

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