Version: 1.0.1 (using KDE 3.5.5, Debian Package 4:3.5.5a.dfsg.1-5 (4.0)) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.19-rc6-marcus Problem: Ipv6-only irc-servers are not resolved and can only be accessed by entering the ip(v6)-address manually. A lookup for AAAA and A -records should be done and either: (correct) if we have a default ipv6-route prefer an AAAA to an A -record. (simple) if no A-record is found at all, try an AAAA-record. test-case: ipv6.furnet.org Cosmetic: Also ipv6-adresses in URL-syntax (enclosed in []) are tried to resolve as names and all ipv6-addresses are displayed without []. The absense of [] causes unreadable names like 2001:1a50:a::2:6697 for [2001:1a50:a::2] port 6697.
The Problem could be with KStreamSockets use of KResolver.
If you're in a position to try out the pre-release KDE 4 port (see Konversation website), could you please check if it works for you there?
SVN commit 1023172 by hein: * Fix a regression vs. the KDE 3 version that caused a failure to correctly parse shortened IPv6 addresses except when using RFC- 2732-style bracket notation and explicitly stating a port to connect to. BUG:198588 * Made the display of server address and port number in various connection-related chat view messages more consistent and IPv6- friendly (with the '<ip>:<port>' forward previously used, it could be hard to tell where the IP ended and the port began -- now it's '<ip> (port <port>)'). CCBUG:139071 M +7 -0 ChangeLog M +10 -8 src/connectionmanager.cpp M +7 -4 src/irc/server.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1023172
Is this still an issue for you with current versions of Konversation?
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 set the bug status 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!
Dear Bug Submitter, 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!