Version: 0.10.3 (using KDE KDE 3.4.2) Installed from: Mandriva RPMs OS: Linux Mandriva 2006 kopete-3.4.2-16mdk bug 199139: http://qa.mandriva.com/show_bug.cgi?id=19939 Qt: 3.3.4 KDE: 3.4.2 Kopete: 0.10.3 I tried to configure kopete to connect to Freenode IRC network. The response from the server is: (01:52:17) # Connecting to irc.debian.org... (01:52:17) # NOTICE from AUTH: *** Looking up your hostname... (01:52:17) # NOTICE from AUTH: *** Found your hostname, welcome back (01:52:17) # NOTICE from AUTH: *** Checking ident (01:52:17) # NOTICE from AUTH: *** No identd (auth) response (01:52:38) # You are now marked as Online. (01:52:38) # You are now marked as Offline. (01:52:38) # You are now marked as Offline. (01:52:38) # You are now marked as Offline. (01:52:38) # You are now marked as Offline. If I try for a second time, the error is: (01:54:56) # Connecting to irc.debian.org... (01:54:56) # NOTICE from AUTH: *** Looking up your hostname... (01:54:56) # NOTICE from AUTH: *** Found your hostname, welcome back (01:54:56) # NOTICE from AUTH: *** Checking ident (01:54:56) # NOTICE from AUTH: *** No identd (auth) response (01:54:56) # :brown.freenode.net 461 * USER :Not enough parameters (01:55:16) # You are now marked as Online. (01:55:16) # You are now marked as Offline. (01:55:16) # You are now marked as Offline. (01:55:16) # You are now marked as Offline. (01:55:16) # You are now marked as Offline.
Works fine here, but I have an identd server running. Identd is not something Kopete can or will ever do. Can you try upgrading to Kopete 0.11?
Unfortunately, that is not an option for me. Excuse me for that but I have only one computer available and that is the highest version of Kopete available on the stable repositories of Mandriva. Installing an unstable Kopete package would require to install the whole unstable KDE environment. I hope you can undestand my situation and sorry for the inconvenience. Thanks for your interest on the problem.
Mandriva ships with pidentd, why don't you install that?
See Bug 102458 for the 461 error: set a real name.
Yeah, that allows me to connect but it is kind of a workaround, isn't it?
No it's the server fault not allowing to have empty real name, while the RFC say it can be any string. No it's the server fault not allowing to have empty real name, while the RFC say it can be any string.<br><br>
*** Bug 102458 has been marked as a duplicate of this bug. ***
I cannot reproduce and this is so old...