Bug 209167 - Segfault after connection interrupted message
Summary: Segfault after connection interrupted message
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-02 02:04 UTC by David
Modified: 2009-10-02 02:07 UTC (History)
1 user (show)

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 David 2009-10-02 02:04:46 UTC
Application that crashed: kontact
Version of the application: 4.3.1
KDE Version: 4.3.1 (KDE 4.3.1)
Qt Version: 4.5.2
Operating System: Linux 2.6.27.30-170.2.82.fc10.x86_64 x86_64
Distribution: "Fedora release 10 (Cambridge)"

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  KIO::Slave::deref (this=0x2a2d450) at /usr/src/debug/kdelibs-4.3.1/kio/kio/slave.cpp:242
#6  0x0000003b9439f53f in KIO::Slave::gotInput (this=0x2a2d450) at /usr/src/debug/kdelibs-4.3.1/kio/kio/slave.cpp:335
#7  0x0000003b943a1798 in KIO::Slave::qt_metacall (this=0x2a2d450, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff7c23e240) at /usr/src/debug/kdelibs-4.3.1/x86_64-redhat-linux-gnu/kio/slave.moc:76
#8  0x000000302bb58f52 in QMetaObject::activate (sender=0x2b66700, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x5e01370) at kernel/qobject.cpp:3113
#9  0x0000003b942bac21 in KIO::ConnectionPrivate::dequeue (this=0x1d434c0) at /usr/src/debug/kdelibs-4.3.1/kio/kio/connection.cpp:82
#10 0x0000003b942bb07a in KIO::Connection::qt_metacall (this=0x2b66700, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x5da5b10)
    at /usr/src/debug/kdelibs-4.3.1/x86_64-redhat-linux-gnu/kio/connection.moc:73
#11 0x000000302bb540d8 in QObject::event (this=0x2b66700, e=0x37956f0) at kernel/qobject.cpp:1111
#12 0x000000302d39008d in QApplicationPrivate::notify_helper (this=0x158cbb0, receiver=0x2b66700, e=0x37956f0) at kernel/qapplication.cpp:4056
#13 0x000000302d3982ca in QApplication::notify (this=0x7fff7c23eca0, receiver=0x2b66700, e=0x37956f0) at kernel/qapplication.cpp:4021
#14 0x0000003b93c134ab in KApplication::notify (this=0x7fff7c23eca0, receiver=0x2b66700, event=0x37956f0) at /usr/src/debug/kdelibs-4.3.1/kdeui/kernel/kapplication.cpp:302
#15 0x000000302bb4407c in QCoreApplication::notifyInternal (this=0x7fff7c23eca0, receiver=0x2b66700, event=0x37956f0) at kernel/qcoreapplication.cpp:610
#16 0x000000302bb44cea in QCoreApplication::sendEvent () at kernel/qcoreapplication.h:213
#17 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x154e850) at kernel/qcoreapplication.cpp:1247
#18 0x000000302bb6d903 in QCoreApplication::sendPostedEvents () at kernel/qcoreapplication.h:218
#19 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:210
#20 0x0000003bcd8377bb in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#21 0x0000003bcd83af8d in ?? () from /lib64/libglib-2.0.so.0
#22 0x0000003bcd83b14b in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#23 0x000000302bb6d58f in QEventDispatcherGlib::processEvents (this=0x154e110, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#24 0x000000302d4274cf in QGuiEventDispatcherGlib::processEvents (this=0x0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#25 0x000000302bb42912 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#26 0x000000302bb42ce4 in QEventLoop::exec (this=0x7fff7c23ec00, flags=) at kernel/qeventloop.cpp:201
#27 0x000000302bb44fb4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#28 0x00000000004045f5 in main (argc=1, argv=0x7fff7c23f388) at /usr/src/debug/kdepim-4.3.1/kontact/src/main.cpp:218

Reported using DrKonqi
Comment 1 David 2009-10-02 02:07:50 UTC
I'm pretty sure this is a duplicate of 191589.

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