Bug 629032 - Xephyr fails to start when IPv6 module is disabled
Xephyr fails to start when IPv6 module is disabled
Product: Fedora
Classification: Fedora
Component: xorg-x11-server (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: X/OpenGL Maintenance List
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-08-31 14:19 EDT by Stefan Becker
Modified: 2012-08-16 17:23 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1221916 (view as bug list)
Last Closed: 2012-08-16 17:23:23 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Stefan Becker 2010-08-31 14:19:27 EDT
[This was found while debugging why SELinux "sandbox -X" doesn't work on my machine]


1. disable IPv6 module loading

  Either add a file to /etc/modprobe.d with

    install ipv6 /bin/true


    blacklist ipv6
  + disable all services that might set up ipv6, e.g. ip6tables

2. after boot make sure that "ipv6" isn't loaded:

    # lsmod | fgrep ipv6

3. SELinux can be in Enforced or Permissive mode

    This only affects what kind of AVCs you'll receive. It hasn't anything to do with the problem.

4. start Xephyr

   (this is the command line used by sandbox -X)

    $ /usr/bin/Xephyr -title "test" -terminate -screen 1024x768 -displayfd 5
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/l3f1199:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/l3f1199:1
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/l3f1199:2
... and so on and so on ...
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet
_XSERVTransSocketOpenCOTSServer: Unable to open socket for local
_XSERVTransOpen: transport open failed for local/l3f1199:64510
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for local
_XSERVTransSocketOpenCOTSServer: Unable to open socket for unix
_XSERVTransOpen: transport open failed for unix/l3f1199:64510
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for unix

Fatal server error:
Failed to find a socket to listen on
Comment 1 Fedora End Of Life 2012-08-16 17:23:25 EDT
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Note You need to log in before you can comment on or make changes to this bug.