Hello,
When using the ppa:x2go/stable repository, something seemed strange when I ran
the update manager in Ubuntu 14.04 and Ubuntu 16.04. I received a message about
a partial upgrade I've never seen since using Ubuntu. I've attached the
message. After running this partial upgrade, I started experiencing the
flickering problems. Removed x2goserver entirely, and did a fresh install of
the most update to date version. Still experiencing the flickering problems.
I uninstalled everything from x2goserver on our system. Also uninstalled any
lingering package versions that might conflict with trying to install from the
Saimaa repository.
After cleaning, I installed x2goserver from the Saimaa repository.
I no longer experience the flickering when maximizing/minimizing or moving the
window from side-to side. Everything is working fine like it was prior to the
most recent update from the ppa:x2go/stable repository. I think I'm going to
stick with the Saimaa repository for now until the bugs are fixed from the
ppa:x2go/stable repository.
Also going to stick with x2goclient 4.1.0.0 where there is no issue with
clicking the session panel. I can click where I'm accustomed to clicking again.
Why are there 2 repositories for x2go and which one should we use for the
long-term?
Any help would be appreciated.
h.
From: x2go-user on behalf of h i
Sent: Friday, March 9, 2018 4:23 PM
To: x2go-user@lists.x2go.org
Subject: Re: [X2Go-User] Problems after upgrading to recent x2go-server and
x2go client releases
Mihai,
Thanks for your response. Please see my responses below:
* On 03/07/2018 07:34 PM, h i wrote:
> >I've been experiencing problems with opening applications and resizing my
> >x2go
> >client window after installing the newest version x2go-server.
>
>
> >The issues occurs on Ubuntu 14.04 and 16.04.
>
>
> >What happens now is that every time I maximize my x2go-client window, the
> >images
> >on screen rapidly flicker and won't stop until I minimize the screen.
>>The flickering is a known problem, but as far as we can tell only appears on
>>Windows (and even then not with all X servers, but prominently with VcXsrv,
>>that
>>we bundle). It's tracked here:
>>https://github.com/ArcticaProject/nx-libs/issues/600
> Also, each time I move the window, a quick flicker occurs across the screen.
>Probably related to the move being something alike to a resize and thus also
>triggering the new xinerama code.
> >This never occurred before this new release.
>There is no known workaround currently, though it might be possible to just
>ignore multiple resize events in nxagent if the requested size doesn't change.
>We'll have to see how that goes.
I think I might have to roll-back to the previous x2goserver version. At least
with our setup, we never had a flicker issue until this most recent update.
> >On the client side, I upgraded to the 4.1.1.1 from 4.1.0.0 and experienced
> >some
> >issues. I have to click on the outside/top-right edge of the session panel
> >for
> >the login session window to appear. Any thing closer to the middle, and it
> >won't
> >respond.
>This is not an issue, but an often requested new feature. I've changed the
>click-sensitive area to an upside-down L shape around the session settings that
>can be modified within the tile. Actually like this, where "s" denotes a
>click-sensitive area:
___
|sss|
|sss|
|sss|
|sss|
|sss|
|sss|
---
>The problem so far has been that users can normally edit some exposed settings
>within a tile, but doing so proved to be very difficult since an incorrect
>click
>triggered a session startup instead of changing a setting, which was happening
>quite often.
>The sensitive area isn't small and figuring that out shouldn't take long
>usually, so I guess you've just been unlucky to always click on the right hand
>side which is typically insensitive but in the upper part.
Interesting. Yeah, I never had an issue with the sensitive area. Understandable
that others might have an issue.
> >Once logged into a session, the flickering resulting
> >from moving/maximizing the window is much worse.
> >
>> Fortunately, I was able to revert back to x2go-client 4.1.0.0.
>Huh, the flickering should be always the same, whether a session has been
>started with 4.1.1.1 or 4.1.0.0. Though, potentially there could be a
>difference: versions prior to 4.1.1.1 won't be able to utilize the Xinerama
>feature in X2Go Server 4.1.0.0, so when connecting with older client versions
>Xinerama will always be disabled in nxagent.
>> However,is there a way to revert back to this previous version/configuration
>> of x2goserver. Right now, it is has been a lot of flickering