Bug 201594

Summary: kmail crashed while I was not at the computer, so don't know what happenend
Product: [Unmaintained] kmail Reporter: m.wege
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 m.wege 2009-07-26 23:26:56 UTC
Application that crashed: kmail
Version of the application: 1.12.0
KDE Version: 4.2.98 (KDE 4.2.98 (KDE 4.3 RC3))
Qt Version: 4.5.1
Operating System: Linux 2.6.30-020630rc6-generic i686
Distribution: Ubuntu 9.04

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#6  KIO::Slave::deref (this=0x9e179d0) at /build/buildd/kde4libs-4.2.98a/kio/kio/slave.cpp:242
#7  0xb6cd5dec in KIO::Slave::gotInput (this=0x9e179d0) at /build/buildd/kde4libs-4.2.98a/kio/kio/slave.cpp:335
#8  0xb6cd8273 in KIO::Slave::qt_metacall (this=0x9e179d0, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfc52848) at /build/buildd/kde4libs-4.2.98a/obj-i486-linux-gnu/kio/slave.moc:76
#9  0xb5e83a58 in QMetaObject::activate (sender=0x9d3cb90, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3120
#10 0xb5e846e2 in QMetaObject::activate (sender=0x9d3cb90, m=0xb6dc3880, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3194
#11 0xb6be2147 in KIO::Connection::readyRead (this=0x9d3cb90) at /build/buildd/kde4libs-4.2.98a/obj-i486-linux-gnu/kio/connection.moc:86
#12 0xb6be3ab3 in KIO::ConnectionPrivate::dequeue (this=0xb682738) at /build/buildd/kde4libs-4.2.98a/kio/kio/connection.cpp:82
#13 0xb6be3e96 in KIO::Connection::qt_metacall (this=0x9d3cb90, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xbafc708) at /build/buildd/kde4libs-4.2.98a/obj-i486-linux-gnu/kio/connection.moc:73
#14 0xb5e7c6ab in QMetaCallEvent::placeMetaCall (this=0xb978dc8, object=0x9d3cb90) at kernel/qobject.cpp:489
#15 0xb5e7e150 in QObject::event (this=0x9d3cb90, e=0xb978dc8) at kernel/qobject.cpp:1118
#16 0xb60f8bcc in QApplicationPrivate::notify_helper (this=0x8438858, receiver=0x9d3cb90, e=0xb978dc8) at kernel/qapplication.cpp:4057
#17 0xb6100ede in QApplication::notify (this=0xbfc53078, receiver=0x9d3cb90, e=0xb978dc8) at kernel/qapplication.cpp:3604
#18 0xb7e365cd in KApplication::notify (this=0xbfc53078, receiver=0x9d3cb90, event=0xb978dc8) at /build/buildd/kde4libs-4.2.98a/kdeui/kernel/kapplication.cpp:302
#19 0xb5e6d7ab in QCoreApplication::notifyInternal (this=0xbfc53078, receiver=0x9d3cb90, event=0xb978dc8) at kernel/qcoreapplication.cpp:610
#20 0xb5e6e405 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x84121f0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#21 0xb5e6e5fd in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#22 0xb5e9958f in postEventSourceDispatch (s=0x843d900) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#23 0xb4273b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#24 0xb42770eb in ?? () from /usr/lib/libglib-2.0.so.0
#25 0xb4277268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#26 0xb5e991d8 in QEventDispatcherGlib::processEvents (this=0x84123c8, flags={i = -1077596456}) at kernel/qeventdispatcher_glib.cpp:324
#27 0xb619a765 in QGuiEventDispatcherGlib::processEvents (this=0x84123c8, flags={i = -1077596408}) at kernel/qguieventdispatcher_glib.cpp:202
#28 0xb5e6bdda in QEventLoop::processEvents (this=0xbfc52f80, flags={i = -1077596344}) at kernel/qeventloop.cpp:149
#29 0xb5e6c21a in QEventLoop::exec (this=0xbfc52f80, flags={i = -1077596280}) at kernel/qeventloop.cpp:200
#30 0xb5e6e6c9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#31 0xb60f8a47 in QApplication::exec () at kernel/qapplication.cpp:3526
#32 0x0804a7d0 in main (argc=) at /build/buildd/kdepim-4.2.98/kmail/main.cpp:146

Reported using DrKonqi
Comment 1 Christophe Marin 2009-07-27 09:34:17 UTC

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