Version: 0.70.90 (using KDE 4.2.96) OS: Linux Installed from: Ubuntu Packages I've a internal ejabberd on debian etch. Since I tried the KDE 4.3 packages from http://www.kubuntu.org/node/89 I cannot connect to this jabber server anymore (ICQ for example works). other users have no problems with the jabber server. when connecting to the jabber server I get the message: Connection problem with Jabber server ... There was a connection error: Remote closed the connection. I started kopete from the cmd line but it doesn't give output when this happens.
Did you try recreating the account ?
(In reply to comment #1) > Did you try recreating the account ? I just tried that but it didn't help (I recreated the account in kopete, not the jabber account at the jabber server). I have configured group chats with auto-join as described in http://userbase.kde.org/Kopete_Jabber_Muc maybe this causes the problem.
OS: Fedora 10 Qt: 4.5.2 KDE: 4.3.00 (KDE 4.3.0) Kopete: 0.70.90 We have the same issue. Kopete can not connect to the ejabberd (in the same local network) after the upgrade to the latest stable KDE version from Fedora repository. The latest PSI version has the same issue. PSI also based on the QT framework. So the issue my belong to the QT. I've used the tcpdump on the serverside for check the connections and found out following: 1. Kopete (or PSI) does not try to connect at all. 2. If I try to use secure connection throw port 5223 the issue is same. 3. Pidgin has no any problem with connect to the ejabber.
Also Kopete connects the GTalk without any trouble...
I can connect to the local ejabber server using IP address instead of domain name from local DNS server. May be the issue is connected to a Qt resolver...
I experience these symptoms, and the problem is always related to a CNAME lookup. talk.mydomain.com CNAME talk.google.com CNAME talk.l.google.com A ip-address. Using talk.mydomain or talk.google.com will not work, but using talk.l.google.com or the IP address works fine. Are your internal hostnames also CNAMEs?
> Are your internal hostnames also CNAMEs? Yes, I use CNAME for local jabber server. I've tried to connect using A-entry but failed to connect. I still able to connect only using ip-address :(
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!