- 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.
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:
|sssssssssssssssssssssssssss| |sssssssssssssssssssssssssss| |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.
I also get a pop-up message about the sound that I had not experienced with previous versions.
What does the Popup say? Was it unable to start PulseAudio? Is there any way to reproduce that?
If possible, a debug log would be good to have, including the PA server config file that is left somewhere in your user's directory when starting the debug version of the client.
You'd have to install the debug version and start it in a command line terminal, redirecting output to a file, such as:
path\to\x2goclient.debug.exe --debug > by\your\user\writeable\path\x2goclient-debug.log 2>&1
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 while to trying to do routine tasks with the current release.
That's what the Saimaa release is for. You'll have to switch repositories and make sure to pin the release.
After doing so, you should be following issue reports that affect you and eventually switch back to the stable server release, since Saimaa is not getting any bug fixes or new features, apart from security-related issues.
Mihai