[X2Go-User] Resizing bug

[Ulrich Sibiller]

On Sun, May 3, 2020 at 9:18 PM Kees Bakker <kees at ijzerbout.nl> wrote:
> > I've seen you mentioning on the irc channel but you did not react to
> > my questions. Thx for posting it here.
> At times, one has to eat :-)

;-)

> >> I'm surprised that I'm the only one seeing this, because I see it on all
> >> the environments that I work on. That is,
> > Obviously you are, I have not heard of this kind of bug before.
>
> That is probably because you're not using the standard Ubuntu desktop.
> Or are you?

No, I am using kde on debian.
>
> >> My client is Ubuntu (with Ubuntu desktop) and the server side is Ubuntu
> >> with a Mate (or Openbox or XFCE) session.
> >> Also worthwhile to mention that I don't have my x2go client full screen.
> >>
> >> When I move(!) the X2GO window, it resizes(!). And when I keep the mouse
> >> clicked on the top bar for the move,
> >> (and even if I don't move anymore) it keeps resizing until it reaches
> >> the maximum height of my local monitor.
> >> BTW. That maximum monitor height is not(!) the maximum height of my
> >> local window manager. The maximum
> >> height for the X2GO client window is the monitor height minus the height
> >> of the top bar.
> > This sounds like a bug in the _local_ window manager. Do you also see
> > that when replacing the local window manager with e.g. openbox
> > (openbox --replace)?
>
> When I run the Mate desktop then the problem does not exist. (I may
> try the suggested openbox --replace in a virtualbox, centainly not
> on my normal PC environments, at home, at work.)

Running another window manager is no permanent thing. You can do that
in your running session and then switch back to the old WM using the
same method (however, I am not sure what the ubuntu default WM is -
maybe marco?).  You can also create a second empty user profile just
for the purpose of testing. It will not harm you standard session. And
it will also not harm your remote session.

> That tells me there is a bug when the X2GO client is used from an Ubuntu
> desktop. The question is, how can we find out where the bug is?

Well, switching the local window manager ist my approach for ruling
out stuff. If this is tied to the window manager I can probably
reproduce this easily.

I can instruct you how to build a debugging version of
nxagent/x2goagent to get more information in the logs.

> Again, I'm surprised that no X2GO user has seen this bug. It makes me
> wonder if I'm the only one running X2GO from an Ubuntu desktop.

Maybe you have altered some setting in your environment that is
falling on your feet now.

Uli