Re: fiji (graphical) remote access problem

Posted by David Pirotte on Feb 26, 2019; 2:48am
URL: http://imagej.273.s1.nabble.com/fiji-graphical-remote-access-problem-tp5021802p5021837.html

Hi Curtis,

> For what it's worth, I performed my test with tightvncserver, rather than
> vnc4server. For window manager I was using xfce locally, and had trouble
> launching another xfce during vncserver session initialization ("there is
> an instance already running") so I just tested without any running window
> manager. And the ImageJ text painted as expected in the client.

I guess it uses your built-in Mac app remote access rendering engine anyway,
and so I am not surprise, but thanks for the info.

> Other things you could try testing:

> * Try plain ImageJ 1.x from https://imagej.net/ij/download.html
> * Try tightnvcserver instead of vnc4server
> * Write a couple of very simple Java UI apps using java.awt and javax.swing
> and see if those also suffer from the issue

So far ) tried with tightvncserver, after I removed (purged) vnc4server, but just
'out of the box', with the exact vncserver config I used for vnc4server, I couldn't
connect (I can create the tunnel ssh successfully, but both xtightvnc (client) and
vinagre report a 'VNC server closed connection' and abort: I didn't try to solve
this (probably minor issue) yet.

> Sorry I can't be more helpful. It would be great if others who use Fiji
> over VNC could do some more exploration and testing to gather more
> information.

You have been very helpful: thanks to your answer (and you did take some of your
time to try ...), I know there is a configuration for which it works, which I can
report to the Gnome/Vinagre team.

> I filed an issue on GitHub to keep track of this problem and center future
> discussion:
>   https://github.com/fiji/fiji/issues/218

Ok,
Thanks again,
David

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html