Package: x2goclient Version: 4.1.2.2
Windows 10, x2goclient 4.1.2.2
When resuming a "paused" x2Go session, x2goclient is using the wrong X-Server settings.
I have configured my x2goclient with the following settings for X.Org Server settings:
**X.Org Server settings** [X] use custom X-Server Executable: C:/Program Files (x86)/x2goclient/VcXsrv/vcxsrv.exe [ ] start X-Server on X2Go Client start
Window mode: -screen 0 %wx%h -notrayicon -clipboard -keyhook
-nowinkill -nopn -silent-dup-error
Fullscreen mode: -fullscreen -notrayicon -clipboard -keyhook
-nowinkill -nopn -silent-dup-error
Single application: -multiwindow -notrayicon -clipboard
-keyhook -nowinkill -nopn -silent-dup-error
Whole display: -nodecoration -notrayicon -clipboard -keyhook
-nopn -silent-dup-error -screen 0 @
My x2goclient session is configured as:
**Session preferences: Input/Output** [ ] Fullscreen [ ] Custom Width (greyed out 3696) Height (greyed out 2160) [X] Use whole display [ ] Maximum available Display: 2
When I start a new x2Go session, it correctly runs the X-Server with the "Whole display" command (as per Windows Task Manager):
"C:\Program Files (x86)\x2goclient\VcXsrv\vcxsrv.exe"
-nodecoration -notrayicon -clipboard -keyhook -nowinkill
-nopn -silent-dup-error screen 0 @2 :0
But if I then "pause" this session and reconnect, x2goclient uses the "Window mode" command line options instead:
"C:\Program Files (x86)\x2goclient\VcXsrv\vcxsrv.exe"
-screen 3696x2160 -notrayicon -clipboard -keyhook
-nowinkill -nopn -silent-dup-error :0
I suspect this has something to do with the code around line 4442 in onmainwindow.cpp, but I've not been able to figure out the exact details yet.
Maarten
Hi all,
Today I've tried to set up a build environment on my Windows 10 laptop so I can (try to) debug this. I've tried to follow the instructions from:
https://wiki.x2go.org/doku.php/wiki:development:build-howto-mswin:x2goclient
However it fails at the step where you need to compile the static version of Qt. The QT build system doesn't seem to support the specific Windows version, as I'm getting the following build error:
$ ./configure -release -static -openssl -qt-style-windowsxp
-qt-style-windowsvista
Which edition of Qt do you want to use ?
Type 'c' if you want to use the Commercial Edition.
Type 'o' if you want to use the Open Source Edition.
o
-qt-style-windowsxp: invalid command-line switch
-qt-style-windowsvista: invalid command-line switch
The specified system/compiler port is not complete:
/c/Qt/4.8.6/mkspecs//qplatformdefs.h
Please use the contact form at http://qt.digia.com/contact-usNote the empty path between the "mkspecs" and "qplatformdefs.h" directories. There is supposed to be a symbolic name there identifying the type of system.
Does anybody have any updated build instructions for x2goclient on Windows? Or did I just miss something obvious?
Maarten
On 9/9/2020 11:55 AM, Maarten Boekhold wrote:
Package: x2goclient Version: 4.1.2.2
Windows 10, x2goclient 4.1.2.2
When resuming a "paused" x2Go session, x2goclient is using the wrong X-Server settings.
I have configured my x2goclient with the following settings for X.Org Server settings:
**X.Org Server settings** [X] use custom X-Server Executable: C:/Program Files (x86)/x2goclient/VcXsrv/vcxsrv.exe [ ] start X-Server on X2Go Client start
Window mode: -screen 0 %wx%h -notrayicon -clipboard -keyhook
-nowinkill -nopn -silent-dup-error Fullscreen mode: -fullscreen -notrayicon -clipboard -keyhook
-nowinkill -nopn -silent-dup-error Single application: -multiwindow -notrayicon -clipboard
-keyhook -nowinkill -nopn -silent-dup-error Whole display: -nodecoration -notrayicon -clipboard -keyhook
-nopn -silent-dup-error -screen 0 @My x2goclient session is configured as:
**Session preferences: Input/Output** [ ] Fullscreen [ ] Custom Width (greyed out 3696) Height (greyed out 2160) [X] Use whole display [ ] Maximum available Display: 2
When I start a new x2Go session, it correctly runs the X-Server with the "Whole display" command (as per Windows Task Manager):
"C:\Program Files (x86)\x2goclient\VcXsrv\vcxsrv.exe"
-nodecoration -notrayicon -clipboard -keyhook -nowinkill
-nopn -silent-dup-error screen 0 @2 :0But if I then "pause" this session and reconnect, x2goclient uses the "Window mode" command line options instead:
"C:\Program Files (x86)\x2goclient\VcXsrv\vcxsrv.exe"
-screen 3696x2160 -notrayicon -clipboard -keyhook
-nowinkill -nopn -silent-dup-error :0I suspect this has something to do with the code around line 4442 in onmainwindow.cpp, but I've not been able to figure out the exact details yet.
Maarten
x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
Hmm, it looks the recommended qt version ist from 2014 - that was BEFORE Windows 10, AFAIR. So maybe you could try a Windows 7, just for building the packages. I do not know how Mihai is creating packages.
Uli
On Tue, Dec 8, 2020 at 1:51 PM Maarten Boekhold <boekhold@gmx.com> wrote:
Hi all,
Today I've tried to set up a build environment on my Windows 10 laptop so I can (try to) debug this. I've tried to follow the instructions from:
https://wiki.x2go.org/doku.php/wiki:development:build-howto-mswin:x2goclient
However it fails at the step where you need to compile the static version of Qt. The QT build system doesn't seem to support the specific Windows version, as I'm getting the following build error:
$ ./configure -release -static -openssl -qt-style-windowsxp -qt-style-windowsvista Which edition of Qt do you want to use ?
Type 'c' if you want to use the Commercial Edition. Type 'o' if you want to use the Open Source Edition.
o
-qt-style-windowsxp: invalid command-line switch -qt-style-windowsvista: invalid command-line switch
The specified system/compiler port is not complete:
/c/Qt/4.8.6/mkspecs//qplatformdefs.hPlease use the contact form at http://qt.digia.com/contact-us
Note the empty path between the "mkspecs" and "qplatformdefs.h" directories. There is supposed to be a symbolic name there identifying the type of system.
Does anybody have any updated build instructions for x2goclient on Windows? Or did I just miss something obvious?
Maarten
On 9/9/2020 11:55 AM, Maarten Boekhold wrote:
Package: x2goclient Version: 4.1.2.2
Windows 10, x2goclient 4.1.2.2
When resuming a "paused" x2Go session, x2goclient is using the wrong X-Server settings.
I have configured my x2goclient with the following settings for X.Org Server settings:
**X.Org Server settings** [X] use custom X-Server Executable: C:/Program Files (x86)/x2goclient/VcXsrv/vcxsrv.exe [ ] start X-Server on X2Go Client start
Window mode: -screen 0 %wx%h -notrayicon -clipboard -keyhook
-nowinkill -nopn -silent-dup-error Fullscreen mode: -fullscreen -notrayicon -clipboard -keyhook
-nowinkill -nopn -silent-dup-error Single application: -multiwindow -notrayicon -clipboard
-keyhook -nowinkill -nopn -silent-dup-error Whole display: -nodecoration -notrayicon -clipboard -keyhook
-nopn -silent-dup-error -screen 0 @My x2goclient session is configured as:
**Session preferences: Input/Output** [ ] Fullscreen [ ] Custom Width (greyed out 3696) Height (greyed out 2160) [X] Use whole display [ ] Maximum available Display: 2
When I start a new x2Go session, it correctly runs the X-Server with the "Whole display" command (as per Windows Task Manager):
"C:\Program Files (x86)\x2goclient\VcXsrv\vcxsrv.exe"
-nodecoration -notrayicon -clipboard -keyhook -nowinkill
-nopn -silent-dup-error screen 0 @2 :0But if I then "pause" this session and reconnect, x2goclient uses the "Window mode" command line options instead:
"C:\Program Files (x86)\x2goclient\VcXsrv\vcxsrv.exe"
-screen 3696x2160 -notrayicon -clipboard -keyhook
-nowinkill -nopn -silent-dup-error :0I suspect this has something to do with the code around line 4442 in onmainwindow.cpp, but I've not been able to figure out the exact details yet.
Maarten
x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
Hi,
Indeed, Qt4 is not supported on Windows 10 at all, as the latest Qt 4.8.x release happened before the Windows 10 release. In fact, Qt 4 is EOL:
https://forum.qt.io/topic/81521/build-qt-4-8-7-on-windows-10-platform https://doc.qt.io/archives/qt-4.8/supported-platforms.html
No idea how much effort this would take, but would it make sense to release a new version of x2goclient that is built with Qt5.x?
https://doc.qt.io/qt-5/supported-platforms.html
This would drop support for Windows XP, but I think nobody would cry about that... @Mihai?
Maarten
ps. Qt6 was released yesterday, which also drops support for Windows 7. Suppose that would be a bit too radical :)
On 12/8/2020 5:37 PM, Ulrich Sibiller wrote:
Hmm, it looks the recommended qt version ist from 2014 - that was BEFORE Windows 10, AFAIR. So maybe you could try a Windows 7, just for building the packages. I do not know how Mihai is creating packages.
Uli
On Tue, Dec 8, 2020 at 1:51 PM Maarten Boekhold <boekhold@gmx.com> wrote:
Hi all,
Today I've tried to set up a build environment on my Windows 10 laptop so I can (try to) debug this. I've tried to follow the instructions from:
https://wiki.x2go.org/doku.php/wiki:development:build-howto-mswin:x2goclient
However it fails at the step where you need to compile the static version of Qt. The QT build system doesn't seem to support the specific Windows version, as I'm getting the following build error:
$ ./configure -release -static -openssl -qt-style-windowsxp -qt-style-windowsvista Which edition of Qt do you want to use ?
Type 'c' if you want to use the Commercial Edition. Type 'o' if you want to use the Open Source Edition.
o
-qt-style-windowsxp: invalid command-line switch -qt-style-windowsvista: invalid command-line switch
The specified system/compiler port is not complete: /c/Qt/4.8.6/mkspecs//qplatformdefs.h Please use the contact form at http://qt.digia.com/contact-usNote the empty path between the "mkspecs" and "qplatformdefs.h" directories. There is supposed to be a symbolic name there identifying the type of system.
Does anybody have any updated build instructions for x2goclient on Windows? Or did I just miss something obvious?
Maarten
On 9/9/2020 11:55 AM, Maarten Boekhold wrote:
Package: x2goclient Version: 4.1.2.2
Windows 10, x2goclient 4.1.2.2
When resuming a "paused" x2Go session, x2goclient is using the wrong X-Server settings.
I have configured my x2goclient with the following settings for X.Org Server settings:
**X.Org Server settings** [X] use custom X-Server Executable: C:/Program Files (x86)/x2goclient/VcXsrv/vcxsrv.exe [ ] start X-Server on X2Go Client start
Window mode: -screen 0 %wx%h -notrayicon -clipboard -keyhook
-nowinkill -nopn -silent-dup-error Fullscreen mode: -fullscreen -notrayicon -clipboard -keyhook
-nowinkill -nopn -silent-dup-error Single application: -multiwindow -notrayicon -clipboard
-keyhook -nowinkill -nopn -silent-dup-error Whole display: -nodecoration -notrayicon -clipboard -keyhook
-nopn -silent-dup-error -screen 0 @My x2goclient session is configured as:
**Session preferences: Input/Output** [ ] Fullscreen [ ] Custom Width (greyed out 3696) Height (greyed out 2160) [X] Use whole display [ ] Maximum available Display: 2
When I start a new x2Go session, it correctly runs the X-Server with the "Whole display" command (as per Windows Task Manager):
"C:\Program Files (x86)\x2goclient\VcXsrv\vcxsrv.exe"
-nodecoration -notrayicon -clipboard -keyhook -nowinkill
-nopn -silent-dup-error screen 0 @2 :0But if I then "pause" this session and reconnect, x2goclient uses the "Window mode" command line options instead:
"C:\Program Files (x86)\x2goclient\VcXsrv\vcxsrv.exe"
-screen 3696x2160 -notrayicon -clipboard -keyhook
-nowinkill -nopn -silent-dup-error :0I suspect this has something to do with the code around line 4442 in onmainwindow.cpp, but I've not been able to figure out the exact details yet.
Maarten
x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
Well, on my debian table system x2goclient is linked against qt5 so the code is prepared for that. Maybe the instructions are simply outdated? Have you tried compiling with qt5?
Uli
On Wed, Dec 9, 2020 at 10:03 AM Maarten Boekhold <boekhold@gmx.com> wrote:
Hi,
Indeed, Qt4 is not supported on Windows 10 at all, as the latest Qt 4.8.x release happened before the Windows 10 release. In fact, Qt 4 is EOL:
https://forum.qt.io/topic/81521/build-qt-4-8-7-on-windows-10-platform https://doc.qt.io/archives/qt-4.8/supported-platforms.html
No idea how much effort this would take, but would it make sense to release a new version of x2goclient that is built with Qt5.x?
https://doc.qt.io/qt-5/supported-platforms.html
This would drop support for Windows XP, but I think nobody would cry about that... @Mihai?
Maarten
ps. Qt6 was released yesterday, which also drops support for Windows 7. Suppose that would be a bit too radical :)
On 12/8/2020 5:37 PM, Ulrich Sibiller wrote:
Hmm, it looks the recommended qt version ist from 2014 - that was BEFORE Windows 10, AFAIR. So maybe you could try a Windows 7, just for building the packages. I do not know how Mihai is creating packages.
Uli
On Tue, Dec 8, 2020 at 1:51 PM Maarten Boekhold <boekhold@gmx.com> wrote:
Hi all,
Today I've tried to set up a build environment on my Windows 10 laptop so I can (try to) debug this. I've tried to follow the instructions from:
https://wiki.x2go.org/doku.php/wiki:development:build-howto-mswin:x2goclient
However it fails at the step where you need to compile the static version of Qt. The QT build system doesn't seem to support the specific Windows version, as I'm getting the following build error:
$ ./configure -release -static -openssl -qt-style-windowsxp -qt-style-windowsvista Which edition of Qt do you want to use ?
Type 'c' if you want to use the Commercial Edition. Type 'o' if you want to use the Open Source Edition.
o
-qt-style-windowsxp: invalid command-line switch -qt-style-windowsvista: invalid command-line switch
The specified system/compiler port is not complete: /c/Qt/4.8.6/mkspecs//qplatformdefs.h Please use the contact form at http://qt.digia.com/contact-usNote the empty path between the "mkspecs" and "qplatformdefs.h" directories. There is supposed to be a symbolic name there identifying the type of system.
Does anybody have any updated build instructions for x2goclient on Windows? Or did I just miss something obvious?
Maarten
On 9/9/2020 11:55 AM, Maarten Boekhold wrote:
Package: x2goclient Version: 4.1.2.2
Windows 10, x2goclient 4.1.2.2
When resuming a "paused" x2Go session, x2goclient is using the wrong X-Server settings.
I have configured my x2goclient with the following settings for X.Org Server settings:
**X.Org Server settings** [X] use custom X-Server Executable: C:/Program Files (x86)/x2goclient/VcXsrv/vcxsrv.exe [ ] start X-Server on X2Go Client start
Window mode: -screen 0 %wx%h -notrayicon -clipboard -keyhook
-nowinkill -nopn -silent-dup-error Fullscreen mode: -fullscreen -notrayicon -clipboard -keyhook
-nowinkill -nopn -silent-dup-error Single application: -multiwindow -notrayicon -clipboard
-keyhook -nowinkill -nopn -silent-dup-error Whole display: -nodecoration -notrayicon -clipboard -keyhook
-nopn -silent-dup-error -screen 0 @My x2goclient session is configured as:
**Session preferences: Input/Output** [ ] Fullscreen [ ] Custom Width (greyed out 3696) Height (greyed out 2160) [X] Use whole display [ ] Maximum available Display: 2
When I start a new x2Go session, it correctly runs the X-Server with the "Whole display" command (as per Windows Task Manager):
"C:\Program Files (x86)\x2goclient\VcXsrv\vcxsrv.exe"
-nodecoration -notrayicon -clipboard -keyhook -nowinkill
-nopn -silent-dup-error screen 0 @2 :0But if I then "pause" this session and reconnect, x2goclient uses the "Window mode" command line options instead:
"C:\Program Files (x86)\x2goclient\VcXsrv\vcxsrv.exe"
-screen 3696x2160 -notrayicon -clipboard -keyhook
-nowinkill -nopn -silent-dup-error :0I suspect this has something to do with the code around line 4442 in onmainwindow.cpp, but I've not been able to figure out the exact details yet.
Maarten
x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
You won't have any problems building X2go client on win 10 using qt5. No need to rebuild qt neither. All you need to do is to put libssh headers and libs to mingw directory. Regards, Alex
Am 9. Dezember 2020 03:02:55 GMT-06:00 schrieb Maarten Boekhold <boekhold@gmx.com>:
Hi,
Indeed, Qt4 is not supported on Windows 10 at all, as the latest Qt 4.8.x release happened before the Windows 10 release. In fact, Qt 4 is EOL:
https://forum.qt.io/topic/81521/build-qt-4-8-7-on-windows-10-platform https://doc.qt.io/archives/qt-4.8/supported-platforms.html
No idea how much effort this would take, but would it make sense to release a new version of x2goclient that is built with Qt5.x?
https://doc.qt.io/qt-5/supported-platforms.html
This would drop support for Windows XP, but I think nobody would cry about that... @Mihai?
Maarten
ps. Qt6 was released yesterday, which also drops support for Windows 7. Suppose that would be a bit too radical :)
Hmm, it looks the recommended qt version ist from 2014 - that was BEFORE Windows 10, AFAIR. So maybe you could try a Windows 7, just for building the packages. I do not know how Mihai is creating packages.
Uli
On Tue, Dec 8, 2020 at 1:51 PM Maarten Boekhold <boekhold@gmx.com> wrote:
Hi all,
Today I've tried to set up a build environment on my Windows 10 laptop so I can (try to) debug this. I've tried to follow the instructions from:
https://wiki.x2go.org/doku.php/wiki:development:build-howto-mswin:x2goclient
However it fails at the step where you need to compile the static
version of Qt. The QT build system doesn't seem to support the specific Windows version, as I'm getting the following build error:
$ ./configure -release -static -openssl -qt-style-windowsxp
-qt-style-windowsvista
Which edition of Qt do you want to use ?
Type 'c' if you want to use the Commercial Edition. Type 'o' if you want to use the Open Source Edition.
o
-qt-style-windowsxp: invalid command-line switch -qt-style-windowsvista: invalid command-line switch
The specified system/compiler port is not complete: /c/Qt/4.8.6/mkspecs//qplatformdefs.h Please use the contact form at http://qt.digia.com/contact-usNote the empty path between the "mkspecs" and "qplatformdefs.h"
Does anybody have any updated build instructions for x2goclient on
Windows? Or did I just miss something obvious?
Maarten
On 9/9/2020 11:55 AM, Maarten Boekhold wrote:
Package: x2goclient Version: 4.1.2.2
Windows 10, x2goclient 4.1.2.2
When resuming a "paused" x2Go session, x2goclient is using the wrong X-Server settings.
I have configured my x2goclient with the following settings for X.Org Server settings:
**X.Org Server settings** [X] use custom X-Server Executable: C:/Program Files (x86)/x2goclient/VcXsrv/vcxsrv.exe [ ] start X-Server on X2Go Client start
Window mode: -screen 0 %wx%h -notrayicon -clipboard -keyhook
-nowinkill -nopn -silent-dup-error Fullscreen mode: -fullscreen -notrayicon -clipboard -keyhook
-nowinkill -nopn -silent-dup-error Single application: -multiwindow -notrayicon -clipboard
-keyhook -nowinkill -nopn -silent-dup-error Whole display: -nodecoration -notrayicon -clipboard -keyhook
-nopn -silent-dup-error -screen 0 @My x2goclient session is configured as:
**Session preferences: Input/Output** [ ] Fullscreen [ ] Custom Width (greyed out 3696) Height (greyed out 2160) [X] Use whole display [ ] Maximum available Display: 2
When I start a new x2Go session, it correctly runs the X-Server with
"Whole display" command (as per Windows Task Manager):
"C:\Program Files (x86)\x2goclient\VcXsrv\vcxsrv.exe"
-nodecoration -notrayicon -clipboard -keyhook -nowinkill
-nopn -silent-dup-error screen 0 @2 :0But if I then "pause" this session and reconnect, x2goclient uses
On 12/8/2020 5:37 PM, Ulrich Sibiller wrote: directories. There is supposed to be a symbolic name there identifying the type of system. the the
"Window mode" command line options instead:
"C:\Program Files (x86)\x2goclient\VcXsrv\vcxsrv.exe"
-screen 3696x2160 -notrayicon -clipboard -keyhook
-nowinkill -nopn -silent-dup-error :0I suspect this has something to do with the code around line 4442 in onmainwindow.cpp, but I've not been able to figure out the exact details yet.
Maarten
x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
-- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
Hi,
I'll see if I can give it a try this weekend. Annoyingly, it seems you need to create a Qt account in order to be able to run the Qt5 installer, even for the Open Source version (and even with the offline installer!).
Maarten
On 12/9/2020 3:56 PM, Oleksandr Shneyder wrote:
You won't have any problems building X2go client on win 10 using qt5. No need to rebuild qt neither. All you need to do is to put libssh headers and libs to mingw directory. Regards, Alex
Am 9. Dezember 2020 03:02:55 GMT-06:00 schrieb Maarten Boekhold <boekhold@gmx.com>:
Hi,
Indeed, Qt4 is not supported on Windows 10 at all, as the latest Qt 4.8.x release happened before the Windows 10 release. In fact, Qt 4 is EOL:
https://forum.qt.io/topic/81521/build-qt-4-8-7-on-windows-10-platform https://doc.qt.io/archives/qt-4.8/supported-platforms.html
No idea how much effort this would take, but would it make sense to release a new version of x2goclient that is built with Qt5.x?
https://doc.qt.io/qt-5/supported-platforms.html
This would drop support for Windows XP, but I think nobody would cry about that... @Mihai?
Maarten
ps. Qt6 was released yesterday, which also drops support for Windows 7. Suppose that would be a bit too radical :)
Hmm, it looks the recommended qt version ist from 2014 - that was BEFORE Windows 10, AFAIR. So maybe you could try a Windows 7, just for building the packages. I do not know how Mihai is creating packages.
Uli
On Tue, Dec 8, 2020 at 1:51 PM Maarten Boekhold <boekhold@gmx.com> wrote:
Hi all,
Today I've tried to set up a build environment on my Windows 10 laptop so I can (try to) debug this. I've tried to follow the instructions from:
https://wiki.x2go.org/doku.php/wiki:development:build-howto-mswin:x2goclient
However it fails at the step where you need to compile the static version of Qt. The QT build system doesn't seem to support the specific Windows version, as I'm getting the following build error: $ ./configure -release -static -openssl -qt-style-windowsxp -qt-style-windowsvista Which edition of Qt do you want to use ?
Type 'c' if you want to use the Commercial Edition. Type 'o' if you want to use the Open Source Edition.
o
-qt-style-windowsxp: invalid command-line switch -qt-style-windowsvista: invalid command-line switch
The specified system/compiler port is not complete: /c/Qt/4.8.6/mkspecs//qplatformdefs.h Please use the contact form at http://qt.digia.com/contact-usNote the empty path between the "mkspecs" and "qplatformdefs.h"
Does anybody have any updated build instructions for x2goclient on Windows? Or did I just miss something obvious? Maarten
On 9/9/2020 11:55 AM, Maarten Boekhold wrote:
Package: x2goclient Version: 4.1.2.2
Windows 10, x2goclient 4.1.2.2
When resuming a "paused" x2Go session, x2goclient is using the wrong X-Server settings.
I have configured my x2goclient with the following settings for X.Org Server settings:
**X.Org Server settings** [X] use custom X-Server Executable: C:/Program Files (x86)/x2goclient/VcXsrv/vcxsrv.exe [ ] start X-Server on X2Go Client start
Window mode: -screen 0 %wx%h -notrayicon -clipboard -keyhook
-nowinkill -nopn -silent-dup-error Fullscreen mode: -fullscreen -notrayicon -clipboard -keyhook
-nowinkill -nopn -silent-dup-error Single application: -multiwindow -notrayicon -clipboard
-keyhook -nowinkill -nopn -silent-dup-error Whole display: -nodecoration -notrayicon -clipboard -keyhook
-nopn -silent-dup-error -screen 0 @My x2goclient session is configured as:
**Session preferences: Input/Output** [ ] Fullscreen [ ] Custom Width (greyed out 3696) Height (greyed out 2160) [X] Use whole display [ ] Maximum available Display: 2
When I start a new x2Go session, it correctly runs the X-Server with
"Whole display" command (as per Windows Task Manager):
"C:\Program Files (x86)\x2goclient\VcXsrv\vcxsrv.exe"
-nodecoration -notrayicon -clipboard -keyhook -nowinkill
-nopn -silent-dup-error screen 0 @2 :0But if I then "pause" this session and reconnect, x2goclient uses
On 12/8/2020 5:37 PM, Ulrich Sibiller wrote: directories. There is supposed to be a symbolic name there identifying the type of system. the the
"Window mode" command line options instead:
"C:\Program Files (x86)\x2goclient\VcXsrv\vcxsrv.exe"
-screen 3696x2160 -notrayicon -clipboard -keyhook
-nowinkill -nopn -silent-dup-error :0I suspect this has something to do with the code around line 4442 in onmainwindow.cpp, but I've not been able to figure out the exact details yet.
Maarten
x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
-
Maarten Boekhold -
Oleksandr Shneyder -
Ulrich Sibiller -
Ulrich Sibiller