Desktop flashing when maximizing window on second screen with Windows client #11
Comments
|
If you are using X2Go Client for Windows, I recommend replacing the Program FIles "x2goclient/VcXsrv" folder entirely with the "VcXsrv" folder that VcXsrv itself installs under Program Files. You could of course configure X2Go Client for Windows to use an external X server, but that is easier and often it passes more correct arguments to VcXsrv. Once the nightly builds of x2goclient for Windows switch to the new VcXsrv, please use those instead for proper testing (until the next release comes out.) Please provide feedback as you do. Alex's winmultiwindow.patch was dropped because it caused a regression, and we found/implemented a better way of solving his customer's issue in x2goclient (launching vcxsrv with different arguments.) (https://github.com/ArcticaProject/vcxsrv/blob/release/1.17.0.0-x/releasenotes/releasenote_1.17.0.0-3.x2go%2Barctica.txt) (X2Go Bug #883) The other patch in #4 was resolved by backporting an upstream xorg-server patch that is surely in VcXsrv by now. The rest of the patches are build-related, such as Windows XP/Vista support & not putting the timestamps in the fonts .gz files, so that builds of fonts .gz files are reproducible/identical & do not waste space / degrade when checked into x2goclient-contrib.git repeatedly. (I should try to get that change accepted upstream.) (I can workaround this as the x2goclient for Windows maintainer until it is accepted.) I would have upgraded x2goclient to a newer version of VcXsrv sooner, but I recall having a regression when I tried 1.19.2.0 a while ago. I forget what it was. Either way, 1.19.6.4 32-bit is working for me fine now based on limited testing on my Win10 1709 64-bit, and XP/Vista support is no longer something I wish to maintain. Please provide more feedback, and I will put it in X2Go Client for Windows. I will re-double my efforts to get those minor build fixes accepted upstream. I will also re-consider retiring this fork, especially if Marha starts accepting more merge requests. |
|
I have no further feedback to provide except that I think in case of
trouble backporting the flashing fix look easily doable.
Uli
…On Thu, Apr 26, 2018 at 2:42 AM, Mike DePaulo ***@***.***> wrote:
@attzonko <https://github.com/attzonko> @nkrepo
<https://github.com/nkrepo>
If you are using X2Go Client for Windows, I recommend replacing the
Program FIles "x2goclient/VcXsrv" folder entirely with the "VcXsrv" folder
that VcXsrv itself installs under Program Files. You could of course
configure X2Go Client for Windows to use an external X server, but that is
easier and often it passes more correct arguments to VcXsrv.
Once the nightly builds of x2goclient for Windows switch to the new
VcXsrv, please use those instead for proper testing (until the next release
comes out.)
Please provide feedback as you do.
@Ionic <https://github.com/Ionic> @uli42 <https://github.com/uli42>
@sunweaver <https://github.com/sunweaver>
Alex's winmultiwindow.patch was dropped because it caused a regression,
and we found/implemented a better way of solving his customer's issue in
x2goclient (launching vcxsrv with different arguments.) (
https://github.com/ArcticaProject/vcxsrv/blob/release/1.17.0.0-x/
releasenotes/releasenote_1.17.0.0-3.x2go%2Barctica.txt) (X2Go Bug #883
<https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=883>)
The other patch in #4 <#4>
was resolved by backporting an upstream xorg-server patch that is surely in
VcXsrv by now.
The rest of the patches are build-related, such as Windows XP/Vista
support & not putting the timestamps in the fonts .gz files, so that builds
of fonts .gz files are reproducible/identical & do not waste space /
degrade when checked into x2goclient-contrib.git
<https://code.x2go.org/gitweb?p=x2goclient-contrib.git;a=summary>
repeatedly. (I should try to get that change accepted upstream.) (I can
workaround this as the x2goclient for Windows maintainer until it is
accepted.)
I would have upgraded x2goclient to a newer version of VcXsrv sooner, but
I recall having a regression when I tried 1.19.2.0 a while ago. I forget
what it was.
Either way, 1.19.6.4 32-bit is working for me fine now based on limited
testing on my Win10 1709 64-bit, and XP/Vista support is no longer
something I wish to maintain. Please provide more feedback, and I will put
it in X2Go Client for Windows. I will re-double my efforts to get those
minor build fixes accepted upstream.
I will also re-consider retiring this fork, especially if Marha starts
accepting more merge requests.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGBw5LFeIRBxO7kcu17UyGbGjcgVK_V7ks5tsRf3gaJpZM4TkWXZ>
.
|
|
When I tried replacing the x2goclient/VcXsrv folder completely, I ran into a different issue. The 'maximize' square got grayed out for me. |
|
Thanks for your great work. I've been suffering from the strange UI behavior of texmaker for nearly two years and I could not figure out why. Now it finally comes to the end. |
Getting VcXsrv version 1.19.6.4 or later shipped with x2go client on Windows would be very much appreciated, as the flickering has a high PITA factor. This is especially true for users that are new to accessing Linux remotely from Windows (or new to using Linux at all). |
|
On Sat, Dec 29, 2018 at 12:16 PM Stefan Blumentrath ***@***.***> wrote:
Either way, 1.19.6.4 32-bit is working for me fine now based on limited testing on my Win10 1709 64-bit, and XP/Vista support is no longer something I wish to maintain. Please provide more feedback, and I will put it in X2Go Client for Windows. I will re-double my efforts to get those minor build fixes accepted upstream.
Getting VcXsrv version 1.19.6.4 or later shipped with x2go client on Windows would be very much appreciated, as the flickering has a high PITA factor. This is especially true for users that are new to accessing Linux remotely from Windows (or new to using Linux at all).
Anything that should be tested and you would like to get feedback on in particular in order to include a newer VcXsrv version?
Vcxsrv 1.20.0.0 has been included from 4.1.2.0 (released 2018-06-25).
Here's the changelog excerpt:
[ Mike DePaulo ]
* New upstream version (4.1.2.0):
...
- Windows: Upgrade bundled VcXsrv from 1.17.0.0-3 (X2Go/Arctica Build)
to 1.20.0.0 (upstream build)
+ Fixes ArcticaProject/nx-libs#600
+ Incompatible with XP & Vista
+ Unmodified except for strip-nondeterminism being run on .gz files
So just upgrade and you'll be fine. Or do you still see this with that
very version? Then we have a new bug...
Uli
|
Continuing discussion of ArcticaProject/nx-libs#600
The text was updated successfully, but these errors were encountered: