Subject: Re: [Kopete-devel]  New: Oscar & ICQ plugin not connecting

On Wednesday 12 February 2003 08:08, Chris Smith wrote:
> QServerSocket: failed to bind or listen to the socket
> 
> Which makes me think it may have more to do with my system than Kopete, but 
> I thought you guys could help.
> 
> When I try to connect using ICQ, I get this on stdout:
> 
> kopete: WARNING: 19:45:16 [WRN] Connection closed
> 
> Is this anything to do with kopete, or is something screwey with my system?

What glibc version do you have? This sounds like bug 53072 to me, actually.

Thanks for the reply Martijn, 
 
I had a look at bug 53072 when i submitted this bug (bugzilla's smart submit system) and I 
decided that my problem was decidedly different. As even GAIM doesn't connect to 
AIM/ICQ either! 
 
Anyway, I use glibc version 2.3.1 
 
Hope you can help me, 
Chris. 
 
 

Subject: Re: [Kopete-devel]  Oscar & ICQ plugin not connecting

On Wednesday 12 February 2003 10:38, Chris Smith wrote:
> Hope you can help me, 

Actually, I'm afraid I can't. Your setup is so much different from mine that I 
cannot really reproduce. The symptoms sounded very familiar and your glibc 
version is the one of which some sub-releases caused problems, but if that's 
not it, I have no idea :(

if gaim won't connect then it's not a kopete problem but a  problem with your system, 
thus closed. 

Well, I reopened the bug because KDE's AIM client (Kit) connects to the server with my 
user/pass fine. So it's not really to do with my system. GAIM has always been weird on my 
machine, but I'll try it again. 
 
LICQ also connects to its server fine. Yet Kopete still packs a sad. 
 
Thanks, 
Chris 

More news: Now when i run kopete and try to connect to my AIM server, this gets 
spammed to stderr: 
 
"select: Bad file descriptor" 
 
I ended up with 965MB ~/.xsession-errors file, and is displayed to console when I run it 
from the command line. 
 
Does this help? 

Could you try updating glibc to a newer version? This helped for all other people 
that had this problem. 
 
Alternatively, ask TrollTech for a workaround in QDns (if possible, this really seems 
to be a very weird problem in recent glibc's resolver code). 
 
A last option is to remove the #undef HAVE_KEXTSOCK_H in client.{h,cpp} as 
suggested in http://bugs.kde.org/show_bug.cgi?id=53072, but since no released 
distro uses this glibc (Debian and Mandrake at least already updated their 
packages to a newer patchlevel that doesn't have the problem. I don't think we 
should remove this in CVS yet. 
 
As for why you get this with some code, but not all: it depends on how the 
resolver lib is used. QDns does it in a way that triggers the bug, 
KExtendedSocket's synchronous (blocking) lookup as used in e.g. MSN does not. 
Plain libc may or may not trigger it as well, etc. Not too much we can (or will) do 
about it. 
 
Martijn 
 

There, GAIM works perfectly fine with ICQ, AIM and MSN. 
 
About GLibc, I'm using the latest version available for my distro (gentoo) and normally they 
are pretty bleeding edge, so whatever fixes made it in I'm pretty sure I have :\ 

Subject: Re: [Kopete-devel]  Oscar & ICQ plugin not connecting

On Wednesday 19 February 2003 08:18, Chris Smith wrote:
> There, GAIM works perfectly fine with ICQ, AIM and MSN. 
>  
> About GLibc, I'm using the latest version available for my distro (gentoo)
> and normally they are pretty bleeding edge, so whatever fixes made it in I'm
> pretty sure I have :\

Then please file a bug against Qt, since it's QDns that chokes on glibc 2.3.1 
or against kdelibs/KExtendedSocket.

We use the socket code from Qt and kdelibs, so besides adding ugly workarounds 
(if possible) we for sure can't fix the real cause of the problem.

(btw: the workaround that I mentioned for ICQ didn't work either?)

Okay, I will file a bug with Qt about the problem. 
 
I understand you use the socket code from kdelibs, but wouldn't Kit (the KDE AOL client) 
use that exact same code? Kit connects fine on my machine. 
 
And no, the ICQ fix you mentioned didn't work. 
 
Thanks for all your help so far Martijn, It is greatly appreciated. 
Chris. 

Subject: Re: [Kopete-devel]  Oscar & ICQ plugin not connecting

On Thursday 20 February 2003 01:23, Chris Smith wrote:
> And no, the ICQ fix you mentioned didn't work. 

It did not? That's strange. It worked for the Mandrake and Debian people with 
a buggy glibc.

I'm beginning to believe that your problem is different then, but *what* could 
it be?

Does Kopete 0.6.1a (the one we released last night, not the non-A version from 
2 days ago :) fix the issues for you?

I tried Kopete 0.6.1a and that didn't fix the problem :( 
 
I tried removing all my kopete config files, and moving my contact list etc... but still the same 
error. 
 
Perhaps I'll try recompiling QT against my latest Glibc? I'll give it a shot. 
 
Thanks, 
Chris. 

Nope, none of that worked. 
 
I guess Kopete is going to be my new MSN client :P 
 
Thanks for all your help Martijn, If I figure something out, I'll get in touch with you. 
 
Thanks again, 
Chris. 

Subject: Re: [Kopete-devel]  Oscar & ICQ plugin not connecting

Do you have any debug output on the console while running Kopete from there 
that might be useful btw?

When I start kopete, and try to connect to AIM, I get this: 
 
chris@chris icq_new $ kopete 
chris@chris icq_new $ QServerSocket: failed to bind or listen to the socket 
QServerSocket: failed to bind or listen to the socket 
QServerSocket: failed to bind or listen to the socket 
QServerSocket: failed to bind or listen to the socket 
 
Then when I try to connect to ICQ, I get this: 
 
QObject::connect: No such slot ICQServerSocket::activated() 
QObject::connect:  (sender name:   'unnamed') 
QObject::connect:  (receiver name: 'unnamed') 
 
Which is different than what I used to get. Anyway, After a while, I get this spammed 
thousands of times (puffs my log files up to over 1 Gb if I leave kopete open) or floods the 
console, depending on how I started kopete. 
 
select: Bad file descriptor 
 
Is there a special debug mode for kopete? The debug window under the AIM menu doesn't 
show anything helpful. 

> chris@chris icq_new $ QServerSocket: failed to bind or listen to the socket 
> QServerSocket: failed to bind or listen to the socket 
> QServerSocket: failed to bind or listen to the socket 
> QServerSocket: failed to bind or listen to the socket 
 
Well, there's the problem. That's definately going to cause those file descriptor 
errors. Few questions: 
 
	- What version of Gentoo? 
 
	- Do you have any kernel patches that improse extra security? 
 
	- Do you know if the Gentoo kernel is stock vanilla kernel? 
 
	- Where'd you get your Qt package? 
 
For some reason your kernel is disallowing QServerSocket to listen on a random port, 
which makes be believe this will also cause unexpected behavior. 
 
I know of many users using Kopete on Gentoo and I've never heard of such a 
problem. Do you have other systems to test with to make sure it's not an internal 
connection problem? 

Hi There, Thanks for the fresh perspective. 
 
I'm running Gentoo version 1.4, KDE 3.1 and kopete cvs now. My kernel is the WOLK 
3.8.1 kernel, with no extra security patches installed (I need that kernel, because of the 
other driver patches it has installed in it, But will compile another vanilla kernel to see if that 
fixes the problem. 
 
gentoo-sources != vanilla sources. Gentoo Sources has many performance, stability and 
feature rich patches installed on it, but I don't use it. 
 
And my QT package is straight from TrollTech, compiled from source. 
 
Thanks for the hint about the kernel, I'll scour the config tonight after work and see if there 
is anything there that jumps out at me. Any suggestions at what the option could be? 
 
Thanks for your help, 
Chris. 

OMFG. 
 
I have no idea what I did. Don't ask me, I don't know. I just started Kopete today and it 
worked. 
 
Whatever was wrong has ironed itself out. 
 
Sorry, and Thanks guys! 
Chris 

Closing Bug. 
 
Thanks!