Summary: | xfree-4.3.0-r3 does not allow ipv4 connections after ipv6 patch | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Paul Slinski <deviantgeek> |
Component: | Current packages | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | deviantgeek, ipv6, latexer, sgtphou |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Paul Slinski
2003-06-09 16:12:35 UTC
Peter, suggestions? I happened upon this via Google. Could this be more relevant? [long url follows] http://216.239.39.100/search?q=cache:IEbf1EB8Iz4J:www.t8o.org/~mca1001/fixed/+X11TransSocketOpen:+socket()+failed+for+tcp&hl=en&ie=UTF-8 well, basically, the patch does that. before xfree-4.4 comes out, the ipv6 patch should get integrated. x.org knows about the issue, and they're going to patch the patch. nothing to do but wait, really. I also have ipv6 enabled in this xfree. Could this explain why it seems to take a much longer time for most apps to open? Seems to be a much larger delay than -r2 with ipv6 enabled as well. Since it should be apperent to anyone using the ipv6 flag that some apps wont work without the module loaded I'm going to suggest that a notice be placed before the build starts reminding folks to load the module first or some stuff wont work (Xnest, import (ImageMagick), etc.). This really isn't a bug per-se anyway ;-) This is well over a year old without a comment. Does anyone object to this being closed? not really a bug, so closing |