Re-establishing remote-X access.
For the past n years I've been running X-capable programs on this system
remote$ uname -a
FreeBSD AngkorWat 9.2-RELEASE-p10 FreeBSD 9.2-RELEASE-p10 #0: Tue Jul 8
10:48:24 UTC 2014
root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
remote$
using this system as the display:
local$ uname -a
Linux BanjaLuka 3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt9-3 (2015-04-23)
i686 GNU/Linux
local$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux testing (stretch)
Release: testing
Codename: stretch
local$
Due to an accidental reboot on the local system, I've discovered this no longer
works:
local$ grep nolisten /etc/X11/xinit/xserverrc
local$ xhost +inet:angkorwat
angkorwat being added to access control list
local$ ssh -YC angkorwat
X11 forwarding request failed on channel 0
Last login: Thu May 28 16:09:09 2015 from banjaluka.rclayton.net
FreeBSD 9.2-RELEASE-p10 (GENERIC) #0: Tue Jul 8 10:48:24 UTC 2014
Welcome to FreeBSD!
[ blah blah blah ]
remote$ export DISPLAY=banjaluka:0.0
remote$ xmixer
Error: Can't open display: banjaluka:0.0
remote$
I don't know what the "X11 forwarding request failed" message means, but it
always shows up and hasn't interfered with remote access before.
Remote access also fails with "ssh -Y", "ssh -XC", and "ssh -X".
The remote system hasn't been changed in quite a while, and the local system is
updated weekly. I'm assuming the problem's occurring due to some change on the
local system.
What problem has developed providing local X access to remote programs? How do
I go about debugging this problem?
Reply to: