Bug 136911 - crash on getting userinfo on irc
Summary: crash on getting userinfo on irc
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Applications
Component: IRC Plugin (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2006-11-05 21:06 UTC by Adrian Friedli
Modified: 2018-10-27 02:44 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adrian Friedli 2006-11-05 21:07:14 UTC
Version:            (using KDE KDE 3.5.5)
Installed from:    Debian testing/unstable Packages

Hi

Kopete crashes when I try to get userinfo of some users on irc. This only happens on some strange usernames, when the name starts with "&".

Regards
Adrian

(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 -1240254240 (LWP 5588)]
[KCrash handler]
#9  0xb6c7e440 in QString::utf8 () from /usr/lib/libqt-mt.so.3
#10 0xb6c7e5a9 in QString::arg () from /usr/lib/libqt-mt.so.3
#11 0xb5825747 in IRCUserContact::updateInfo ()
   from /usr/lib/kde3/kopete_irc.so
#12 0xb5830e9a in IRCUserContact::whoIsComplete ()
   from /usr/lib/kde3/kopete_irc.so
#13 0xb584eec9 in IRCSignalMapping<IRCUserContact>::exec ()
   from /usr/lib/kde3/kopete_irc.so
#14 0xb581f76e in QMember::qt_invoke () from /usr/lib/kde3/kopete_irc.so
#15 0xb6963cb3 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#16 0xb69641e0 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#17 0xb5865a63 in KIRC::Engine::incomingEndOfWhois ()
   from /usr/lib/kde3/kopete_irc.so
#18 0xb58734ee in KIRC::Engine::numericReply_318 ()
   from /usr/lib/kde3/kopete_irc.so
#19 0xb586a598 in KIRC::Engine::qt_invoke () from /usr/lib/kde3/kopete_irc.so
#20 0xb6963cb3 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#21 0xb58778f1 in KIRC::MessageRedirector::redirect ()
   from /usr/lib/kde3/kopete_irc.so
#22 0xb5877b77 in KIRC::MessageRedirector::operator() ()
   from /usr/lib/kde3/kopete_irc.so
#23 0xb586850a in KIRC::Engine::slotReadyRead ()
   from /usr/lib/kde3/kopete_irc.so
#24 0xb586a018 in KIRC::Engine::qt_invoke () from /usr/lib/kde3/kopete_irc.so
#25 0xb6963cb3 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#26 0xb6ceccef in QSignal::signal () from /usr/lib/libqt-mt.so.3
#27 0xb6983836 in QSignal::activate () from /usr/lib/libqt-mt.so.3
#28 0xb698b208 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#29 0xb68fbbd6 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#30 0xb68fd9f3 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#31 0xb70ace6e in KApplication::notify (this=0xbfaaf28c, receiver=0x8219c70, 
    event=0xbfaaefe8)
    at /home/sid-user/kdelibs/kdelibs-3.5.5/./kdecore/kapplication.cpp:550
#32 0xb688f3d1 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#33 0xb68ee5d3 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#34 0xb68a371f in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#35 0xb6916129 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#36 0xb6915f4a in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#37 0xb68fd76f in QApplication::exec () from /usr/lib/libqt-mt.so.3
#38 0x0807e070 in ?? ()
#39 0xbfaaf28c in ?? ()
#40 0xbfaaf3c0 in ?? ()
#41 0xbfaaf3b8 in ?? ()
#42 0x00000000 in ?? ()
Comment 1 Christoph Feck 2011-12-20 02:58:16 UTC
This crash report is at least 4 years old and there were no further comments or status updates since then.

Therefore we believe that this crash is already fixed in KDE 4 or the backtrace is no longer applicable to KDE 4.

If the crash still happens with a recent KDE version (4.7.4 or 4.8), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

(To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or NEW)
Comment 2 Andrew Crouthamel 2018-09-22 01:50:51 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-10-27 02:44:53 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!