Bug 130909 - IRC plugin crash on /j #channel
Summary: IRC plugin crash on /j #channel
Status: RESOLVED DUPLICATE of bug 105977
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-16 13:39 UTC by Marcin Gryszkalis
Modified: 2006-07-16 18:22 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 Marcin Gryszkalis 2006-07-16 13:39:53 UTC
Version:           0.12.0 (using KDE KDE 3.5.3)
Installed from:    Gentoo Packages
OS:                Linux

Kopete crashes when I type /j #channel in server window, here is the bt:

Using host libthread_db library "/lib/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1239553856 (LWP 32183)]
[KCrash handler]
#6  0xb7e429b2 in Kopete::ChatSession::setDisplayName (this=0x0, 
    newName=@0xbfb2cb40) at kopetechatsession.cpp:139
#7  0xb5dcc385 in IRCChannelContact::channelTopic (this=0x8b0a760, 
    topic=@0xbfb2cb40) at ircchannelcontact.cpp:271
#8  0xb5deae3b in IRCSignalMappingSingle<IRCChannelContact>::exec (
    this=0xb5dcc2e0, id=@0xbfb2cb40, arg=@0xbfb2cb40)
    at ircsignalhandler.h:197
#9  0xb5de9626 in QMemberSingle::qt_invoke (this=0x854f0f0, _id=2, 
    _o=0xb5e3de78) at ircsignalhandler.h:113
#10 0xb692b3d3 in QObject::activate_signal (this=0x84e2c38, clist=0x852b7d8, 
    o=0xbfb2cc30) at qconnection.h:56
#11 0xb5e0cc1e in KIRC::Engine::incomingExistingTopic (this=0x84e2c38, 
    t0=@0xbfb2cb40, t1=@0xbfb2cb40) at kircengine.moc:1460
#12 0xb5e19cce in KIRC::Engine::numericReply_332 (this=0xbfb2cb40, 
    msg=@0xbfb2cb40) at kircmessage.h:123
#13 0xb5e10618 in KIRC::Engine::qt_invoke (this=0x84e2c38, _id=117, 
    _o=0xbfb2ce60) at qucom_p.h:316
#14 0xb692b3d3 in QObject::activate_signal (this=0x866df00, clist=0x8616588, 
    o=0xbfb2ce60) at qconnection.h:56
#15 0xb5e1ea2a in KIRC::MessageRedirector::redirect (this=0x866df00, 
    t0=@0xbfb2cb40) at kircmessageredirector.moc:95
#16 0xb5e1e720 in KIRC::MessageRedirector::operator() (this=0x866df00, 
    msg=@0xbfb2cf80) at kircmessageredirector.cpp:47
#17 0xb5e0b2bd in KIRC::Engine::slotReadyRead (this=0x84e2c38)
    at kircengine.cpp:371
#18 0xb5e10229 in KIRC::Engine::qt_invoke (this=0x84e2c38, _id=66, 
    _o=0xbfb2d160) at kircengine.moc:2029
#19 0xb692b3d3 in QObject::activate_signal (this=0x8297d08, clist=0x8616588, 
    o=0xbfb2d160) at qconnection.h:56
#20 0xb6c64698 in QSignal::signal (this=0x8297d08, t0=@0xbfb2cb40)
    at .moc/release-shared-mt/moc_qsignal.cpp:100
#21 0xb6944fef in QSignal::activate (this=0x8297d08) at kernel/qsignal.cpp:212
#22 0xb694c6a3 in QSingleShotTimer::event (this=0x8297ce0)
    at kernel/qtimer.cpp:286
#23 0xb68ced0f in QApplication::internalNotify (this=0xbfb2cb40, 
    receiver=0x8297ce0, e=0xbfb2d510) at kernel/qapplication.cpp:2615
#24 0xb68ce175 in QApplication::notify (this=0xbfb2d780, receiver=0x8297ce0, 
    e=0xbfb2d510) at kernel/qapplication.cpp:2372
#25 0xb6f35474 in KApplication::notify (this=0xbfb2d780, receiver=0x8297ce0, 
    event=0xbfb2d510) at kapplication.cpp:550
#26 0xb68be777 in QEventLoop::activateTimers (this=0x822be60)
    at kernel/qeventloop_unix.cpp:555
#27 0xb6879d94 in QEventLoop::processEvents (this=0x822be60, flags=4)
    at kernel/qeventloop_x11.cpp:389
#28 0xb68e0a2a in QEventLoop::enterLoop (this=0x822be60)
    at kernel/qeventloop.cpp:198
#29 0xb68e08c8 in QEventLoop::exec (this=0x822be60)
    at kernel/qeventloop.cpp:145
#30 0xb68cef41 in QApplication::exec (this=0xbfb2d780)
    at kernel/qapplication.cpp:2758
#31 0x0806eb18 in main (argc=-1078801600, argv=0xbfb2cb40) at main.cpp:107
Comment 1 Stefan Borggraefe 2006-07-16 18:22:03 UTC

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