Version: 0.9.92 (using KDE 3.3.92 (beta2), compiled sources) Compiler: gcc version 3.3.4 20040623 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6) OS: Linux (i686) release 2.6.10-gentoo-r5 This leaves me with 2 choices: drop kopete, or drop icq. It's simply not acceptable.
Do the popups show during the login process? or are they shown after that? What's the message displayed in the popups?
On Wednesday 23 February 2005 14:30, Gustavo Pichorim Boiko wrote: > Do the popups show during the login process? or are they > shown after that? After. they appear in some interval it seems, sometimes i find a whole load hidden behind other windows. (just now, 3 since a few minutes). They are modal to kopete, and thus prevents showing the kopete window by clicking the systray icon. pow, one more... > What's the message displayed in the popups? An unknown error has occurred and the connection has been closed.
Please provide debug output
The ICQ server behavior today is completelly weird. Some accounts connect without error, some can connect to one server, but not to another, and sometimes after connecting to one server, I can login to the another one :/ But, indeed, there shouldn't be more than one error dialog.
On Wednesday 23 February 2005 15:44, Gustavo Pichorim Boiko wrote: > Some accounts connect without error, some can connect to one server, but > not to another, and sometimes after connecting to one server, I can login > to the another one :/ > > But, indeed, there shouldn't be more than one error dialog. I'm not disconnected (except i close the account because it's too annoying). And it's not just today, it's since i updated last time (about a week ago).
On Wednesday 23 February 2005 15:39, Matt Rogers wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=100064 > > > > > ------- Additional Comments From mattr kde org 2005-02-23 15:39 ------- > Please provide debug output libkopete: [void Kopete::Account::slotOnlineStatusChanged(Kopete::Contact*, const Kopete::OnlineStatus&, const Kopete::OnlineStatus&)] account 99053095 changed status. was Online, is Offline ... kopete: statistics - status change for ICQProtocol:99053095:107841072 : 10 libkopete: [void Kopete::Account::slotOnlineStatusChanged(Kopete::Contact*, const Kopete::OnlineStatus&, const Kopete::OnlineStatus&)] account 99053095 changed status. was Offline, is Offline knotify: [void KDE::POFHelper::connectAmanPlay()] libkopete: [void Kopete::Account::slotOnlineStatusChanged(Kopete::Contact*, const Kopete::OnlineStatus&, const Kopete::OnlineStatus&)] account 99053095 changed status. was Offline, is Connecting QMetaObject::findSignal:ClientStream: Conflict with Stream::readyRead() libkopete: [void Kopete::Account::slotOnlineStatusChanged(Kopete::Contact*, const Kopete::OnlineStatus&, const Kopete::OnlineStatus&)] account 99053095 changed status. was Connecting, is Online libkopete: [QImage Kopete::MetaContact::photo() const] no KABC::Addressee found for ( ICQProtocol:99053095:122264266 ) [SoK]uncle in current address book This some of it.
I need all of it, from the time you open kopete, connect one icq account, till you get a popup or two or three, until you close kopete.
On Wednesday 23 February 2005 16:06, Matt Rogers wrote: > I need all of it, from the time you open kopete, connect one icq account, > till you get a popup or two or three, until you close kopete. That would require me reconfiguring kopete, reconfigureing my debug output, restarting kopete etc.. And even I can see from the clip what it does: It shows a kmessagebox when the connection is lost. Then it reconnects. That happens very often == MANY dialogs. What you'll want to do is not showing the messagebox if you are going to try to reconnect, wait till connection actually failed (for the last try if you try multiple times). Or at least define a 'don't show this again' name, so I can get rid of it for good. -anders
yes, getting debug output would require all of that. We ask our other users to do this and while inconvenient, it's the only way we get good information to troubleshoot bugs. you shouldn't get this messagebox under normal circumstances anyways, unless it's an error that i haven't accounted for. In that case, I feel its better that the user gets reconnected. However, since ICQ's servers are broken, there's really nothing I can do. If it still happens after ICQ's servers are fixed, I'll need to know so i can actually attempt to reproduce and fix the problem.
If the icq server is not available (not route to host) the massebox "An unknown eror has occurred and the connection has been closes" pop up freqently so i con only kill kopete. Better error Messeage and only one would be better.
CVS commit by mattr: Display only one error when we hit an unknown error that I don't do a good job of handling yet. You get to choose whether or not to reconnect now. BUG: 100064 CCBUG: 101626 M +1 -1 oscaraccount.cpp 1.174 M +3 -27 liboscar/client.cpp 1.13 M +0 -2 liboscar/client.h 1.12 M +5 -5 liboscar/connectionlist.cpp 1.3 --- kdenetwork/kopete/protocols/oscar/oscaraccount.cpp #1.173:1.174 @@ -248,5 +248,5 @@ void OscarAccount:: protocolError( int e if ( psError == 0 ) //zero is a generic error when i don't know what's wrong. :/ { - disconnected( Kopete::Account::ConnectionReset ); + disconnected( Kopete::Account::Manual ); } --- kdenetwork/kopete/protocols/oscar/liboscar/client.cpp #1.12:1.13 @@ -125,32 +125,8 @@ Client::~Client() //delete the connections differently than in deleteConnections() //deleteLater() seems to cause destruction order issues - QValueList<Connection*> connList = d->connections.getConnections(); - QValueList<Connection*>::iterator it = connList.begin(); - d->connections.removeAllConnections(); - while ( it != connList.end() ) - { - Connection* c = *it; - it = connList.remove( it ); - delete c; - } - delete d->ssiManager; delete d; } -void Client::deleteConnections() -{ -// kdDebug( OSCAR_RAW_DEBUG ) << k_funcinfo << "Deleting " << d->connections.count() << " connections" << endl; - QValueList<Connection*> list = d->connections.getConnections(); - QValueList<Connection*>::iterator it = list.begin(); - d->connections.removeAllConnections(); - while ( it != list.end() ) - { - Connection* c = *it; - it = list.remove( it ); - c->deleteLater(); - } -} - void Client::connectToServer( Connection *c, const QString& server, bool auth ) { @@ -184,5 +160,4 @@ void Client::close() d->active = false; // kdDebug( OSCAR_RAW_DEBUG ) << k_funcinfo << "Closing " << d->connections.count() << " connections" << endl; - deleteConnections(); //these are based on a connection. delete them. delete d->errorTask; @@ -207,4 +182,5 @@ void Client::close() // kdDebug(OSCAR_RAW_DEBUG) << k_funcinfo << "Clearing our internal SSI list" << endl; d->ssiManager->clear(); + d->connections.removeAllConnections(); } --- kdenetwork/kopete/protocols/oscar/liboscar/client.h #1.11:1.12 @@ -382,6 +382,4 @@ protected slots: private: - /** Delete the connections */ - void deleteConnections(); /** Initialize some static tasks */ --- kdenetwork/kopete/protocols/oscar/liboscar/connectionlist.cpp #1.2:1.3 @@ -35,7 +35,4 @@ ConnectionList::ConnectionList() ConnectionList::~ConnectionList() { - delete m_bosConnection; - delete m_authConnection; - delete m_iconConnection; } @@ -57,4 +54,7 @@ QValueList<Connection*> ConnectionList:: void ConnectionList::removeAllConnections() { + delete m_authConnection; + delete m_bosConnection; + delete m_iconConnection; m_bosConnection = 0; m_authConnection = 0;
CVS commit by mattr: Backport the fix for 100064 CCBUG: 100064 M +1 -1 oscaraccount.cpp 1.169.2.3 --- kdenetwork/kopete/protocols/oscar/oscaraccount.cpp #1.169.2.2:1.169.2.3 @@ -239,5 +239,5 @@ void OscarAccount:: protocolError( int e if ( psError == 0 ) //zero is a generic error when i don't know what's wrong. :/ { - disconnected( Kopete::Account::ConnectionReset ); + disconnected( Kopete::Account::Manual ); }
You need to log in before you can comment on or make changes to this bug.
KDE Bug Tracking System
KDE Bug Tracking System 