Bug 196862

Summary: kontact crashed after losing connection with gmail
Product: [Applications] kontact Reporter: Miguel Tadeu <mtadeunet>
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 Miguel Tadeu 2009-06-17 12:28:30 UTC
Application that crashed: kontact
Version of the application: 4.3.0 pre
KDE Version: 4.2.90 (KDE 4.2.90 (KDE 4.3 Beta2))
Qt Version: 4.5.1
Operating System: Linux 2.6.30-9-generic i686
Distribution: Ubuntu karmic (development branch)

What I was doing when the application crashed:
kontact crashed after displaying a window with a message saying it lost connection with my gmail account

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  KIO::Slave::deref (this=0xa4fad08) at ../../kio/kio/slave.cpp:242
#7  0x046f3e96 in KIO::Slave::gotInput (this=0xa4fad08) at ../../kio/kio/slave.cpp:335
#8  0x046f62b3 in KIO::Slave::qt_metacall (this=0xa4fad08, _c=QMetaObject::InvokeMetaMethod, _id=30, _a=0xbfde1c3c) at ./slave.moc:76
#9  0x009dbff3 in QMetaObject::activate (sender=0xa479fb0, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3120
#10 0x009dcc42 in QMetaObject::activate (sender=0xa479fb0, m=0x48148a0, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3194
#11 0x045ff337 in KIO::Connection::readyRead (this=0xa479fb0) at ./connection.moc:86
#12 0x046010fe in KIO::ConnectionPrivate::dequeue (this=0xa31e490) at ../../kio/kio/connection.cpp:82
#13 0x0460122e in KIO::Connection::qt_metacall (this=0xa479fb0, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xa943078) at ./connection.moc:73
#14 0x009d4bab in QMetaCallEvent::placeMetaCall (this=0xa73b218, object=0xa479fb0) at kernel/qobject.cpp:489
#15 0x009d629e in QObject::event (this=0xa479fb0, e=0xa73b218) at kernel/qobject.cpp:1118
#16 0x00e2daa4 in QApplicationPrivate::notify_helper (this=0x96d7cd8, receiver=0xa479fb0, e=0xa73b218) at kernel/qapplication.cpp:4057
#17 0x00e351dc in QApplication::notify (this=0xbfde24d4, receiver=0xa479fb0, e=0xa73b218) at kernel/qapplication.cpp:3604
#18 0x0051002a in KApplication::notify (this=0xbfde24d4, receiver=0xa479fb0, event=0xa73b218) at ../../kdeui/kernel/kapplication.cpp:302
#19 0x009c617b in QCoreApplication::notifyInternal (this=0xbfde24d4, receiver=0xa479fb0, event=0xa73b218) at kernel/qcoreapplication.cpp:610
#20 0x009c6c42 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x96b2278) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#21 0x009c6e0d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#22 0x009f10df in postEventSourceDispatch (s=0x96d9420) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#23 0x08765b18 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#24 0x087690b0 in ?? () from /usr/lib/libglib-2.0.so.0
#25 0x087691e3 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#26 0x009f0d0c in QEventDispatcherGlib::processEvents (this=0x96d16a0, flags={i = 36}) at kernel/qeventdispatcher_glib.cpp:324
#27 0x00ece5c5 in QGuiEventDispatcherGlib::processEvents (this=0x96d16a0, flags={i = 36}) at kernel/qguieventdispatcher_glib.cpp:202
#28 0x009c4729 in QEventLoop::processEvents (this=0xbfde2434, flags=) at kernel/qeventloop.cpp:149
#29 0x009c4b72 in QEventLoop::exec (this=0xbfde2434, flags={i = 0}) at kernel/qeventloop.cpp:200
#30 0x009c6ecf in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#31 0x00e2d927 in QApplication::exec () at kernel/qapplication.cpp:3526
#32 0x0804b4d6 in main (argc=1, argv=0xbfde26d4) at ../../../kontact/src/main.cpp:218

Reported using DrKonqi
Comment 1 Dario Andres 2009-06-17 22:03:26 UTC
Thanks

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