Bug 210240

Summary: was just clicking in the panel to activate kmail window, then crash
Product: [Unmaintained] kmail Reporter: m.wege
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description m.wege 2009-10-11 21:43:41 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.30-02063003-generic i686
Distribution: Ubuntu 9.04

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#6  KIO::Slave::deref (this=0xedbe0b0) at /build/buildd/kde4libs-4.3.2/kio/kio/slave.cpp:242
#7  0xb6c25e5c in KIO::Slave::gotInput (this=0xedbe0b0) at /build/buildd/kde4libs-4.3.2/kio/kio/slave.cpp:335
#8  0xb6c282e3 in KIO::Slave::qt_metacall (this=0xedbe0b0, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfda08f8) at /build/buildd/kde4libs-4.3.2/obj-i486-linux-gnu/kio/slave.moc:76
#9  0xb5dfc1b8 in QMetaObject::activate (sender=0xedcc8b8, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#10 0xb5dfce42 in QMetaObject::activate (sender=0xedcc8b8, m=0xb6d13880, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#11 0xb6b31a77 in KIO::Connection::readyRead (this=0xedcc8b8) at /build/buildd/kde4libs-4.3.2/obj-i486-linux-gnu/kio/connection.moc:86
#12 0xb6b333e3 in KIO::ConnectionPrivate::dequeue (this=0xedcc8c8) at /build/buildd/kde4libs-4.3.2/kio/kio/connection.cpp:82
#13 0xb6b337c6 in KIO::Connection::qt_metacall (this=0xedcc8b8, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x10ea4528) at /build/buildd/kde4libs-4.3.2/obj-i486-linux-gnu/kio/connection.moc:73
#14 0xb5df58cb in QMetaCallEvent::placeMetaCall (this=0x10ecdbe0, object=0xedcc8b8) at kernel/qobject.cpp:477
#15 0xb5df73b0 in QObject::event (this=0xedcc8b8, e=0x10ecdbe0) at kernel/qobject.cpp:1111
#16 0xb6072d3c in QApplicationPrivate::notify_helper (this=0xa18b560, receiver=0xedcc8b8, e=0x10ecdbe0) at kernel/qapplication.cpp:4056
#17 0xb607b03e in QApplication::notify (this=0xbfda1148, receiver=0xedcc8b8, e=0x10ecdbe0) at kernel/qapplication.cpp:3603
#18 0xb7d9249d in KApplication::notify (this=0xbfda1148, receiver=0xedcc8b8, event=0x10ecdbe0) at /build/buildd/kde4libs-4.3.2/kdeui/kernel/kapplication.cpp:302
#19 0xb5de6bcb in QCoreApplication::notifyInternal (this=0xbfda1148, receiver=0xedcc8b8, event=0x10ecdbe0) at kernel/qcoreapplication.cpp:610
#20 0xb5de7825 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0xa04f1f0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#21 0xb5de7a1d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#22 0xb5e126af in postEventSourceDispatch (s=0xa18b780) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#23 0xb41cab88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#24 0xb41ce0eb in ?? () from /usr/lib/libglib-2.0.so.0
#25 0xb41ce268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#26 0xb5e122f8 in QEventDispatcherGlib::processEvents (this=0xa04f3c8, flags={i = -1076228216}) at kernel/qeventdispatcher_glib.cpp:327
#27 0xb6114a75 in QGuiEventDispatcherGlib::processEvents (this=0xa04f3c8, flags={i = -1076228168}) at kernel/qguieventdispatcher_glib.cpp:202
#28 0xb5de51fa in QEventLoop::processEvents (this=0xbfda1030, flags={i = -1076228104}) at kernel/qeventloop.cpp:149
#29 0xb5de5642 in QEventLoop::exec (this=0xbfda1030, flags={i = -1076228040}) at kernel/qeventloop.cpp:201
#30 0xb5de7ae9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#31 0xb6072bb7 in QApplication::exec () at kernel/qapplication.cpp:3525
#32 0x0804a7d0 in main (argc=) at /build/buildd/kdepim-4.3.2/kmail/main.cpp:146

Reported using DrKonqi
Comment 1 Dario Andres 2009-10-11 22:28:24 UTC
Thanks

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