Version: 0.12 beta2 (using KDE KDE 3.5.2) Installed from: Gentoo Packages kopete doesn't recognize my icq-transport (and doesn't add it as an account). jabber-server is ejabberd 1.0 icq transport is pyicq-t 0.7a please tell me how to provide valuable debug information. thanks
First, run kopete from konsole and paste as much output as possible. Second, are you registered with the transport? Kopete won't pick it up unless you are.
I have the same problem with sms transport. What is more any contact is shown online (see my bug #129059). For me kopete doesn't show any output in konsole.
Can i please have the debug output ? Also, please give me a server i could use to test.
I need more info. If the ICQ server doesn't suppoer Service discovery (jep-0030) or does not identify itslef as a gatway according to the jep-0030 , it will not work. Could i have the debug output please ?
I need more information
I see this too with wildfire and PyICQt/MSNt. I had added the transports in another program. When running kopete after that it does not recognise the transports, i.e. no extra account icon in the status-bar. They do work though. After a transport throws an error, e.g.: "Failed to connect to MSN servers: [Failure instance: Traceback (failure with no frames): exceptions.Exception: Timeout ]" the transport is recognised. My first guess is that kopete just forgets to ask the contact (transport) what category it belongs to. I am not sure if kopete should ask all contacts or wait for some trigger, e.g. a JID without an @ or if it gets asked for disco, to ask back: XML IN: <iq from="icq.jabber.rwth-aachen.de" <query xmlns="http://jabber.org/protocol/disco#info"/> </iq> If it would ask the relevant contact: XML OUT: <iq type='get' from='ssssssssss@jabber.ddddddd.aa' to='icq.jabber.ssssssssss.aa' id='info1'> <query xmlns='http://jabber.org/protocol/disco#info'/> </iq> It would get an answer which clearly states that the contact is a gateway. XML IN: <iq from="icq.jabber.sssssssssss.aa" type="result" to="sssssssssssss@jabber.sssssssssss.aa/Kopete" id="info1" > <query xmlns="http://jabber.org/protocol/disco#info"> <identity category="gateway" type="icq" name="ICQ Transport" /> <feature var="http://jabber.org/protocol/disco" /> <feature var="http://jabber.org/protocol/commands" /> <feature var="jabber:iq:register" /> <feature var="jabber:iq:last" /> <feature var="jabber:iq:gateway" /> <feature var="jabber:iq:version" /> <feature var="jabber:iq:time" /> <feature var="vcard-temp" /> </query> </iq> Another possible trigger for asking could be a message from a node: XML IN: <presence from="ssssssssssss%sss.aa <c xmlns="http://jabber.org/protocol/caps" node="http://msn-transport.jabberstudio.org/protocol/caps" ver="0.11.2-dev" /> </presence>
Does kopete ask for available services when connecting to the Jabber-server? <iq to="jabber.aaaaaaa.ss" type="get" id="p83"> <query xmlns="http://jabber.org/protocol/disco#items" /> </iq> Would supply a list with JIDs that should be asked for their category. <iq type="result" id="p83" from="jabber.sssssssss.aa" to="sssssssssssss@jabber.sssssssss.aa/xyz"> <query xmlns="http://jabber.org/protocol/disco#items"> . . . <item jid="msn.jabber.sssssssss.aa" name="MSN Transport"/> <item jid="aim.jabber.ssssssss.aa" name="AIM Transport"/> <item jid="icq.jabber.ssssssss.aa" name="ICQ Transport"/> </query> </iq> Maybe I missed it in kopete's output, but I think that it does not automatically ask those JIDs on every connect to pick up transports that have been set-up with another program.
i am not exactly sure why this bugs status is set to WORKSFORME (by me?) because, actually it still doesn't work. now tested with 0.12.2. and other reporters seem to have the same issues, so i am reopening.
I can confirm that with kopete 0.50.80 from Kubuntu packages. I tried two different ways of adding a msn transport from the same jabber-server: 1.) Kopete's service discovery correctly showed me the msn transport and i could register with it. Kopete displayed a message that this was succesfull and i received the regular authorization request from the transport and authorized it. 2.) I registered with the msn transport using psi. In both cases, the transport was shown in psi but not in kopete.
Can you still reproduce this in KDE 4.2 or later if yes could you give me address to server were I can reproduce this?
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.
Dear user, unfortunately Kopete is no longer maintained. Please migrate to another solution, e.g. for Jabber a possibility is Kaidan, for Matrix a candidate is NeoChat.