Version: 0.11.93 (0.12 Beta 2) (using KDE 3.5.2, Debian Package 4:3.5.2-1 (testing/unstable)) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.15.6 Hi, I am trying to register for ICQ transport and I have been unsuccessful so far. I am attaching log of stdout/stderr from kopete 0.12.beta2 when I tried to register with different jabber servers. Either (with jabber.cz) I got registered on couple of attempts, but resulting transport in kopete was not authorized (i.e., there was a exclamation mark in the status bar of kopete) and I would have to re-register all my ICQ contacts (who are getting already quite angry with me and Jabber :-)). So, I tried another servers (amessage.info, ursine.ca, swissjabber.ch) but always the result was the same -- I get list of transports on the server, but both Browse and Register buttons are greyed out for all transports, so I cannot do anything. When registering to either of these servers with Psi, I have no problem, except that in kopete I get message "You cannot see each others status", so it practically useless. Any ideas, what's going wrong, please?
Created attachment 15424 [details] stderr/stdout of kopete session
I think you need to ask the authorisation for all contact, there is no way to work around that i think. that's due to current limitaiton of the jabber protocol. Gateway are not allowed to change themself the authorisations Anyway, even if your contact are marked as unauthorised, all should work fine. 0) is that the latest svn ? i fixed a bug with the icq gateway, but i don't remember when (probably two week ago) 1) I see you have the icq account connected in Kopete, please make sure to disconnect it. 2) It seems the cpnnection status plugin try to disconnect all accounts. It maybe believe the network is down because the icq accounts get disconnected. please unload that plugin Also i noticed a problem that the icq gateway is trying to push a /registered ressource on the roster. Which is not XMPP compilant
0) no, beta2 -- will be there beta3? 1) now, it was disconnected, and now it is removed 2) I have no plugin downloaded, and the situation is the same Thanks, Matej
Apparently icq.com has been down since yesterday, so that may be the problem -- I will recheck when ICQ will be up. Matej
OK, ICQ is up and I was able to have perfectly working ICQ transport with psi. However, even when I removed all kopete information I have on my computer, and tried to start fresh, kopete did not recognize, that I have ICQ transport registered -- it found MSN and AIM transports, but not ICQ. Any ideas? For now I have to switch to psi (although I would prefer kopete). Matej
Created attachment 15462 [details] stderr/stdout of kopete session I removed ~/.kde/share/apps/kopete, ~/.kde/share/config/kopete*, and ~/.kde/share/config/session/kopete* and tried to start from scratch. However, ICQ transport (although present and working with psi) didn't show up in kopete. Individual contacts are there, but not the lightbulb on the status line. Moreover, other transports (AIM and MSN) are not authorized (although, they are in psi). Using still beta2
Correction, after restart of kopete, MSN and AIM transports are registered and authorized, but ICQ transport is still nowhere to be found.
For some inexplicable reason, I had ICQ transport twice in my roster. Could it make kopete behave like it did? Can anybody confirm that he has working all fourt big transports working?
about the last sentence of comment 2 -- can you tell me please where standards say that gateway should not have a resource? Thanks.
Just to confirm, that I have yesterday compiled 0.12 from SVN and the problem persists -- ICQ transport is still not registered. Concerning your comment about resources in gateway -- icq.jabber.cz is running JIT which is not maintained currently, so it is possible that it is doing something wrong, but unfortunately, I don't see much way how to fix it.
SVN commit 540794 by ogoffart: Accept the fact that gateway may contain ressource, that's the case of the ICQ JIT gateway which contains /registered BUG: Bug 124776 WARNING: after this commit, you need to remove your gateway from kopete, or strange accounts will appears. The config file format has changed. May also help to fix bug 126144: empty contact added on every connection to accout . please have a test CCBUG: 126144 M +6 -6 jabberaccount.cpp M +5 -5 jabbercontact.cpp M +2 -3 jabberprotocol.cpp M +63 -38 jabbertransport.cpp M +16 -5 jabbertransport.h