Re: [X2Go-User] Problems after upgrading to recent x2go-server and x2go client releases
* On 03/08/2018 07:52 PM, Stefan Baur wrote: > Could we change the mouse cursor over the sensitive area, maybe? Or, > undo the change and go back to a fully sensitive tile, but change the > mouse cursor once it hovers over an editable field? The problem isn't visual indication and changing the mouse cursor thus wouldn't help. The fields are already highlighted when hovering over them, which gives the same visual clue changing the cursor would. The problem is human accuracy, as demonstrated by Fitts's Law. Pointing accuracy decreases as the distance to or size of the target increase. Typically, the distance is pretty high, so users often over- or undershoot the target box, even if by just a few pixels. Decreasing the sensitive area totally makes sense - I've had requests for this from multiple users and my personal experience is also that it was frustrating to change settings directly in the tiles before since every and now and then you ended up starting the session instead of changing a setting. I'd generally advise to trigger sessions by clicking a pointer near the session icon (or in any area horizontally or vertically from it). Mihai signature.asc Description: OpenPGP digital signature ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] Problems after upgrading to recent x2go-server and x2go client releases
Am 08.03.2018 um 19:38 schrieb Mihai Moldovan: >> 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. Could we change the mouse cursor over the sensitive area, maybe? Or, undo the change and go back to a fully sensitive tile, but change the mouse cursor once it hovers over an editable field? Kind Regards, Stefan Baur -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 signature.asc Description: OpenPGP digital signature ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] Problems after upgrading to recent x2go-server and x2go client releases
* 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: ___ |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. > 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 signature.asc Description: OpenPGP digital signature ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
[X2Go-User] Problems after upgrading to recent x2go-server and x2go client releases
Hello, 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. Also, each time I move the window, a quick flicker occurs across the screen. This never occurred before this new release. I have a few systems with the current x2go verison installed, here is the output: x2goversion x2goserver: 4.1.0.0 x2goserver-common: 4.1.0.0 x2goserver-extensions: 4.1.0.0 x2goserver-fmbindings: 4.1.0.0 x2goserver-printing: 4.1.0.0 x2goserver-x2goagent: 3.5.99.14 x2goserver-xsession: 4.1.0.0 We have another system running x2go server, but have yet to update it due to the problems we've experienced. Here is the output of the previous version we are running without the issues: x2goversion x2goagent: 3.5.0.33 x2goserver: 4.0.1.22 x2goserver-extensions: 4.0.1.22 x2goserver-xsession: 4.0.1.22 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. I also get a pop-up message about the sound that I had not experienced with previous versions. 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. 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. Any insight would be appreciated. Thanks. H. ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
