Package: x2goclient Severity: critical Version: 4.0.2.1
x2goclient-4.0.2.1+hotfix1+build3-setup.exe does not install VcXsrv/zlib1.dll, which leads X2Go Client to fail to connect with "Can't start X Server / Please check your installation". You can also check by running vcxsrv.exe and seeing the missing-DLL dialog.
This worked fine with x2goclient-4.0.2.0-setup.exe
Thanks,
Ivan
Am 29.08.2014 um 09:08 schrieb Ivan Kozik:
Package: x2goclient Severity: critical Version: 4.0.2.1
x2goclient-4.0.2.1+hotfix1+build3-setup.exe does not install VcXsrv/zlib1.dll, which leads X2Go Client to fail to connect with "Can't start X Server / Please check your installation". You can also check by running vcxsrv.exe and seeing the missing-DLL dialog.
This worked fine with x2goclient-4.0.2.0-setup.exe
Unable to confirm (Windows 7 x86). Fresh install of x2goclient-4.0.2.1+hotfix1+build3-setup.exe, running the actual setup.
zlib1.dll *is* there, it's in the x2goclient main directory, though. Not in the VcXsrv subdirectory. x2goclient connects just fine and starts VcXsrv.
If you're missing the zlib1.dll, check that you don't have an overzealous virus scanner that might have quarantined it by accident.
-Stefan
(Sending again to the right address, sorry)
On Fri, Aug 29, 2014 at 9:20 AM, Stefan Baur <x2go-ml-1@baur-itcs.de> wrote:
Unable to confirm (Windows 7 x86). Fresh install of x2goclient-4.0.2.1+hotfix1+build3-setup.exe, running the actual setup.
zlib1.dll *is* there, it's in the x2goclient main directory, though. Not in the VcXsrv subdirectory.
I do have a zlib1.dll in the x2goclient main directory, but that wasn't enough to make VcXsrv work.
x2goclient connects just fine and starts VcXsrv.
I found the problem: it looks like it works only when you start x2goclient with the current directory set to the install directory (in my case, "C:\Program Files (x86)\x2goclient"). It does ship with a working shortcut, but I made my own that didn't set up the cwd properly.
In my case, it was because runas didn't pass through the "Start In" directory:
C:\Windows\System32\runas.exe /savecred /profile /user:x2go "C:\Program Files (x86)\x2goclient\x2goclient.exe"
but it can also happen if you just have the wrong "Start In" directory on the shortcut.
Control: close -1 Control: tag -1 not-a-bug
On Fr 29 Aug 2014 11:49:23 CEST, Ivan Kozik wrote:
(Sending again to the right address, sorry)
On Fri, Aug 29, 2014 at 9:20 AM, Stefan Baur <x2go-ml-1@baur-itcs.de> wrote:
Unable to confirm (Windows 7 x86). Fresh install of x2goclient-4.0.2.1+hotfix1+build3-setup.exe, running the actual setup.
zlib1.dll *is* there, it's in the x2goclient main directory, though. Not in the VcXsrv subdirectory.
I do have a zlib1.dll in the x2goclient main directory, but that wasn't enough to make VcXsrv work.
x2goclient connects just fine and starts VcXsrv.
I found the problem: it looks like it works only when you start x2goclient with the current directory set to the install directory (in my case, "C:\Program Files (x86)\x2goclient"). It does ship with a working shortcut, but I made my own that didn't set up the cwd properly.
In my case, it was because runas didn't pass through the "Start In"
directory:C:\Windows\System32\runas.exe /savecred /profile /user:x2go "C:\Program Files (x86)\x2goclient\x2goclient.exe"
but it can also happen if you just have the wrong "Start In" directory on the shortcut.
Thanks for reporting your observed issue.
I close this bug as the problem seems to be related to your setup.
Launching X2Go Client always requires to cwd to its installation
directory, otherwise its DLLs will not be found.
We won't register the shipped cygwin-based DLLs system-wide as the
danger of interference with other cygwin-based applications is too high.
Mike
--
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On Fri, Aug 29, 2014 at 11:04 AM, Mike Gabriel <mike.gabriel@das-netzwerkteam.de> wrote:
Thanks for reporting your observed issue.
I close this bug as the problem seems to be related to your setup.
Launching X2Go Client always requires to cwd to its installation directory, otherwise its DLLs will not be found.
I don't think this is true - like almost all programs, x2goclient.exe starts fine with an incorrect cwd. The problem arises only when x2goclient tries to start VcXsrv.
Also, it's rather hard to figure out the source of the problem from the "Can't start X Server / Please check your installation" message.
Processing control commands:
close -1 Bug #587 [x2goclient] x2goclient is missing VcXsrv/zlib1.dll Marked Bug as done tag -1 not-a-bug Bug #587 {Done: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>} [x2goclient] x2goclient is missing VcXsrv/zlib1.dll Added tag(s) not-a-bug.
-- 587: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=587 X2Go Bug Tracking System Contact owner@bugs.x2go.org with problems
Processing control commands:
reopen -1 Bug #587 [x2goclient] x2goclient is missing VcXsrv/zlib1.dll Bug 587 is not marked as done; doing nothing. tag -1 - not-a-bug Bug #587 [x2goclient] x2goclient is missing VcXsrv/zlib1.dll Ignoring request to alter tags of bug #587 to the same tags previously set
-- 587: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=587 X2Go Bug Tracking System Contact owner@bugs.x2go.org with problems
Processing control commands:
tags 587 build-win32 Bug #587 [x2goclient] x2goclient is missing VcXsrv/zlib1.dll Added tag(s) build-win32.
-- 587: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=587 X2Go Bug Tracking System Contact owner@bugs.x2go.org with problems
Processing control commands:
fixed -1 4.0.2.1+hotfix1+build4 Bug #587 [x2goclient] x2goclient is missing VcXsrv/zlib1.dll There is no source info for the package 'x2goclient' at version '4.0.2.1+hotfix1+build4' with architecture '' Unable to make a source version for version '4.0.2.1+hotfix1+build4' Marked as fixed in versions 4.0.2.1+hotfix1+build4.
-- 587: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=587 X2Go Bug Tracking System Contact owner@bugs.x2go.org with problems