Version: 0.12.4 (using KDE KDE 3.5.6) Installed from: Ubuntu Packages OS: Linux I am using Jabber, ICQ and MSN. And since today (I did not change anything in the settings, neither yesterday nor today) it crashes every now and then, but I could not find out what's causing this. I could try to run wireshark and check if it's coming from the outside? Crash Output: (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1241044592 (LWP 10824)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #6 0xb6111597 in strstr () from /lib/tls/i686/cmov/libc.so.6 #7 0xb5a430f9 in otrl_proto_message_type (message=0x0) at proto.c:321 #8 0xb5e5f7f5 in OtrlChatInterface::shouldDiscard () from /usr/lib/libkotr.so.0 #9 0xb5a588f0 in OtrMessageHandler::handleMessage () from /usr/lib/kde3/kopete_otr.so #10 0xb7eaf55c in Kopete::MessageHandler::handleMessageInternal () from /usr/lib/libkopete.so.1 #11 0xb7eb30ee in Kopete::ProcessMessageTask::slotStart () from /usr/lib/libkopete.so.1 #12 0xb7eb8458 in Kopete::ProcessMessageTask::qt_invoke () from /usr/lib/libkopete.so.1 #13 0xb68fc88b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #14 0xb6c88ae0 in QSignal::signal () from /usr/lib/libqt-mt.so.3 #15 0xb691c81e in QSignal::activate () from /usr/lib/libqt-mt.so.3 #16 0xb6924234 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3 #17 0xb6893a60 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #18 0xb689588f in QApplication::notify () from /usr/lib/libqt-mt.so.3 #19 0xb7057ce2 in KApplication::notify () from /usr/lib/libkdecore.so.4 #20 0xb68261e9 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3 #21 0xb68864ab in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3 #22 0xb683ad25 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #23 0xb68ae136 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #24 0xb68adf46 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #25 0xb6895609 in QApplication::exec () from /usr/lib/libqt-mt.so.3 #26 0x0807feec in ?? () #27 0xbfe5d864 in ?? () #28 0xbfe5d85c in ?? () #29 0xbfe5d854 in ?? () #30 0x00000000 in ?? ()
This looks like a problem in the OTR plugin which the Kopete developers don't officially support. You should contact the plugin's author and report the problem to him.
Oops :) Thanks though, will forward this to the OTR-guys.