Bug 144100 - Crash(SIGABRT) when new message notification was to dissapear.
Summary: Crash(SIGABRT) when new message notification was to dissapear.
Status: RESOLVED DUPLICATE of bug 141044
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-11 23:07 UTC by Raúl
Modified: 2007-07-15 22:29 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 Raúl 2007-04-11 23:07:10 UTC
Version:           0.12.4 (using KDE 3.5.6, Debian Package 4:3.5.6.r1.dfsg.1-2 (4.0))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.20.3rs

I was using kopete normally, it was idle on the system tray till I receive a new message from a friend. The notification went up but when it was going to dissappear kopete crashed with SIGABRT.

Relevant part of .xsession-errors:
-->
kopete: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file jabberchatui.rc
QFont::setPointSize: Point size <= 0 (-1)
QFont::setPointSize: Point size <= 0 (-1)
terminate called after throwing an instance of 'std::bad_alloc'
  what():  St9bad_alloc
KCrash: Application 'kopete' crashing...
kio (KIOConnection): ERROR: Header read failed, errno=104
kio (KIOConnection): ERROR: Header has invalid size (-1)
<--

And this is the backtrace:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1240979776 (LWP 3194)]
[KCrash handler]
#6  0xb7f19410 in __kernel_vsyscall ()
#7  0xb60dc811 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb60ddfb9 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb62c7994 in __gnu_cxx::__verbose_terminate_handler ()
   from /usr/lib/libstdc++.so.6
#10 0xb62c53b5 in ?? () from /usr/lib/libstdc++.so.6
#11 0xb62c53f2 in std::terminate () from /usr/lib/libstdc++.so.6
#12 0xb62c552a in __cxa_throw () from /usr/lib/libstdc++.so.6
#13 0xb62c596b in operator new () from /usr/lib/libstdc++.so.6
#14 0xb62c5a3d in operator new[] () from /usr/lib/libstdc++.so.6
#15 0xb6bcd623 in QString::setLength (this=0xbfd81f10, newLen=913392347)
    at tools/qstring.cpp:1703
#16 0xb6bd4e55 in operator>> (s=@0xbfd81e84, str=@0xbfd81f10)
    at tools/qstring.cpp:6873
#17 0xb74c4ef3 in KIO::Slave::createSlave (protocol=@0x868e378, 
    url=@0x86f9a08, error=@0xbfd81fb4, error_text=@0xbfd81fb0)
    at /tmp/buildd/kdelibs-3.5.6.r1.dfsg.1/./kio/kio/slave.cpp:445
#18 0xb74f5ae2 in KIO::Scheduler::createSlave (this=0x8695ef8, 
    protInfo=0x868e330, job=0x86f9990, url=@0x86f9a08)
    at /tmp/buildd/kdelibs-3.5.6.r1.dfsg.1/./kio/kio/scheduler.cpp:539
#19 0xb7512109 in KIO::Scheduler::startJobScheduled (this=0x8695ef8, 
    protInfo=0x868e330)
    at /tmp/buildd/kdelibs-3.5.6.r1.dfsg.1/./kio/kio/scheduler.cpp:386
#20 0xb75121fe in KIO::Scheduler::startStep (this=0x8695ef8)
    at /tmp/buildd/kdelibs-3.5.6.r1.dfsg.1/./kio/kio/scheduler.cpp:278
#21 0xb75138ac in KIO::Scheduler::qt_invoke (this=0x8695ef8, _id=4, 
    _o=0xbfd8211c) at ./scheduler.moc:161
#22 0xb68b5d4f in QObject::activate_signal (this=0x8695f20, clist=0x86844d8, 
    o=0xbfd8211c) at kernel/qobject.cpp:2356
#23 0xb68b67e0 in QObject::activate_signal (this=0x8695f20, signal=2)
    at kernel/qobject.cpp:2325
#24 0xb6c40faa in QTimer::timeout (this=0x8695f20)
    at .moc/debug-shared-mt/moc_qtimer.cpp:82
#25 0xb68dd603 in QTimer::event (this=0x8695f20, e=0xbfd82468)
    at kernel/qtimer.cpp:219
#26 0xb684dc26 in QApplication::internalNotify (this=0xbfd8270c, 
    receiver=0x8695f20, e=0xbfd82468) at kernel/qapplication.cpp:2635
#27 0xb684fa43 in QApplication::notify (this=0xbfd8270c, receiver=0x8695f20, 
    e=0xbfd82468) at kernel/qapplication.cpp:2358
#28 0xb6fdfc3e in KApplication::notify (this=0xbfd8270c, receiver=0x8695f20, 
    event=0xbfd82468)
    at /tmp/buildd/kdelibs-3.5.6.r1.dfsg.1/./kdecore/kapplication.cpp:550
#29 0xb67e1421 in QApplication::sendEvent (receiver=0x8695f20, 
    event=0xbfd82468) at ../include/qapplication.h:520
#30 0xb6840623 in QEventLoop::activateTimers (this=0x8162d00)
    at kernel/qeventloop_unix.cpp:556
#31 0xb67f576f in QEventLoop::processEvents (this=0x8162d00, flags=4)
    at kernel/qeventloop_x11.cpp:389
#32 0xb6868179 in QEventLoop::enterLoop (this=0x8162d00)
    at kernel/qeventloop.cpp:198
#33 0xb6867f9a in QEventLoop::exec (this=0x8162d00)
    at kernel/qeventloop.cpp:145
#34 0xb684f7bf in QApplication::exec (this=0xbfd8270c)
    at kernel/qapplication.cpp:2758
#35 0x0807e490 in ?? ()
#36 0xbfd8270c in ?? ()
#37 0xbfd82840 in ?? ()
#38 0xbfd82838 in ?? ()
#39 0x00000000 in ?? ()
Comment 1 Raúl 2007-04-13 19:14:58 UTC
I've also repeated this problem when once I opened kopete, double clicked the tray icon. Then double clicked on a contact and double clicked again, the conversation window raised but after that kopete crashed.
Comment 2 Stefan Borggraefe 2007-07-15 22:29:39 UTC

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