Bug 214910 - konact crash when connection disappeared
Summary: konact crash when connection disappeared
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-11-17 02:32 UTC by Danny Auble
Modified: 2009-11-17 07:13 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 Danny Auble 2009-11-17 02:32:54 UTC
Application that crashed: kontact
Version of the application: 4.3.3
KDE Version: 4.3.3 (KDE 4.3.3)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-14-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
The connection was lost and kontact crashed

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  0x02e9909d in KIO::Slave::deref() () from /usr/lib/libkio.so.5
#7  0x02e99c46 in KIO::Slave::gotInput() () from /usr/lib/libkio.so.5
#8  0x02e9c033 in KIO::Slave::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5
#9  0x00cf1263 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#10 0x00cf1ec2 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#11 0x02da4057 in KIO::Connection::readyRead() () from /usr/lib/libkio.so.5
#12 0x02da5e1e in ?? () from /usr/lib/libkio.so.5
#13 0x02da5f4e in KIO::Connection::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5
#14 0x00ce9f0b in QMetaCallEvent::placeMetaCall(QObject*) () from /usr/lib/libQtCore.so.4
#15 0x00ceb5fe in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#16 0x00f88f54 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#17 0x00f9067c in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#18 0x004d614a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#19 0x00cdb6cb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#20 0x00cdc2b2 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#21 0x00cdc47d in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4
#22 0x00d063ff in ?? () from /usr/lib/libQtCore.so.4
#23 0x03999e78 in g_main_dispatch (context=0x9a01320) at /build/buildd/glib2.0-2.22.2/glib/gmain.c:1960
#24 IA__g_main_context_dispatch (context=0x9a01320) at /build/buildd/glib2.0-2.22.2/glib/gmain.c:2513
#25 0x0399d720 in g_main_context_iterate (context=0x9a01320, block=<value optimized out>, dispatch=1, self=0x99ff7b8) at /build/buildd/glib2.0-2.22.2/glib/gmain.c:2591
#26 0x0399d853 in IA__g_main_context_iteration (context=0x9a01320, may_block=1) at /build/buildd/glib2.0-2.22.2/glib/gmain.c:2654
#27 0x00d0602c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#28 0x01029be5 in ?? () from /usr/lib/libQtGui.so.4
#29 0x00cd9c79 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#30 0x00cda0ca in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#31 0x00cdc53f in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#32 0x00f88dd7 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#33 0x0804b4e6 in _start ()

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

Reported using DrKonqi
Comment 1 Christophe Marin 2009-11-17 07:13:24 UTC

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