Bug 137023

Summary: crash when opening a chat window
Product: [Unmaintained] kopete Reporter: Mathieu Jobin <opensource>
Component: generalAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: crash CC: Stefan.Borggraefe
Priority: NOR    
Version First Reported In: 0.12.3   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Mathieu Jobin 2006-11-08 04:54:47 UTC
Version:           0.12.3 (using KDE 3.5.5, Gentoo)
Compiler:          gcc version 3.3.6 (Gentoo 3.3.6-r1, ssp-3.3.6-1.0, pie-8.7.8)
OS:                Linux (i686) release 2.6.18-justbudget

I had this crash several times recently.
it usually happens when I click "Yes" to receive a chat after I receive a message.

and today, I clicked on "chat" on a online notification bubble. so I guess it crash when openening a chat window except when clicking on the contact list, which works fine. and except few other times where it does not crash.

backtrace attached

System configuration startup check disabled.

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 9194)]
[New Thread 32769 (LWP 9376)]
[KCrash handler]
#7  0xb5dd7fb1 in kill () from /lib/libc.so.6
#8  0xb5fb09b6 in pthread_kill () from /lib/libpthread.so.0
#9  0xb5fb0d19 in raise () from /lib/libpthread.so.0
#10 0xb5dd7d3c in raise () from /lib/libc.so.6
#11 0xb5dd920e in abort () from /lib/libc.so.6
#12 0xb5f78113 in __cxxabiv1::__terminate ()
   from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/libstdc++.so.5
#13 0xb5f78146 in std::terminate ()
   from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/libstdc++.so.5
#14 0xb5f78291 in __cxa_throw ()
   from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/libstdc++.so.5
#15 0xb5f7849d in operator new ()
   from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/libstdc++.so.5
#16 0xb5f7855b in operator new[] ()
   from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/libstdc++.so.5
#17 0xb69075ce in operator>> (s=@0xbf8bba60, str=@0xbf8bbb10)
    at qstring.cpp:6869
#18 0xb73b45b3 in KIO::Slave::createSlave (protocol=@0x8717d68, url=@0x0, 
    error=@0xbf8bbc6c, error_text=@0xbf8bbc90) at slave.cpp:445
#19 0xb73bdb7a in KIO::Scheduler::createSlave (this=0x827a4a0, 
    protInfo=0x8717d20, job=0x958f2c0, url=@0x0) at scheduler.cpp:539
#20 0xb73bd1e9 in KIO::Scheduler::startJobScheduled (this=0x827a4a0, 
    protInfo=0x8717d20) at scheduler.cpp:386
#21 0xb73bc7ba in KIO::Scheduler::startStep (this=0x827a4a0)
    at scheduler.cpp:278
#22 0xb73bf807 in KIO::Scheduler::qt_invoke (this=0x827a4a0, _id=4, 
    _o=0xbf8bbe30) at scheduler.moc:161
#23 0xb658f1b4 in QObject::activate_signal (this=0x827a4c8, clist=0x8271348, 
    o=0xbf8bbe30) at qobject.cpp:2356
#24 0xb658f00c in QObject::activate_signal (this=0x827a4c8, signal=2)
    at qobject.cpp:2325
#25 0xb6979a88 in QTimer::timeout (this=0x827a4c8) at moc_qtimer.cpp:82
#26 0xb65ba8a6 in QTimer::event (this=0x827a4c8, e=0xbf8bc150)
    at qtimer.cpp:219
#27 0xb651e3b7 in QApplication::internalNotify (this=0xbf8bc400, 
    receiver=0x827a4c8, e=0xbf8bc150) at qapplication.cpp:2635
#28 0xb651d5f9 in QApplication::notify (this=0xbf8bc400, receiver=0x827a4c8, 
    e=0xbf8bc150) at qapplication.cpp:2358
#29 0xb6d6ea5f in KApplication::notify (this=0xbf8bc400, receiver=0x827a4c8, 
    event=0xbf8bc150) at kapplication.cpp:550
#30 0xb79c5355 in QApplication::sendEvent (receiver=0x0, event=0x6)
    at qapplication.h:496
#31 0xb650993b in QEventLoop::activateTimers (this=0x81f6458)
    at qeventloop_unix.cpp:556
#32 0xb64b98eb in QEventLoop::processEvents (this=0x81f6458, flags=4)
    at qeventloop_x11.cpp:389
#33 0xb6535921 in QEventLoop::enterLoop (this=0x81f6458) at qeventloop.cpp:198
#34 0xb653583a in QEventLoop::exec (this=0x81f6458) at qeventloop.cpp:145
#35 0xb651e559 in QApplication::exec (this=0xbf8bc400)
    at qapplication.cpp:2758
#36 0x08075046 in main (argc=0, argv=0x0) at main.cpp:107
Comment 1 Philip Rodrigues 2006-11-08 18:59:10 UTC
which protocol?
Comment 2 Mathieu Jobin 2006-11-09 12:52:13 UTC
both jabber and msn.
Comment 3 Matt Rogers 2006-11-10 06:13:18 UTC
rerun kbuildsycoca and see if the crashing continues. Are you using the HTTP proxy with MSN?
Comment 4 Mathieu Jobin 2006-11-10 08:25:39 UTC
no proxy, I'll reopen and let you know if it happens again.
Comment 5 Stefan Borggraefe 2007-07-15 22:36:36 UTC
This is another dupe of bug 141044.
Comment 6 Stefan Borggraefe 2007-07-15 22:37:33 UTC

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