Version: (using KDE 4.3.0) Installed from: Ubuntu Packages I have several XMPP/Jabber servers that are dualstacked. Ignoring the default system policy to use IPv6 over IPv4 Kopete connects to the servers using IPv4.
KDE 4.3.1 on Ubuntu Karmic btw, kopete 4:4.3.1-0ubuntu1 (0.70.90)
I confirm this bug, KDE 4.3.2 on Ubuntu Karmic Koala, Kopete Version 0.80.2 (package kopete 4:4.3.2-0ubuntu4). It is also worth noting that the file transfer port 8010 should also be IPv6; doing so will greatly enhance its utility, since it will avoid NAT issues.
Same problem here with 4.4.1 r225 on OpenSUSE 11.2 (x86) with KDE:Factory:Desktop.
I confirm this bug on Kubuntu 10.04 with additional KDE SC 4.4.4 packages. I have an account at jabber.ipv6-world.net, if I remove the IPv4 address from my client Kopete doesn't even seem to try to connect via IPv6.
Same here on Ubuntu 10.10 (Kopete Version 1.0.80; KDE 4.5.1). with tcpdump there is no IPv6-traffic (the SRV-record gets looked up "_xmpp-client._tcp.draugr.de.", but the AAAA-record is not used).
*** This bug has been confirmed by popular vote. ***
I can also confirm it on Kopete 1.0.80 (KDE 4.5.3) on Gentoo/MIPS, and on Gentoo/AMD64. In my case, I'm using my netbook (Yeeloong) from my workplace via IPv6 tunnel, and my home desktop to access a XMPP server that resides on my home network (atomic-im.yi.org). Between my desktop and the XMPP server, there is no NAT, both machines are connected to the same Ethernet segment. Between the netbook and the XMPP server, there's only my workplace's NAT via IPv4, or the tunnel to the AARNet tunnel broker via IPv6. IPv6 *used* to work back in KDE3 days. I think I still have KDE 4.2 still installed in a chroot on this netbook, I can give that a try and see if that connects.
Created attachment 58238 [details] Screenshot of server console, showing successful IPv6 connectivity in Kopete 0.70.2 This is a screen-shot of the management interface for my XMPP server (which I have tunneled via SSH). As seen from the IP addresses, the desktop (with KDE 4.5 or 4.6, not sure which) and my netbook (with KDE 4.5) have connected via IPv4. The chrooted instance of Kopete on my netbook (KDE 4.2) has connected via IPv6.
IPv6 testing day is imminent now, don't KDE devs think this is kind of important ? or is it there-is-not-too-much-users-of-IPv6-which-means-not-too-much-to-complain mentality in action ? this is why IPv6-by-default in Dual Stack is _not a recommendation_ but a policy - to avoid such near sightedness and prevent worsening of transition problems.
(In reply to comment #9) > IPv6 testing day is imminent now, don't KDE devs think this is kind of > important ? Perhaps as a useful datapoint, is someone able to force modern Kopete to connect via IPv6 either by removing the route via IPv4, or connecting to a XMPP server with no A record in DNS? > this is why IPv6-by-default in Dual Stack is _not a > recommendation_ but a policy - to avoid such near sightedness and prevent > worsening of transition problems. The other prospect to consider is that perhaps there's more focus on moving to an IM based on Telepathy. I'm currently monitoring that list and I plan to give that a try at some point to see if it proves better than the current monolithic approach.
I found this svn revision which disabling IPv6 support in jabber protocol: http://websvn.kde.org/?view=revision&revision=888259
Kopete has updated XMPP libiris library, so please test if this problem is fixed now.
no responce since last comment, closing as fixed.