Bug 125703

Summary: Unable to login to IRC servers without realname field filled
Product: [Unmaintained] kopete Reporter: Giuseppe Ricupero <protocollozero>
Component: IRC PluginAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Giuseppe Ricupero 2006-04-17 00:50:49 UTC
Version:           0.10.4 (using KDE KDE 3.4.3)
Installed from:    Gentoo Packages
Compiler:          gcc-3.4.5-r1 
OS:                Linux

I was unable to login to IRC Freenode network until i have filled "Real name" field with something.
To explain better i was unable to login with these filled fields:
* nickname
* Alternative nickname
* Remember password checked
* Password field filled correctly
* Freenode network chosen under Connection tab
* Remaining fields left blank or default

I report messages received from servers (they're always the same).

*************************************************************************
Server Message log:
*************************************************************************
(00:26:03) #  NOTICE from AUTH: *** Looking up your hostname...
(00:26:03) #  NOTICE from AUTH: *** Found your hostname, welcome back
(00:26:03) #  NOTICE from AUTH: *** Checking ident
(00:26:33) #  NOTICE from AUTH: *** No identd (auth) response
(00:26:33) #  :kornbluth.freenode.net 461 * USER :Not enough parameters
(00:26:33) #  You are now marked as Online.
(00:26:34) #  You are now marked as Offline.
(00:26:34) #  You are now marked as Offline.
(00:26:34) #  You are now marked as Offline.
(00:26:34) #  You are now marked as Offline.
*************************************************************************

Affected servers (i suppose all freenode servers are involved, but i've tested only these):
irc.freenode.net:6667
irc.kde.org:6667
Comment 1 Tommi Rantala 2006-04-18 19:11:04 UTC

*** This bug has been marked as a duplicate of 105681 ***