Bug 204654 - kontact crash imap broken connection
Summary: kontact crash imap broken connection
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-08-21 14:54 UTC by Andreas K. Huettel
Modified: 2009-08-21 14:59 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 Andreas K. Huettel 2009-08-21 14:54:22 UTC
Application that crashed: kontact
Version of the application: 4.3.0
KDE Version: 4.3.00 (KDE 4.3.0)
Qt Version: 4.5.1
Operating System: Linux 2.6.29-gentoo-r5 x86_64

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  KIO::Slave::deref (this=0x2796cb0) at /var/tmp/portage/kde-base/kdelibs-4.3.0/work/kdelibs-4.3.0/kio/kio/slave.cpp:242
#6  0x00007f2cbd73a40f in KIO::Slave::gotInput (this=0x2796cb0) at /var/tmp/portage/kde-base/kdelibs-4.3.0/work/kdelibs-4.3.0/kio/kio/slave.cpp:335
#7  0x00007f2cbd73c668 in KIO::Slave::qt_metacall (this=0x2796cb0, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fffc9277440)
    at /var/tmp/portage/kde-base/kdelibs-4.3.0/work/kdelibs-4.3.0_build/kio/slave.moc:76
#8  0x00007f2cbb359e4d in QMetaObject::activate (sender=0x27ace10, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x1066a610) at kernel/qobject.cpp:3108
#9  0x00007f2cbd65811f in KIO::ConnectionPrivate::dequeue (this=0x27a7fd0) at /var/tmp/portage/kde-base/kdelibs-4.3.0/work/kdelibs-4.3.0/kio/kio/connection.cpp:82
#10 0x00007f2cbd65857a in KIO::Connection::qt_metacall (this=0x27ace10, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xd879800)
    at /var/tmp/portage/kde-base/kdelibs-4.3.0/work/kdelibs-4.3.0_build/kio/connection.moc:73
#11 0x00007f2cbb3567e1 in QObject::event (this=0x27ace10, e=0xd7d6700) at kernel/qobject.cpp:1106
#12 0x00007f2cbbe9865d in QApplicationPrivate::notify_helper (this=0x1973860, receiver=0x27ace10, e=0xd7d6700) at kernel/qapplication.cpp:4057
#13 0x00007f2cbbea104a in QApplication::notify (this=0x7fffc9277f90, receiver=0x27ace10, e=0xd7d6700) at kernel/qapplication.cpp:4022
#14 0x00007f2cbcc62fab in KApplication::notify (this=0x7fffc9277f90, receiver=0x27ace10, event=0xd7d6700)
    at /var/tmp/portage/kde-base/kdelibs-4.3.0/work/kdelibs-4.3.0/kdeui/kernel/kapplication.cpp:302
#15 0x00007f2cbb347a1b in QCoreApplication::notifyInternal (this=0x7fffc9277f90, receiver=0x27ace10, event=0xd7d6700) at kernel/qcoreapplication.cpp:606
#16 0x00007f2cbb34835e in QCoreApplicationPrivate::sendPostedEvents (receiver=<value optimized out>, event_type=0, data=0x1942230) at kernel/qcoreapplication.h:213
#17 0x00007f2cbb36d1f3 in postEventSourceDispatch (s=<value optimized out>) at kernel/qcoreapplication.h:218
#18 0x00007f2cb6771bf6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#19 0x00007f2cb6774de5 in ?? () from /usr/lib/libglib-2.0.so.0
#20 0x00007f2cb6774ff7 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#21 0x00007f2cbb36ce8f in QEventDispatcherGlib::processEvents (this=0x19733d0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:324
#22 0x00007f2cbbf1e81f in QGuiEventDispatcherGlib::processEvents (this=0x20, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#23 0x00007f2cbb3463d2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -920158800}) at kernel/qeventloop.cpp:149
#24 0x00007f2cbb346565 in QEventLoop::exec (this=0x7fffc9277df0, flags={i = -920158720}) at kernel/qeventloop.cpp:196
#25 0x00007f2cbb3485fc in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#26 0x0000000000404b59 in main (argc=1, argv=0x7fffc9278568) at /var/tmp/portage/kde-base/kontact-4.3.0/work/kontact-4.3.0/kontact/src/main.cpp:218

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

Reported using DrKonqi
Comment 1 Christophe Marin 2009-08-21 14:59:04 UTC

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