Version: 0.12.1 (using KDE KDE 3.5.4) Installed from: SuSE RPMs OS: Linux Go online with the IRC-plugin and open a private chat window by sending a message to yourself. /msg nickname Close the new window by clicking on the X at the top right. You have found another shortcut for closing kopete. ;)
Created attachment 17359 [details] Backtrace of closing IRC chat to myself
Created attachment 26843 [details] Crash log
It seems the server is having trouble letting me edit the description on my initial comment. I meant to say that I can confirm this bug on Kopete 0.12.7 using KDE 3.5.9 on Kubuntu 8.04.1, although my backtrace appears to be slightly different.
Comment on attachment 26843 [details] Crash log I can confirm this bug on Kopete 0.12.7 using KDE 3.5.9 on Kubuntu 8.04.1, although my backtrace appears to be slightly different.
These are all the same backtrace actually, one doesn't have line numbers, another the Qt calls. Not sure if this exists at all in 4, since I'm not sure if it the codebase is completely rewritten or not (irc support is not releasable atm). #6 0xb7e341b1 in QMapPrivate<QString, Kopete::ContactProperty>::end ( this=0x28) at /usr/lib/qt3/include/qmap.h:380 #7 0xb7e341f5 in QMap<QString, Kopete::ContactProperty>::end (this=0x84d7190) at /usr/lib/qt3/include/qmap.h:663 #8 0xb7e34d42 in QMap<QString, Kopete::ContactProperty>::contains ( this=0x84d7190, k=@0x87106d0) at /usr/lib/qt3/include/qmap.h:703 #9 0xb7e2f8be in Kopete::Contact::hasProperty (this=0x849af88, key=@0x87106d0) at /home/jan/Dev/kde35/kdenetwork/0.12/kopete/libkopete/kopetecontact.cpp:578 #10 0xb7e2f8f4 in Kopete::Contact::property (this=0x849af88, tmpl=@0x8564260) at /home/jan/Dev/kde35/kdenetwork/0.12/kopete/libkopete/kopetecontact.cpp:592 #11 0xb7e2f960 in Kopete::Contact::nickName (this=0x849af88) at /home/jan/Dev/kde35/kdenetwork/0.12/kopete/libkopete/kopetecontact.cpp:847 #12 0xb5cf0187 in ChatMessagePart::formatStyleKeywords (this=0x845f850, sourceHTML=@0xbfae1854) at /home/jan/Dev/kde35/kdenetwork/0.12/kopete/kopete/chatwindow/chatmessagepart.cpp:1102 #13 0xb5cf3808 in ChatMessagePart::writeTemplate (this=0x845f850) at /home/jan/Dev/kde35/kdenetwork/0.12/kopete/kopete/chatwindow/chatmessagepart.cpp:1296 #14 0xb5cf468c in ChatMessagePart::changeStyle (this=0x845f850) at /home/jan/Dev/kde35/kdenetwork/0.12/kopete/kopete/chatwindow/chatmessagepart.cpp:1232 #15 0xb5cf552c in ChatMessagePart::qt_invoke (this=0x845f850, _id=108, _o=0xbfae1964) at /home/jan/Dev/kde35/kdenetwork/0.12/kopete/kopete/chatwindow/chatmessagepart.moc:226 #16 0xb690cb5d in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #17 0xb6c43cde in QSignal::signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #18 0xb6928c27 in QSignal::activate () from /usr/lib/qt3/lib/libqt-mt.so.3 #19 0xb692ffe3 in QSingleShotTimer::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #20 0xb68adc47 in QApplication::internalNotify () from /usr/lib/qt3/lib/libqt-mt.so.3 #21 0xb68aea11 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3 #22 0xb6fe08e3 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4 #23 0xb68a2dd5 in QEventLoop::activateTimers () from /usr/lib/qt3/lib/libqt-mt.so.3 #24 0xb685d710 in QEventLoop::processEvents () from /usr/lib/qt3/lib/libqt-mt.so.3 #25 0xb68c4a78 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3 #26 0xb68c490e in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #27 0xb68ad7ff in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #28 0x08072e7b in main (argc=135036396, argv=0x80c7e28) at /home/jan/Dev/kde35/kdenetwork/0.12/kopete/kopete/main.cpp:107
This crash report is at least 3 years old and there were no further comments or status updates since then. Therefore we believe that this crash is already fixed in recent KDE 4 versions or the backtrace is no longer applicable to the current KDE 4 sources. If the crash still happens with a recent KDE version (4.10.5 or 4.11), 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 CONFIRMED)
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!
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!