On 2019/12/29 11:05, Dave Howorth wrote:
On Sun, 29 Dec 2019 02:27:12 -0800 L A Walsh <suse@tlinx.org> wrote:
It's a workaround, not really a solution.
I was going to ask are you sure your remote device is accepting traffic (is listening) for X11? I.e. is there a firewall in place? Same on the machine running xeyes -- is there a firewall in place that might be blocking outgoing X11 traffic?
I think I answered that upthread.
Seem like you missed trying basic network connectivity stuff, like DISPLAY=192.168.1.22:0.0 xeyes
You mean my original message? where I said:
---- The above was meant to be a location -- where you tried the above, did you also look at ping and netstat? Sorry for unclarity, but face it I'd have to have gotten that example from your posting with the same addr and program. I was wondering about pings and netstats.
$ DISPLAY=192.168.1.22:0.0 xeyes Error: Can't open display: 192.168.1.22:0.0
can the remote system ping your remote system?
if you look at netstat (linux args -tln), bsdish cygwin args : -an I piped output into |grep ':60..' to find the X11 port.
when something is listening, you'd see: TCP 0.0.0.0:6000 0.0.0.0:0 LISTENING or connected: TCP 192.168.3.12:6000 192.168.3.1:33722 ESTABLISHED TCP 192.168.3.12:6000 192.168.3.1:35116 ESTABLISHED
Main thing -- is something 'LISTENING' on port 6000.
Anyway, a bit late now, but X is generally a good thing to have running apart from a VNC/VPN.
Glad you got it working for you.
Yeah, me too. There does seem to be a problem with that video driver though, whereby it works for a couple of days and then apparently (to the client) appears to continue working but nothing appears on the display. I haven't investigated yet. It's Xmas/NY :)
I've seen something like that with GL/X where some clients seem to lose syncronization sometimes. But I haven't figured out the cause. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org