I just uploaded 2.6.0_beta2 which pulls in all the updates in X11R7.6 RC1 plus the xorg-server 1.9.3 RC1 server. You can obtain the update by checking for updates in the X11 menu or directly here: http://static.macosforge.org/xquartz/downloads/SL/XQuartz-2.6.0_beta2.dmg The full ChangeLog is available here: http://xquartz.macosforge.org/trac/wiki/ChangeLog The only XQuartz specific changes I want to address before making rc1 are related to RandR. If you find any regressions or serious issues, please let me know. --Jeremy
For some reason, I can't ssh -XY anymore. $DISPLAY on the Mac is :0 The sshd on the remote side logs the message "channel 3: open failed: administratively prohibited: open failed" This all worked yesterday, the only difference is that the Mac was upgraded from beta1 to beta2. Restarting xquartz does not help. The "About X11" item shows that beta2 is running. The remote connections option in preferences is enabled (it was before as well) Possibly related, I no longer get an xterm when launching xquartz from the dock. On Nov 14, 2010, at 1:40 AM, Jeremy Huddleston wrote:
I just uploaded 2.6.0_beta2 which pulls in all the updates in X11R7.6 RC1 plus the xorg-server 1.9.3 RC1 server. You can obtain the update by checking for updates in the X11 menu or directly here: http://static.macosforge.org/xquartz/downloads/SL/XQuartz-2.6.0_beta2.dmg
The full ChangeLog is available here: http://xquartz.macosforge.org/trac/wiki/ChangeLog
The only XQuartz specific changes I want to address before making rc1 are related to RandR. If you find any regressions or serious issues, please let me know.
--Jeremy
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Beta2 is almost a year old, perhaps you should try upgrading to 2.6.3 now? Also your DISPLAY value should not be :0, please check your bashrc or tcshrc files to see if its being set in there, and remove that. Jamie On Sep 27, 2011, at 9:12 AM, Daniel Seagraves wrote:
For some reason, I can't ssh -XY anymore. $DISPLAY on the Mac is :0 The sshd on the remote side logs the message "channel 3: open failed: administratively prohibited: open failed" This all worked yesterday, the only difference is that the Mac was upgraded from beta1 to beta2. Restarting xquartz does not help. The "About X11" item shows that beta2 is running. The remote connections option in preferences is enabled (it was before as well)
Possibly related, I no longer get an xterm when launching xquartz from the dock.
On Nov 14, 2010, at 1:40 AM, Jeremy Huddleston wrote:
I just uploaded 2.6.0_beta2 which pulls in all the updates in X11R7.6 RC1 plus the xorg-server 1.9.3 RC1 server. You can obtain the update by checking for updates in the X11 menu or directly here: http://static.macosforge.org/xquartz/downloads/SL/XQuartz-2.6.0_beta2.dmg
The full ChangeLog is available here: http://xquartz.macosforge.org/trac/wiki/ChangeLog
The only XQuartz specific changes I want to address before making rc1 are related to RandR. If you find any regressions or serious issues, please let me know.
--Jeremy
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
You're right; I replied to the wrong thread. I had deleted the 2.7.0_beta2 announcement and had to dig in my trash for it. I meant 2.7.0_beta2. Should I change the subject? On Sep 27, 2011, at 9:58 AM, Jamie Kennea wrote:
Beta2 is almost a year old, perhaps you should try upgrading to 2.6.3 now?
Also your DISPLAY value should not be :0, please check your bashrc or tcshrc files to see if its being set in there, and remove that.
Jamie
On Sep 27, 2011, at 9:12 AM, Daniel Seagraves wrote:
For some reason, I can't ssh -XY anymore. $DISPLAY on the Mac is :0 The sshd on the remote side logs the message "channel 3: open failed: administratively prohibited: open failed" This all worked yesterday, the only difference is that the Mac was upgraded from beta1 to beta2. Restarting xquartz does not help. The "About X11" item shows that beta2 is running. The remote connections option in preferences is enabled (it was before as well)
Possibly related, I no longer get an xterm when launching xquartz from the dock.
On Nov 14, 2010, at 1:40 AM, Jeremy Huddleston wrote:
I just uploaded 2.6.0_beta2 which pulls in all the updates in X11R7.6 RC1 plus the xorg-server 1.9.3 RC1 server. You can obtain the update by checking for updates in the X11 menu or directly here: http://static.macosforge.org/xquartz/downloads/SL/XQuartz-2.6.0_beta2.dmg
The full ChangeLog is available here: http://xquartz.macosforge.org/trac/wiki/ChangeLog
The only XQuartz specific changes I want to address before making rc1 are related to RandR. If you find any regressions or serious issues, please let me know.
--Jeremy
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
On Sep 27, 2011, at 11:35 AM, Daniel Seagraves wrote:
You're right; I replied to the wrong thread. I had deleted the 2.7.0_beta2 announcement and had to dig in my trash for it. I meant 2.7.0_beta2. Should I change the subject?
Well that puts a different light on things. Still doesn't change the fact that your DISPLAY should not be :0 though! Try fixing that. :) Jamie
I checked my bashrc and login files, there's nothing that sets DISPLAY. If I run Terminal, $DISPLAY is /tmp/launch-5Xo9WK/org.x:0 If I run xquartz, launch terminal from the menu, then $DISPLAY is :0 Nothing in my home directory has the string "DISPLAY" in it. Anywhere else you can think of to look? On Sep 27, 2011, at 11:27 AM, Jamie Kennea wrote:
On Sep 27, 2011, at 11:35 AM, Daniel Seagraves wrote:
You're right; I replied to the wrong thread. I had deleted the 2.7.0_beta2 announcement and had to dig in my trash for it. I meant 2.7.0_beta2. Should I change the subject?
Well that puts a different light on things. Still doesn't change the fact that your DISPLAY should not be :0 though!
Try fixing that. :)
Jamie
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
On Sep 27, 2011, at 10:11 AM, Daniel Seagraves wrote:
I checked my bashrc and login files, there's nothing that sets DISPLAY.
If I run Terminal, $DISPLAY is /tmp/launch-5Xo9WK/org.x:0 If I run xquartz, launch terminal from the menu, then $DISPLAY is :0 Nothing in my home directory has the string "DISPLAY" in it. Anywhere else you can think of to look?
This $DISPLAY sounds like "correct" behavior given that the default $DISPLAY is owned by X11.app (see the parallel thread).
On Sep 27, 2011, at 6:12 AM, Daniel Seagraves wrote:
For some reason, I can't ssh -XY anymore. $DISPLAY on the Mac is :0 The sshd on the remote side logs the message "channel 3: open failed: administratively prohibited: open failed"
You can use '-vvv' to get much more verbose information out of ssh, but my guess is that your remote system doesn't allow ssh forwarding. You should check /etc/ssh/sshd_config or /etc/sshd_config on the remote host.
Unless it somehow got disabled on every host on our network, that's not it. As a test, I opened Terminal next to xterm, and set DISPLAY in xterm equal to what was in Terminal (/tmp/launch-LNnWLq/org.x:0 in this case) After doing that, ssh -XY works again. Maybe ssh is doing something unusual that causes :0 to fail? On Sep 27, 2011, at 1:34 PM, Jeremy Huddleston wrote:
On Sep 27, 2011, at 6:12 AM, Daniel Seagraves wrote:
For some reason, I can't ssh -XY anymore. $DISPLAY on the Mac is :0 The sshd on the remote side logs the message "channel 3: open failed: administratively prohibited: open failed"
You can use '-vvv' to get much more verbose information out of ssh, but my guess is that your remote system doesn't allow ssh forwarding. You should check /etc/ssh/sshd_config or /etc/sshd_config on the remote host.
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
I take that back, sort of. The $DISPLAY in Terminal points to xquartz 2.6.3, is that the one that came with Lion? It does get me a display though, so it proves it's not my servers at fault. On Sep 28, 2011, at 8:08 AM, Daniel Seagraves wrote:
Unless it somehow got disabled on every host on our network, that's not it. As a test, I opened Terminal next to xterm, and set DISPLAY in xterm equal to what was in Terminal (/tmp/launch-LNnWLq/org.x:0 in this case) After doing that, ssh -XY works again. Maybe ssh is doing something unusual that causes :0 to fail?
On Sep 27, 2011, at 1:34 PM, Jeremy Huddleston wrote:
On Sep 27, 2011, at 6:12 AM, Daniel Seagraves wrote:
For some reason, I can't ssh -XY anymore. $DISPLAY on the Mac is :0 The sshd on the remote side logs the message "channel 3: open failed: administratively prohibited: open failed"
You can use '-vvv' to get much more verbose information out of ssh, but my guess is that your remote system doesn't allow ssh forwarding. You should check /etc/ssh/sshd_config or /etc/sshd_config on the remote host.
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
The launchd socket does not use xauth. Again, use -vvv to get mode info. On Sep 28, 2011, at 06:08, Daniel Seagraves wrote:
Unless it somehow got disabled on every host on our network, that's not it. As a test, I opened Terminal next to xterm, and set DISPLAY in xterm equal to what was in Terminal (/tmp/launch-LNnWLq/org.x:0 in this case) After doing that, ssh -XY works again. Maybe ssh is doing something unusual that causes :0 to fail?
On Sep 27, 2011, at 1:34 PM, Jeremy Huddleston wrote:
On Sep 27, 2011, at 6:12 AM, Daniel Seagraves wrote:
For some reason, I can't ssh -XY anymore. $DISPLAY on the Mac is :0 The sshd on the remote side logs the message "channel 3: open failed: administratively prohibited: open failed"
You can use '-vvv' to get much more verbose information out of ssh, but my guess is that your remote system doesn't allow ssh forwarding. You should check /etc/ssh/sshd_config or /etc/sshd_config on the remote host.
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
I did ssh -XYvvv and the messages relevant to x11 are as follows: During the connection negotiation (after auth) debug2: x11_get_proto: /usr/X11R6/bin/xauth list :0 2>/dev/null debug1: Requesting X11 forwarding with authentication spoofing. debug2: channel 0: request x11-req confirm 0 When trying to run emacs: debug1: client_input_channel_open: ctype x11 rchan 3 win 65536 max 16384 debug1: client_request_x11: request from ::1 48744 debug1: failure x11 If I am supposed to be doing something with xauth, I didn't have to do it before. On Sep 28, 2011, at 6:53 PM, Jeremy Huddleston wrote:
The launchd socket does not use xauth. Again, use -vvv to get mode info.
On Sep 28, 2011, at 06:08, Daniel Seagraves wrote:
Unless it somehow got disabled on every host on our network, that's not it. As a test, I opened Terminal next to xterm, and set DISPLAY in xterm equal to what was in Terminal (/tmp/launch-LNnWLq/org.x:0 in this case) After doing that, ssh -XY works again. Maybe ssh is doing something unusual that causes :0 to fail?
On Sep 27, 2011, at 1:34 PM, Jeremy Huddleston wrote:
On Sep 27, 2011, at 6:12 AM, Daniel Seagraves wrote:
For some reason, I can't ssh -XY anymore. $DISPLAY on the Mac is :0 The sshd on the remote side logs the message "channel 3: open failed: administratively prohibited: open failed"
You can use '-vvv' to get much more verbose information out of ssh, but my guess is that your remote system doesn't allow ssh forwarding. You should check /etc/ssh/sshd_config or /etc/sshd_config on the remote host.
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
participants (3)
-
Daniel Seagraves
-
Jamie Kennea
-
Jeremy Huddleston