Bug 102458 - irc error connection problem
Summary: irc error connection problem
Status: RESOLVED DUPLICATE of bug 120042
Alias: None
Product: kopete
Classification: Unmaintained
Component: IRC Plugin (other bugs)
Version First Reported In: unspecified
Platform: openSUSE Linux
: LO normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
: 102909 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-03-25 13:49 UTC by Nobuteru
Modified: 2006-06-14 01:06 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Screenshot of error (181.07 KB, application/octet-stream)
2005-03-27 18:28 UTC, Nobuteru
Details
server ok (241.76 KB, application/octet-stream)
2005-03-27 18:29 UTC, Nobuteru
Details
Screenshot of error (181.07 KB, image/jpeg)
2005-03-27 18:42 UTC, Nobuteru
Details
server ok (241.76 KB, image/jpeg)
2005-03-27 18:43 UTC, Nobuteru
Details
Configure error (10.62 KB, text/plain)
2005-03-28 12:51 UTC, Nobuteru
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nobuteru 2005-03-25 13:49:56 UTC
Version:            (using KDE KDE 3.4.0)
Installed from:    SuSE RPMs
OS:                Linux

Hi all,
what did you change in kopete 0.10 IRC module from the old previous in kopete 0.9.2?

the IRC connection module worked very fine, after the upgrage to kde 3.4 the new kopete don't want to connect to IRC server.

i get this errors :

"conneting to fastweb.azzurra.it"
"now you are online"
"now you are offline"
"conneting to fastweb.azzurra.it"
"KIRC error, interpreting error"

and it stopped to connect to the server.

i checked that the irc server is ok, because i tryed Ksirc, and it connect fine ..., i also checked you bugs list and faq, but i find no help to solve my problem.

when i used the old kopete 0.9.2 i had a problem about the continue blinking of the IRC icon, but i changed the socket timeout (to 90 seconds) from the KDE control pannel, and it worked fine till kde 3.4...


My linux bos is a suse 9.2, upgraded from the supplementary package in the ftp site ftp.leo.org...

thanks all

bye bye
Comment 1 Michel Hermier 2005-03-25 15:10:12 UTC
Could you paste the console log? (use kdebugdialog if necessary)
The socket timeout trick can't be used anymore, and should have nothing to do with the bug.
Comment 2 Nobuteru 2005-03-25 20:59:01 UTC
Hello,
i am sorry but maybe i don't understand how to use kdebugdialog.

I did (but i am not sure that is the right way):
I opened a shell, i wrote "kdedialog",i  selected all the voices with kopete and irc from the window and i clicked on ok, and after from the shell i started kopete, but i didn't get any debug message.

I also did:
I opened a shell, i wrote "kdedialog -fullmode", i selected a voice with kopete and irc (there are only 2 voices, and i tryed with both) and i clicked on ok, and after from the shell i started kopete, but i didn't get any debug message.

i searched kdedebugdialog on google, but i didn't find any help

when i "tell" to kopete to go online with IRC, i always open the server window, and i see the errors, that i reported, if you want i can cut and paste them, but are in italian...

any idea how i can't you to show my problem/bug?
Comment 3 Michel Hermier 2005-03-25 21:10:34 UTC
I forgot to say:
You must have kopete configured with "--enable-debug=full" when compiled.
You must look into the console for the debug output.

So it's normal you don't see anything in kopete.
In kdebugdialog try to only select the kopete irc debug channels. The ouput 
will be huge and not very usefull.
Comment 4 Nobuteru 2005-03-25 21:31:28 UTC
I don't have kopete compiled from myself, i upgraded my suse linux box from kde 3.3.2 to 3.4 using YAST and the rpms on ftp.leo.org

So to help you, i need to download kopete from cvs and compile it with the full debug parameter?
Comment 5 Michel Hermier 2005-03-25 23:35:14 UTC
You should, but there are problems doing this with the rpm system. Maybe some 
rpm user could help here?
Comment 6 Nobuteru 2005-03-27 18:28:23 UTC
Created attachment 10369 [details]
Screenshot of error
Comment 7 Nobuteru 2005-03-27 18:29:03 UTC
Created attachment 10370 [details]
server ok
Comment 8 Nobuteru 2005-03-27 18:35:32 UTC
Hi, 
i posted the two screenshot, the first with the errors that i get on connecting, (i am sorry, they are write in italian, the translation is easy with a normal web translator, or you can read my previous post)

The second screenshot is a demo that show that the server is ok and from another kde irc client it work fine.

I tryed to compile Kopete from source, i followed the instruction from kopete web site to donwload and compile it from cvs, but i got this error :

checking for gcc... gcc
checking for C compiler default output file name... configure: error: C compiler cannot create executables
See `config.log' for more details.

i can post the log if you want.

My suse box is a suse 9.2 professional and the gcc is the version :

Reading specs from /usr/lib/gcc-lib/i586-suse-linux/3.3.4/specs
Configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --enable-languages=c,c++,f77,objc,java,ada --disable-checking --libdir=/usr/lib --enable-libgcj --with-gxx-include-dir=/usr/include/g++ --with-slibdir=/lib --with-system-zlib --enable-shared --enable-__cxa_atexit i586-suse-linux
Thread model: posix
gcc version 3.3.4 (pre 3.3.5 20040809)


Any idea?
i can compile it with full debug, and send the bugs report, if i succeed ti compile it...

i also try to dl the source from kopete web site, but the links are broken..

sorry to not be more usefull
Comment 9 Nobuteru 2005-03-27 18:42:12 UTC
Created attachment 10371 [details]
Screenshot of error
Comment 10 Nobuteru 2005-03-27 18:43:02 UTC
Created attachment 10372 [details]
server ok
Comment 11 Jason Keirstead 2005-03-27 21:26:26 UTC
I am getting this reply from the server, it seems to be rejecting our (perfectly valid) USER reply with an empty real name.

kopete (irc - raw protocol): (19 bytes) >> USER jasonk 0 * :
kopete (irc - raw protocol): (18 bytes) >> NICK brunes_test
kopete (irc - raw protocol): << :libero.azzurra.org 461  USER :Not enough parameters

Try setting a 'Real Name' field. When I do that, I get this different error, which usually means the network is restricted to certain IP ranges:

kopete (irc - raw protocol): << ERROR :Closing Link: 0.0.0.0 (You are not authorized to use this server, visit www.azzurra.org/access.html for more info)
Comment 12 Nobuteru 2005-03-27 22:49:27 UTC
hi,
it's normal because the server fastweb.azzurra.org is for the user of the fastweb network, i setted the real name and it work very very fine!

I am so sorry, it's not a bug, but a configuration error....

thanks a lot
Comment 13 Jason Keirstead 2005-03-28 03:33:07 UTC
I am going to re-open this because I still need to investigate what the error messages were not being properly propegated to the chat window for this server.
Comment 14 Nobuteru 2005-03-28 12:51:13 UTC
Created attachment 10386 [details]
Configure error
Comment 15 Nobuteru 2005-03-28 12:52:06 UTC
Ok, but i can't help you, because my linux box can't compile kopete from source, i think that is a gcc problem...

sorry
Comment 16 Thiago Macieira 2005-03-28 12:55:34 UTC
Yes it is:

configure:2823: gcc     conftest.c  >&5
gcc: invalid specification!  Bug in cc
Comment 17 Nobuteru 2005-03-28 13:21:33 UTC
hmmm, excuse me, but i am not a linux expert, i have to change my gcc compiler?
Comment 18 Tommi Rantala 2005-04-15 22:00:17 UTC
The problem is in the server response ...

:libero.azzurra.org 461  USER :Not enough parameters 

... where there is a double space after 461.


The IRC-plugin seems to follow RFC 2812, which restricts all the parameters to have maximum of one space between each other:

"2.3 Messages
   [...]
   Each IRC message may consist of up to three main parts: the prefix
   (OPTIONAL), the command, and the command parameters (maximum of
   fifteen (15)).  The prefix, command, and all parameters are separated
   by one ASCII space character (0x20) each."


The original RFC 1459 is however more relaxed about this:

"2.3 Messages
   [...] The prefix, command, and all parameters are
   separated by one (or more) ASCII space character(s) (0x20)."


Anyways I think this can be fixed by modifying the regexps defined in kopete/protocols/irc/libkirc/kircmessage.cpp
Comment 19 Michel Hermier 2005-04-15 22:54:36 UTC
The problem is in kopete but also in the server not allowing you to have an 
empty real user name.
Comment 20 Matt Rogers 2005-10-05 23:35:59 UTC
*** Bug 102909 has been marked as a duplicate of this bug. ***
Comment 21 Michel Hermier 2006-06-14 01:06:25 UTC

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