Summary: | x11-servers/xorg-server In X server after 1.17, default configuration is now -nolisten tcp | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | Yasuhito FUTATSUKI <freebsd-bug-report-yf> |
Component: | Individual Port(s) | Assignee: | freebsd-x11 (Nobody) <x11> |
Status: | Closed Not A Bug | ||
Severity: | Affects Some People | CC: | bob, freebsd-bug-report-yf, junovitch |
Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(x11) |
Version: | Latest | ||
Hardware: | Any | ||
OS: | Any |
Description
Yasuhito FUTATSUKI
2015-10-16 18:07:34 UTC
I believe that I am experiencing this problem with xorg-server-1.17.2 as well. Can someone please provide details of how to work around it? (In reply to bob from comment #1) There are two way of working arround it. (1) For clients, specifying display with a form of ":n". If you set DISPLAY environment in your X session starting script with "hostname:n" style, where hostname is your local hostname or "localhost", remove hostname. Then the clients will be able to connect X server via UNIX domain socket. This solution cannot be applied if you want to connect from other host than the host X server runs without proxy such as ssh forwarding. (2) For X server, pass "-listen tcp option" to X server. If you are using startx(1) or xinit(1) for starting X server, add its command line argument "-listen tcp" after "--", or use xserverrc script to start X server to pass the arguments. (Please see startx(1) or xinit(1) man page for detail) If you are using other way to starting X (for example xdm or gdm for grafical login session), check your script (or program) to pass the argument. Thanks! Adding the '-- listen tcp' option to my startx command resolved this for me. I do agree that something should be added to UPDATING about this. It is clearly a violation of POLA for those of us that are affected. Is this worth staying open at this point? xorg 1.17 not listening on a TCP port is old news at this point and I don't know how relevant an UPDATING entry would be a year later given how few folks probably use the feature. (In reply to Jason Unovitch from comment #4) I'm sorry too late to respond. I agree this is too late to mention it. |