Hi all,
Thanks for the answers.
@Stefan: The problem occurs in both modes. (We used X2Go in desktop mode
for a long time before trying single-application mode, no difference).
Adding
*-Dsun.java2d.xrender=True*
did improve latency (although it's noticeable, so I'd like to investigate
more).
If you are using the single application mode you could try this:
https://superuser.com/questions/400766/netbeans-java-shows-empty-window-in-tiling-window-manager-awesome-wm
In the past I had success both with the wmname tool and the
environment variable.
Uli
On Tue, Jun 22, 2021 at 8:58 AM
Hi Tom,
Am 21.06.21 um 22:20 schrieb Tom Korach:
> mobaXterm did not allow forwarding a
> single application
This makes me wonder - in your initial post to the list, you stated you
were using XFCE. Now it sounds like you're trying to use single
application mode.
If you're only seeing this
On Mon, Jun 21, 2021 at 10:20 PM Tom Korach wrote:
> I connected to the same server using mobXterm (X11 forwarding): similar
> latency, this time across the board - mobaXterm did not allow forwarding a
> single application, so I connected to a desktop session. Both dbeaver,
> Firefox and the
Hi,
Thanks for the quick response.
I connected to the same server using mobXterm (X11 forwarding): similar
latency, this time across the board - mobaXterm did not allow forwarding a
single application, so I connected to a desktop session. Both dbeaver,
Firefox and the desktop in general suffered
Hmm, I have tried replicating this problem, but to no avail.
Can you please try running another Xserver on Windows, like mobaxterm?
Uli
On Mon, Jun 21, 2021 at 9:09 PM Tom Korach wrote:
>
> Hi,
>
> When using X2Go to work on Java-based applications (specifically, the
> Eclipse-based dbeaver
