Bug 203222 - kmail crashes after losing imap connection
Summary: kmail crashes after losing imap connection
Status: RESOLVED DUPLICATE of bug 191589
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-09 22:39 UTC by Thorsten Zantis
Modified: 2009-08-09 23:10 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 Thorsten Zantis 2009-08-09 22:39:55 UTC
Application that crashed: kmail
Version of the application: 1.12.0
KDE Version: 4.3.00 (KDE 4.3.0)
Qt Version: 4.5.2
Operating System: Linux 2.6.30-1-amd64 x86_64

What I was doing when the application crashed:
Message appears that connection is broken, after that the crash reporting tool kicks in... here you are. :D

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#5  KIO::Slave::deref (this=0x19859b0) at ../../kio/kio/slave.cpp:242
#6  0x00007f23948bb43a in KIO::Slave::gotInput (this=0x19859b0) at ../../kio/kio/slave.cpp:335
#7  0x00007f23948bd758 in KIO::Slave::qt_metacall (this=0x19859b0, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fffa81d7710) at ./slave.moc:76
#8  0x00007f239b03b602 in QMetaObject::activate (sender=0x22ec760, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x24e2df0) at kernel/qobject.cpp:3112
#9  0x00007f23947d8381 in KIO::ConnectionPrivate::dequeue (this=0x22db0e0) at ../../kio/kio/connection.cpp:82
#10 0x00007f23947d87da in KIO::Connection::qt_metacall (this=0x22ec760, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x19852d0) at ./connection.moc:73
#11 0x00007f239b035ee8 in QObject::event (this=0x22ec760, e=0x2354a40) at kernel/qobject.cpp:1110
#12 0x00007f239a49e7ad in QApplicationPrivate::notify_helper (this=0x173b3d0, receiver=0x22ec760, e=0x2354a40) at kernel/qapplication.cpp:4056
#13 0x00007f239a4a680a in QApplication::notify (this=0x7fffa81d8280, receiver=0x22ec760, e=0x2354a40) at kernel/qapplication.cpp:4021
#14 0x00007f239c6d4b2b in KApplication::notify (this=0x7fffa81d8280, receiver=0x22ec760, event=0x2354a40) at ../../kdeui/kernel/kapplication.cpp:302
#15 0x00007f239b02649c in QCoreApplication::notifyInternal (this=0x7fffa81d8280, receiver=0x22ec760, event=0x2354a40) at kernel/qcoreapplication.cpp:610
#16 0x00007f239b0270e4 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x1706340) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#17 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x1706340) at kernel/qcoreapplication.cpp:1247
#18 0x00007f239b04eef3 in QCoreApplication::sendPostedEvents (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#19 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:210
#20 0x00007f23923c67aa in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#21 0x00007f23923c9df8 in ?? () from /usr/lib/libglib-2.0.so.0
#22 0x00007f23923c9fac in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#23 0x00007f239b04eb7f in QEventDispatcherGlib::processEvents (this=0x1705fa0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#24 0x00007f239a5355ef in QGuiEventDispatcherGlib::processEvents (this=0x20, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#25 0x00007f239b024d62 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#26 0x00007f239b025134 in QEventLoop::exec (this=0x7fffa81d80d0, flags=...) at kernel/qeventloop.cpp:201
#27 0x00007f239b0273a4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#28 0x0000000000402fab in main (argc=<value optimized out>, argv=<value optimized out>) at ../../kmail/main.cpp:146

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

Reported using DrKonqi
Comment 1 Christophe Marin 2009-08-09 23:10:27 UTC

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