Bug 200569 - kopete crash in libkyahoo
Summary: kopete crash in libkyahoo
Status: RESOLVED DUPLICATE of bug 200186
Alias: None
Product: kopete
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-17 17:31 UTC by Paul Fee
Modified: 2009-08-11 20:03 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Fee 2009-07-17 17:31:42 UTC
Application that crashed: kopete
Version of the application: 0.70.90
KDE Version: 4.2.96 (KDE 4.2.96 (KDE 4.3 RC2))
Qt Version: 4.5.0
Operating System: Linux 2.6.28-13-generic x86_64
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
kopete had been running for a few hours, so this isn't related to logging into Yahoo IM.

I wasn't interacting with kopete at the time, so presumably this was provoked by background kopete/yahoo communication.

Important libkyahoo details in the stack trace are missing, however the debuginfo package for kopete wasn't available for installation.  Hope there's enough info anyway.

Current kopete package: 4:4.2.96-0ubuntu1~jaunty1~ppa1

$ sudo apt-get install kopete-dbg
E: Couldn't find package kopete-dbg

If a debuginfo could be place in the repo, then better bracktraces could be provided.

Thanks.

 -- Backtrace:
Application: Kopete (kopete), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f6bf4fbd0e4 in KIO::TransferJob::isErrorPage (this=0x1f6f400) at /build/buildd/kde4libs-4.2.96/kio/kio/job.cpp:1121
#6  0x00007f6be43de11e in ?? () from /usr/lib/libkyahoo.so.1
#7  0x00007f6be43dece1 in ?? () from /usr/lib/libkyahoo.so.1
#8  0x00007f6bf399f1f2 in QMetaObject::activate (sender=0xc5c610, from_signal_index=<value optimized out>, to_signal_index=7, argv=0x7fffff9b9040) at kernel/qobject.cpp:3069
#9  0x00007f6bf3fe3512 in KJob::result (this=0x1f6f400, _t1=0xc5c610) at /build/buildd/kde4libs-4.2.96/obj-x86_64-linux-gnu/kdecore/kjob.moc:188
#10 0x00007f6bf3fe388f in KJob::emitResult (this=0xc5c610) at /build/buildd/kde4libs-4.2.96/kdecore/jobs/kjob.cpp:304
#11 0x00007f6bf4fc7d70 in KIO::SimpleJob::slotFinished (this=0xc5c610) at /build/buildd/kde4libs-4.2.96/kio/kio/job.cpp:477
#12 0x00007f6bf4fc8223 in KIO::TransferJob::slotFinished (this=0xc5c610) at /build/buildd/kde4libs-4.2.96/kio/kio/job.cpp:948
#13 0x00007f6bf4fc3015 in KIO::TransferJob::qt_metacall (this=0xc5c610, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffff9b9440)
    at /build/buildd/kde4libs-4.2.96/obj-x86_64-linux-gnu/kio/jobclasses.moc:343
#14 0x00007f6bf399f1f2 in QMetaObject::activate (sender=0xe53b50, from_signal_index=<value optimized out>, to_signal_index=8, argv=0x7fffff9b9040) at kernel/qobject.cpp:3069
#15 0x00007f6bf5084371 in KIO::SlaveInterface::dispatch (this=0xe53b50, _cmd=104, rawdata=<value optimized out>) at /build/buildd/kde4libs-4.2.96/kio/kio/slaveinterface.cpp:175
#16 0x00007f6bf5080ec2 in KIO::SlaveInterface::dispatch (this=0xe53b50) at /build/buildd/kde4libs-4.2.96/kio/kio/slaveinterface.cpp:91
#17 0x00007f6bf5073a43 in KIO::Slave::gotInput (this=0xe53b50) at /build/buildd/kde4libs-4.2.96/kio/kio/slave.cpp:322
#18 0x00007f6bf5075ca8 in KIO::Slave::qt_metacall (this=0xe53b50, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fffff9b9860) at /build/buildd/kde4libs-4.2.96/obj-x86_64-linux-gnu/kio/slave.moc:76
#19 0x00007f6bf399f1f2 in QMetaObject::activate (sender=0x1d30f60, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x7fffff9b9040) at kernel/qobject.cpp:3069
#20 0x00007f6bf4f91761 in KIO::ConnectionPrivate::dequeue (this=0x1d29400) at /build/buildd/kde4libs-4.2.96/kio/kio/connection.cpp:82
#21 0x00007f6bf4f91bba in KIO::Connection::qt_metacall (this=0x1d30f60, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xdf2810)
    at /build/buildd/kde4libs-4.2.96/obj-x86_64-linux-gnu/kio/connection.moc:73
#22 0x00007f6bf3999848 in QObject::event (this=0x1d30f60, e=0x1d4bb80) at kernel/qobject.cpp:1118
#23 0x00007f6bf2b7378d in QApplicationPrivate::notify_helper (this=0x97a250, receiver=0x1d30f60, e=0x1d4bb80) at kernel/qapplication.cpp:4084
#24 0x00007f6bf2b7b97a in QApplication::notify (this=0x7fffff9badc0, receiver=0x1d30f60, e=0x1d4bb80) at kernel/qapplication.cpp:4049
#25 0x00007f6bf457763b in KApplication::notify (this=0x7fffff9badc0, receiver=0x1d30f60, event=0x1d4bb80) at /build/buildd/kde4libs-4.2.96/kdeui/kernel/kapplication.cpp:302
#26 0x00007f6bf398975c in QCoreApplication::notifyInternal (this=0x7fffff9badc0, receiver=0x1d30f60, event=0x1d4bb80) at kernel/qcoreapplication.cpp:602
#27 0x00007f6bf398a3ca in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x94d720) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#28 0x00007f6bf39b31e3 in postEventSourceDispatch (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#29 0x00007f6bedd8920a in IA__g_main_context_dispatch (context=0x984520) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:1814
#30 0x00007f6bedd8c8e0 in g_main_context_iterate (context=0x984520, block=1, dispatch=1, self=<value optimized out>) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2448
#31 0x00007f6bedd8ca7c in IA__g_main_context_iteration (context=0x984520, may_block=1) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2511
#32 0x00007f6bf39b2e6f in QEventDispatcherGlib::processEvents (this=0x94cf70, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:323
#33 0x00007f6bf2c0bbef in QGuiEventDispatcherGlib::processEvents (this=0x1f6f400, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#34 0x00007f6bf3988002 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -6577696}) at kernel/qeventloop.cpp:149
#35 0x00007f6bf39883cd in QEventLoop::exec (this=0x7fffff9ba220, flags={i = -6577600}) at kernel/qeventloop.cpp:200
#36 0x00007f6bf303110e in QDialog::exec (this=0xdc2620) at dialogs/qdialog.cpp:498
#37 0x00007f6bf44ea38f in KDialogQueue::Private::slotShowQueuedDialog (this=0xd44420) at /build/buildd/kde4libs-4.2.96/kdeui/dialogs/kdialog.cpp:1055
#38 0x00007f6bf44ea43d in KDialogQueue::qt_metacall (this=0xd44370, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=<value optimized out>)
    at /build/buildd/kde4libs-4.2.96/obj-x86_64-linux-gnu/kdeui/kdialogqueue_p.moc:66
#39 0x00007f6bf399f1f2 in QMetaObject::activate (sender=0xdf5890, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x7fffff9b9040) at kernel/qobject.cpp:3069
#40 0x00007f6bf39a452f in QSingleShotTimer::timerEvent (this=0xdf5890) at kernel/qtimer.cpp:298
#41 0x00007f6bf39994d3 in QObject::event (this=0xdf5890, e=0xc5c610) at kernel/qobject.cpp:1082
#42 0x00007f6bf2b7378d in QApplicationPrivate::notify_helper (this=0x97a250, receiver=0xdf5890, e=0x7fffff9baa80) at kernel/qapplication.cpp:4084
#43 0x00007f6bf2b7b97a in QApplication::notify (this=0x7fffff9badc0, receiver=0xdf5890, e=0x7fffff9baa80) at kernel/qapplication.cpp:4049
#44 0x00007f6bf457763b in KApplication::notify (this=0x7fffff9badc0, receiver=0xdf5890, event=0x7fffff9baa80) at /build/buildd/kde4libs-4.2.96/kdeui/kernel/kapplication.cpp:302
#45 0x00007f6bf398975c in QCoreApplication::notifyInternal (this=0x7fffff9badc0, receiver=0xdf5890, event=0x7fffff9baa80) at kernel/qcoreapplication.cpp:602
#46 0x00007f6bf39b67f6 in QTimerInfoList::activateTimers (this=0x985340) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#47 0x00007f6bf39b2f0d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:164
#48 0x00007f6bedd8920a in IA__g_main_context_dispatch (context=0x984520) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:1814
#49 0x00007f6bedd8c8e0 in g_main_context_iterate (context=0x984520, block=1, dispatch=1, self=<value optimized out>) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2448
#50 0x00007f6bedd8ca7c in IA__g_main_context_iteration (context=0x984520, may_block=1) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2511
#51 0x00007f6bf39b2e6f in QEventDispatcherGlib::processEvents (this=0x94cf70, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:323
#52 0x00007f6bf2c0bbef in QGuiEventDispatcherGlib::processEvents (this=0x1f6f400, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#53 0x00007f6bf3988002 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -6574864}) at kernel/qeventloop.cpp:149
#54 0x00007f6bf39883cd in QEventLoop::exec (this=0x7fffff9bad30, flags={i = -6574784}) at kernel/qeventloop.cpp:200
#55 0x00007f6bf398a694 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#56 0x0000000000415738 in _start ()

Reported using DrKonqi
Comment 1 Dario Andres 2009-07-17 22:37:12 UTC
This looks related to bug 200186 / bug 200207
BTW, the debug package is named "kdenetwork-dbg", if you could install it and try to get a new backtrace it could be great.
Thanks
Comment 2 Paul Fee 2009-07-18 10:36:34 UTC
Hi Dario,

Thanks for the info on where to find the debuginfo package.

Curious that "dpkg -S /usr/lib/libkyahoo.so.1" showed that the library came from the kopete package, yet the debuginfo data is in kdenetwork-dbg.

I've been following the convention of installing the package with the same name, but with a -dbg suffix.  If this isn't always the case, do you have tips on how to find the right debuginfo package for other packages?

I'll install kdenetwork-dbg and post a new backtrace should the crash happen again.

Thanks,
Paul
Comment 3 Dario Andres 2009-08-08 15:53:00 UTC
Thanks.
On Debian/Ubuntu like distributions, the KDE packages for installation uses the name of the app (they are splitted; like "kopete", "kget" ...); but the debug information packages uses the name of the whole module (kdebase, kdenetwork, kdegraphics, kdemultimedia) plus the "-dbg" suffix
Comment 4 Paul Fee 2009-08-10 00:37:29 UTC
This particular bug hasn't recurred, so I'm unable to give a better stack trace at this time.

I'm unable to say whether the bug has been fixed, if my usage pattern has changed or if Yahoo servers are behaving differently such that the relevant code containing the bug is not getting triggered.
Comment 5 Dario Andres 2009-08-11 20:03:22 UTC
Thanks. I'm merging with bug 200186.

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