Bug 210460 - KMail crashes after network disconnect using dimap
Summary: KMail crashes after network disconnect using dimap
Status: RESOLVED DUPLICATE of bug 191589
Alias: None
Product: kontact
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-10-13 19:11 UTC by Jeremy Kloth
Modified: 2009-10-14 01:04 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jeremy Kloth 2009-10-13 19:11:22 UTC
Application that crashed: kontact
Version of the application: 4.3.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.28-15-generic x86_64
Distribution: Ubuntu 9.04

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  KIO::Slave::deref (this=0x2d15970) at /build/buildd/kde4libs-4.3.2/kio/kio/slave.cpp:242
#6  0x00007f12000dd2bf in KIO::Slave::gotInput (this=0x2d15970) at /build/buildd/kde4libs-4.3.2/kio/kio/slave.cpp:335
#7  0x00007f12000df518 in KIO::Slave::qt_metacall (this=0x2d15970, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff0b689e80) at /build/buildd/kde4libs-4.3.2/obj-x86_64-linux-gnu/kio/slave.moc:76
#8  0x00007f11fdbd9ea2 in QMetaObject::activate (sender=0x2d15f70, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x498bf20) at kernel/qobject.cpp:3113
#9  0x00007f11ffffa161 in KIO::ConnectionPrivate::dequeue (this=0x2d160a0) at /build/buildd/kde4libs-4.3.2/kio/kio/connection.cpp:82
#10 0x00007f11ffffa5ba in KIO::Connection::qt_metacall (this=0x2d15f70, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x399ee90)
    at /build/buildd/kde4libs-4.3.2/obj-x86_64-linux-gnu/kio/connection.moc:73
#11 0x00007f11fdbd45d8 in QObject::event (this=0x2d15f70, e=0x3e66530) at kernel/qobject.cpp:1111
#12 0x00007f11fe745f4d in QApplicationPrivate::notify_helper (this=0x1435ce0, receiver=0x2d15f70, e=0x3e66530) at kernel/qapplication.cpp:4056
#13 0x00007f11fe74e18a in QApplication::notify (this=0x7fff0b68a8e0, receiver=0x2d15f70, e=0x3e66530) at kernel/qapplication.cpp:4021
#14 0x00007f11ffb4aabb in KApplication::notify (this=0x7fff0b68a8e0, receiver=0x2d15f70, event=0x3e66530) at /build/buildd/kde4libs-4.3.2/kdeui/kernel/kapplication.cpp:302
#15 0x00007f11fdbc46ac in QCoreApplication::notifyInternal (this=0x7fff0b68a8e0, receiver=0x2d15f70, event=0x3e66530) at kernel/qcoreapplication.cpp:610
#16 0x00007f11fdbc531a in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x1407850) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#17 0x00007f11fdbede03 in postEventSourceDispatch (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#18 0x00007f11f731520a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#19 0x00007f11f73188e0 in ?? () from /usr/lib/libglib-2.0.so.0
#20 0x00007f11f7318a7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#21 0x00007f11fdbeda8f in QEventDispatcherGlib::processEvents (this=0x14070a0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#22 0x00007f11fe7debdf in QGuiEventDispatcherGlib::processEvents (this=0x6112, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#23 0x00007f11fdbc2f42 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 191408128}) at kernel/qeventloop.cpp:149
#24 0x00007f11fdbc3314 in QEventLoop::exec (this=0x7fff0b68a840, flags={i = 191408208}) at kernel/qeventloop.cpp:201
#25 0x00007f11fdbc55e4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#26 0x0000000000404945 in main (argc=1, argv=0x7fff0b68afc8) at /build/buildd/kdepim-4.3.2/kontact/src/main.cpp:218

Reported using DrKonqi
Comment 1 Christophe Marin 2009-10-14 01:04:59 UTC

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