So I have a brand new KDE 4.8 install under Arch Linux (fresh install) from last night. I opted for a base install, and have cherry picked software and groups, building my KDE setup, instead of just grabbing everything all at once.

I installed Konversation and booted it. And whether I try to customize the server, or even just try and connect to FreeNode with the default settings, I get the same infinite loop:

Code: Select all

[15:40] [Info] Looking for server chat.freenode.com (port 6667)...
[15:40] [Info] Server found, connecting...
[15:40] [Info] Connected; logging in...
[15:40] [Notice] -adams.freenode.net- *** Looking up your hostname...
[15:40] [Notice] -adams.freenode.net- *** Checking Ident
[15:40] [Notice] -adams.freenode.net- *** Found your hostname
[15:40] [Notice] -adams.freenode.net- *** No Ident response
[15:40] [Error] Connection to server chat.freenode.com (port 6667) lost: Unknown error.
[15:40] [Info] Trying to reconnect to chat.freenode.com (port 6667) in 10 seconds.
[15:40] [error] Closing Link: 127.0.0.1 (Connection timed out)

I've tried Google for awhile now. I've searched through some bug reports, hunted the forums and tried tweaking various settings. No matter what I do, Konversation simple won't connect to an IRC server. Any idea what I'm missing?

try server=irc.freenode.org & port=8001
that's what works for me

google01103 wrote:try server=irc.freenode.org & port=8001
that's what works for me

Thanks for the timely suggestion. I've tried varying combinations of irc/chat.freenode.com and several port numbers to no avail. I also tried OFTC to the same end. And, to be thorough, I installed KVirc and tried that, which promptly connected using the same FreeNode server (adams.freenode.com).

So the issue is very specifically Konversation. Any idea where, if anywhere, there might be more info before logged? There's nothing in /var/log/messages.log (Arch user, for what it's worth). And the logs in my home directory (logs folder) are just showing me trying to log in.

I haven't used KDE in a while, but I'd never had issues before. And another IRC client working from the same machine makes me wonder what specifically about Konversation is preventing it from connecting.

if you had an existing ~/.kde[4] try running as a new user

Hmm, weird, I'm using konversion on arch linux too, with freenode (irc.freenode.net:8001) and it works just fine (thus probably not a general problem with arch+konversation, or freenode, or whatever).
You could try enabling "konversation" in the "kdebugdialog" program and look at the console output. Maybe it tells something interesting?

Greetings

Thanks for all the help guys. So to follow up, I tried add Konversation to kdebugdialog, and I didn't get much of anything in terminal relating to my issues. Then tonight after work, I created a new user with the intention of trying to see if something in my .kde4 folder was causing a conflict. Just before logging out, I figure what the Hell, and launch Konversation... and it works. Huh?

The only things that have changed are a)rebooting, but I did that before too, and b)disabling desktop search with Nepomuk. On a possibly unrelated note, I had Kontact freeze and wouldn't restart until after a reboot. Having disabled desktop search, Konversation and Kontact seem to be working. I haven't read too much about Nepomuk and that whole bag, but could that possible be/have been related?

While it is good to hear it is solved, I suspect this may be related:

Code: Select all

[15:40] [Error] Connection to server chat.freenode.com (port 6667) lost: Unknown error.
[15:40] [Info] Trying to reconnect to chat.freenode.com (port 6667) in 10 seconds.
[15:40] [error] Closing Link: 127.0.0.1 (Connection timed out)

Seeing a reference to 127.0.0.1 is very unusual for a freenode connection (and may have been caused by a DNS fault, or filtering)

bcooksley wrote:While it is good to hear it is solved, I suspect this may be related:

Code: Select all

[15:40] [Error] Connection to server chat.freenode.com (port 6667) lost: Unknown error.
[15:40] [Info] Trying to reconnect to chat.freenode.com (port 6667) in 10 seconds.
[15:40] [error] Closing Link: 127.0.0.1 (Connection timed out)

Seeing a reference to 127.0.0.1 is very unusual for a freenode connection (and may have been caused by a DNS fault, or filtering)

I'd say you're very right, since this morning I had to reboot and tried Konversation only to find myself in the same failing loop. I didn't notice it before, but I *think* this is only happening at work. I believe I first tried it at work, no luck, and it succeeded last night at home. So there must be something going on with my work connection that's jacking up my ability to connect.

Maybe there's some kind of firewall blocking the connection? Did you try to connect from another client (irssi or xchat, for example), or just netcat:

Code: Select all

netcat irc.freenode.net 8001
NICK somenickname
USER somerealname 0 0 somerealname

If it doesn't work there either, then it's probably related to your network connection...

Just as a note (as this has been linked in #freenode right now), sorry for replying to an old thread, but people appear to still be finding this:

Our address is chat.freenode.net on the ports 6665, 6666, 6667, 6697 (SSL only), 7000 (SSL only), 7070 (SSL only), 8000, 8001 and 8002.

It's neither .org nor .com.

Thanks, kind regards,

Fuchs