Bug 112373

Summary: right clicking on icq protocol icon and changing it to offline when it's connecting crashes kopete
Product: [Unmaintained] kopete Reporter: Iuri Fiedoruk <protomank>
Component: ICQ and AIM PluginsAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: crash CC: patrick.trettenbrein
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Iuri Fiedoruk 2005-09-10 16:47:46 UTC
Version:           built from svn 08 sept 2005 (using KDE KDE 3.4.2)
Installed from:    SuSE RPMs

Kopete have problems to make ICQ protocol to connect on start. It just keeps conecting forever. A solution is to change it to offline and then online, the problem is that I get a crash when doing it:

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1105372288 (LWP 6133)]
[KCrash handler]
#7  0x42bb5276 in Client::deleteStaticTasks ()
   from /opt/kde3/lib/libkopete_oscar.so.2
#8  0x42bbbe5f in Client::close () from /opt/kde3/lib/libkopete_oscar.so.2
#9  0x42ba773a in OscarAccount::logOff ()
   from /opt/kde3/lib/libkopete_oscar.so.2
#10 0x42ba8a8e in OscarAccount::disconnect ()
   from /opt/kde3/lib/libkopete_oscar.so.2
#11 0x42b2ce69 in ICQAccount::setPresenceTarget ()
   from /opt/kde3/lib/kde3/kopete_icq.so
#12 0x42b2d0d1 in ICQAccount::setPresenceType ()
   from /opt/kde3/lib/kde3/kopete_icq.so
#13 0x42b2dd75 in ICQAccount::setOnlineStatus ()
   from /opt/kde3/lib/kde3/kopete_icq.so
#14 0x40108658 in Kopete::Account::qt_invoke ()
   from /opt/kde3/lib/libkopete.so.1
#15 0x4012892e in Kopete::PasswordedAccount::qt_invoke ()
   from /opt/kde3/lib/libkopete.so.1
#16 0x42ba8b1c in OscarAccount::qt_invoke ()
   from /opt/kde3/lib/libkopete_oscar.so.2
#17 0x42b2de68 in ICQAccount::qt_invoke ()
   from /opt/kde3/lib/kde3/kopete_icq.so
#18 0x413ea20e in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0x400c262c in Kopete::OnlineStatusAction::activated ()
   from /opt/kde3/lib/libkopete.so.1
#20 0x400c26f0 in Kopete::OnlineStatusAction::slotActivated ()
   from /opt/kde3/lib/libkopete.so.1
#21 0x40daae2d in KAction::slotPopupActivated ()
   from /opt/kde3/lib/libkdeui.so.4
#22 0x40dab00d in KAction::qt_invoke () from /opt/kde3/lib/libkdeui.so.4
#23 0x400c2581 in Kopete::OnlineStatusAction::qt_invoke ()
   from /opt/kde3/lib/libkopete.so.1
#24 0x413ea20e in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0x4173c122 in QSignal::signal () from /usr/lib/qt3/lib/libqt-mt.so.3
#26 0x41407763 in QSignal::activate () from /usr/lib/qt3/lib/libqt-mt.so.3
#27 0x414fab88 in QPopupMenu::mouseReleaseEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#28 0x40dcb591 in KPopupMenu::mouseReleaseEvent ()
   from /opt/kde3/lib/libkdeui.so.4
#29 0x414207f5 in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#30 0x41387a5f in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#31 0x41389e06 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#32 0x41012971 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#33 0x4132513b in QETWidget::translateMouseEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#34 0x41323d76 in QApplication::x11ProcessEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#35 0x413349a8 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#36 0x4139f9f1 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#37 0x4139f836 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#38 0x413894ef in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#39 0x0806db8c in main ()

There are two solutions for this: make icq connect at start as msn and jabber does, or fix the crash ;)
Comment 1 Matt Rogers 2005-12-13 05:44:45 UTC
bug 115772 has a better backtrace. marking this one as duplicate

*** This bug has been marked as a duplicate of 115772 ***
Comment 2 Jan Ritzerfeld 2005-12-31 13:11:02 UTC
*** Bug 119296 has been marked as a duplicate of this bug. ***