Bug 148998 - kopete crash when removing jabber contact
Summary: kopete crash when removing jabber contact
Status: RESOLVED DUPLICATE of bug 126036
Alias: None
Product: kopete
Classification: Unmaintained
Component: Jabber Plugin (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-19 15:04 UTC by Mathieu Jobin
Modified: 2008-07-03 16:53 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 Mathieu Jobin 2007-08-19 15:04:47 UTC
Version:           unknown (using KDE 3.5.7, Gentoo)
Compiler:          Target: i686-pc-linux-gnu
OS:                Linux (i686) release 2.6.19-suspend2-r1-justbudget

I've got a message from Google Talk server sayin g "contact xxx@gmail.com has removed you from his contact list, you won't be able to see his online status. would you like to remove it from your contact list as well." I clicked YES and kopete crash.

backtrace below....


Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1245435712 (LWP 6618)]
[New Thread -1286587504 (LWP 6966)]
[KCrash handler]
#9  0xb4e7a227 in XMPP::Client::streamReadyRead (this=0x8538ee0)
    at client.cpp:512
#10 0xb4e3ac57 in XMPP::Client::qt_invoke (this=0x8538ee0, _id=3, 
    _o=0xbfd7921c) at im.moc.cpp:542
#11 0xb655e23b in QObject::activate_signal (this=0x908bc30, clist=0x83f1e88, 
    o=0xbfd7921c) at kernel/qobject.cpp:2356
#12 0xb655efd4 in QObject::activate_signal (this=0x908bc30, signal=4)
    at kernel/qobject.cpp:2325
#13 0xb4e399b1 in XMPP::Stream::readyRead (this=0x908bc30) at xmpp.moc.cpp:617
#14 0xb4e6844d in XMPP::ClientStream::doReadyRead (this=0x908bc30)
    at stream.cpp:1280
#15 0xb4e3966a in XMPP::ClientStream::qt_invoke (this=0x908bc30, _id=20, 
    _o=0xbfd79328) at xmpp.moc.cpp:888
#16 0xb655e23b in QObject::activate_signal (this=0x81d23a8, clist=0x9045ff0, 
    o=0xbfd79328) at kernel/qobject.cpp:2356
#17 0xb695f2df in QSignal::signal (this=0x81d23a8, t0=@0x81d23d0)
    at .moc/debug-shared-mt/moc_qsignal.cpp:100
#18 0xb658256f in QSignal::activate (this=0x81d23a8) at kernel/qsignal.cpp:212
#19 0xb658c760 in QSingleShotTimer::event (this=0x81d2380)
    at kernel/qtimer.cpp:286
#20 0xb64e96b3 in QApplication::internalNotify (this=0xbfd7996c, 
    receiver=0x81d2380, e=0xbfd796c8) at kernel/qapplication.cpp:2635
#21 0xb64eb7e5 in QApplication::notify (this=0xbfd7996c, receiver=0x81d2380, 
    e=0xbfd796c8) at kernel/qapplication.cpp:2358
#22 0xb6d7b467 in KApplication::notify (this=0xbfd7996c, receiver=0x81d2380, 
    event=0xbfd796c8) at kapplication.cpp:550
#23 0xb798a25a in QApplication::sendEvent (receiver=0x81d2380, 
    event=0xbfd796c8) at /usr/qt/3/include/qapplication.h:520
#24 0xb64da404 in QEventLoop::activateTimers (this=0x813c178)
    at kernel/qeventloop_unix.cpp:556
#25 0xb648a217 in QEventLoop::processEvents (this=0x813c178, flags=4)
    at kernel/qeventloop_x11.cpp:389
#26 0xb6507971 in QEventLoop::enterLoop (this=0x813c178)
    at kernel/qeventloop.cpp:198
#27 0xb6507792 in QEventLoop::exec (this=0x813c178)
    at kernel/qeventloop.cpp:145
#28 0xb64eb531 in QApplication::exec (this=0xbfd7996c)
    at kernel/qapplication.cpp:2758
#29 0x080745b5 in main (argc=153741304, argv=0x835f3e8) at main.cpp:107
Comment 1 Christophe Marin 2008-07-03 16:53:55 UTC

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