Public SourceMage Discussion List

["Jimmy Yen(顏孝杰)" <jimmy AT yen.tp>]

I seem to have found a workaround. I recompiled linux and net-tools, 
both with IPv6 enabled, and now it works mysteriously. I have tested 
this with both the 2.4 and 2.6 kernel on two machines so it shouldn't be 
a coincidence.

Dufflebunk wrote:

> I don't think I did. I ended up using vnc instead. Overkill, but it
> worked. When you compile X, take a look at the configure message the
> whip by, I think one is about IPv6 and mine always said yes.
>
> On Fri, 2003-08-22 at 14:35, "Jimmy Yen(顏孝杰)" wrote:
>  
>
> > Um, this thread is old, but did you find a solution for this? I just 
> > found that I'm having the same problem!
> >
> > Dufflebunk wrote:
> >
> >    
> >
> > > The net-tools had it off, I double checked linux and found ipv6 enabled
> > > as a module, but the module is unloaded. I've recompiled linux and X.
> > > Same problem still.
> > >
> > > I think I recompiled X before this problem started showing up.
> > >
> > > On Fri, 2003-07-25 at 12:37, Eric Sandall wrote:
> > >
> > >
> > >      
> > >
> > > > Dufflebunk said:
> > > >   
> > > >
> > > >        
> > > >
> > > > > I seem to be having a problem with my x server thinking that it can use
> > > > > IPv6. Here's the dope:
> > > > >
> > > > > $ export DISPLAY=localhost:0
> > > > > $ xclock
> > > > > _X11TransSocketOpen: socket() failed for tcp
> > > > > _X11TransSocketOpenCOTSClient: Unable to open socket for tcp
> > > > > _X11TransOpen: transport open failed for tcp/localhost:0
> > > > > Error: Can't open display: localhost:0
> > > > > $
> > > > >
> > > > > In an strace, everything looks goo up until:
> > > > > socket(PF_INET6, SOCK_STREAM, 0)        = -1 EAFNOSUPPORT (Address family
> > > > > not supported by protocol)
> > > > >
> > > > > The same command on another box without this error, results in
> > > > > socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 3
> > > > >
> > > > > Anyone have any idea how to tell X to ditch the IPv6 support?
> > > > >     
> > > > >
> > > > >          
> > > > When you compiled net-tools, did you say 'y' to configure?  And if so, did
> > > > you then say 'y' to IPV6 support (default is 'n' to both)?  Does your
> > > > kernel have IPV6 support?  If yes to any of these, perhaps a compile of
> > > > xfree86 detected these changes.  Did this problem occur after recompling
> > > > xfree86, or did it start happening without a recompile of xfree86?
> > > >
> > > > -sandalle
> > > >   
> > > >
> > > >        
> > > _______________________________________________
> > > SM-Discuss mailing list
> > > SM-Discuss AT lists.ibiblio.org
> > > http://lists.ibiblio.org/mailman/listinfo/sm-discuss
> > >
> > >
> > >
> > >
> > >      
> > _______________________________________________
> > SM-Discuss mailing list
> > SM-Discuss AT lists.ibiblio.org
> > http://lists.ibiblio.org/mailman/listinfo/sm-discuss
> >