Bug 163472

Summary: Kopete crashed after failing to connect to Yahoo IM protocol
Product: [Unmaintained] kopete Reporter: Adam Jimerson <vendion>
Component: Yahoo PluginAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED FIXED    
Severity: crash CC: des, duffeck, twisted_sketch777
Priority: NOR    
Version First Reported In: 0.50.1   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Screen shot of Kopete/Yahoo error

Description Adam Jimerson 2008-06-07 19:20:39 UTC
Version:           0.50.1 (using 4.0.4 (KDE 4.0.4 >= 20080505) "release 23.2", compiled sources)
Compiler:          gcc
OS:                Linux (i686) release 2.6.22.17-0.1-default

Kopete crashes when not able to connect to Yahoo IM protocol, this seems to happen 3 or 4 times before Kopete crashes.  The error I get back from Kopete is that the server is busy, screen shot will be attached, I also got the following backtrace:

[?1034hUsing host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb5bfe6d0 (LWP 3739)]
[New Thread 0xb10ffb90 (LWP 16795)]
[New Thread 0xb2b95b90 (LWP 16791)]
[KCrash handler]
#6  0xb33b3514 in CoreProtocol::addIncomingData () from /usr/lib/libkyahoo.so.1
#7  0xb33ae79a in ClientStream::bs_readyRead () from /usr/lib/libkyahoo.so.1
#8  0xb33aeaac in ClientStream::qt_metacall () from /usr/lib/libkyahoo.so.1
#9  0xb6fa936a in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#10 0xb6fa97b2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb33ad747 in ByteStream::readyRead () from /usr/lib/libkyahoo.so.1
#12 0xb33ad17a in KNetworkByteStream::slotReadyRead ()
   from /usr/lib/libkyahoo.so.1
#13 0xb33ad24a in KNetworkByteStream::qt_metacall ()
   from /usr/lib/libkyahoo.so.1
#14 0xb6fa936a in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#15 0xb6fa97b2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0xb6fdf807 in QIODevice::readyRead () from /usr/lib/libQtCore.so.4
#17 0xb727b386 in KNetwork::KClientSocketBase::slotReadActivity ()
   from /usr/lib/libkdecore.so.5
#18 0xb727a12b in KNetwork::KBufferedSocket::slotReadActivity ()
   from /usr/lib/libkdecore.so.5
#19 0xb7279596 in KNetwork::KBufferedSocket::qt_metacall ()
   from /usr/lib/libkdecore.so.5
#20 0xb6fa936a in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#21 0xb6fa97b2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#22 0xb6fe1473 in QSocketNotifier::activated () from /usr/lib/libQtCore.so.4
#23 0xb6fb15df in QSocketNotifier::event () from /usr/lib/libQtCore.so.4
#24 0xb657f00c in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#25 0xb6585ff9 in QApplication::notify () from /usr/lib/libQtGui.so.4
#26 0xb75deebd in KApplication::notify () from /usr/lib/libkdeui.so.5
#27 0xb6f98d09 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#28 0xb6fc086a in QEventDispatcherUNIX::activateSocketNotifiers ()
   from /usr/lib/libQtCore.so.4
#29 0xb6fc0deb in QEventDispatcherUNIXPrivate::doSelect ()
   from /usr/lib/libQtCore.so.4
#30 0xb6fc1e74 in QEventDispatcherUNIX::processEvents ()
   from /usr/lib/libQtCore.so.4
#31 0xb6604cd1 in QEventDispatcherX11::processEvents ()
   from /usr/lib/libQtGui.so.4
#32 0xb6f97f9d in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#33 0xb6f98131 in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#34 0xb6f9a27a in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#35 0xb657e707 in QApplication::exec () from /usr/lib/libQtGui.so.4
#36 0x0808826a in main ()
#0  0xffffe410 in __kernel_vsyscall ()
Comment 1 Adam Jimerson 2008-06-07 19:23:04 UTC
Created attachment 25192 [details]
Screen shot of Kopete/Yahoo error

Screen shot of the Yahoo error that causes kopete to crash.
Comment 2 Dirk Mueller 2008-08-18 01:27:38 UTC
*** Bug 169297 has been marked as a duplicate of this bug. ***
Comment 3 Josh Berry 2008-12-04 00:29:59 UTC
Whups, forgot to set confirmed state.  Sorry for the extra spam.

Confirmed in trunk r891864.
Comment 4 Josh Berry 2008-12-04 00:40:21 UTC
D'oh.  I grabbed the wrong bug.  Sorry about that!

(My bugzilla at work goes back to the same bug, but KDE bugzilla moved on to the next one... >.>)
Comment 5 Andre Duffeck 2009-02-04 10:10:37 UTC
I think this is already fixed. Please reopen if it happens again.