Hi list,
I'd like to start a quick and informal poll:
From what I can tell, Mac OS X 10.5 is no longer supported by Apple (i.e. no new security fixes will be provided etc.).
Miha is currently developing on Mac OS X 10.6, and cross-checking on my Mac Mini with Mac OS X 10.5 to see if everything works there, too.
At present, we do not seem to have anybody developing/checking on Mac OS 10.7, which is the current Mac OS X release.
If we could agree on dropping support for 10.5, I would upgrade my Mac Mini to 10.7, or, should it turn out to be too slow for 10.7, we might arrange for Miha to upgrade his Mac to 10.7 and I'd upgrade to 10.6.
Of course, if the majority of our Mac users is still on 10.5, we'd shoot ourselves in the foot by dropping support for it.
So, please speak up and let us know which version you are using, and in what numbers (especially those of you offering commercial support to clients on Mac OS X)!
-Stefan
Hi Stefan,
i can do the 10.7 tests for mihai. the latest version is running under 10.7.
Stephan
Am 16.04.2012 um 13:28 schrieb Stefan Baur:
Stephan Diehl Geschäftsführer
Open Solutions GmbH & Co. KG Luisenweg 109 20537 Hamburg
Fon: 040 / 7070806 - 70 Mail: stephan.diehl@opensolutions.net
Registergericht: Amtsgericht Hamburg, HRA 105 704 Persönlich haftende Gesellschafterin: Open Solutions GmbH Registergericht: Amtsgericht Hamburg, HRB 999 00 Geschäftsführer: Stephan Diehl USt-Id-Nr: DE253775678; Steuer-Nr: 46/649/00349
Hello Dear X2Go users,
X2Go Client 3.99.2.1-rc1 for windows is ready for testing.
This version have some elements updated: nxcomp+nxproxy - recent version from GIT pulseaudio - 1.1 Vcxsrv - 1.12.0.1 build with Qt-4.8.1
download under: http://code.x2go.org/releases/binary-win32/x2goclient/x2goclient-3.99.2.1-rc...
Please test and give feedback
Oleksandr Shneyder Dipl. Informatik X2go Core Developer Team
email: oleksandr.shneyder@obviously-nice.de web: www.obviously-nice.de
--> X2go - everywhere@home
Am 16.04.2012 14:41, schrieb Oleksandr Shneyder:
Hello Dear X2Go users,
X2Go Client 3.99.2.1-rc1 for windows is ready for testing.
Please test and give feedback
Problem: Sound is not working after reconnect or client reboot
Steps to reproduce:
Effect: Browser stalls as it has no pulseaudio to connect to.
Workaround: x2goclient.exe should check for the presence of the file
%USERPROFILE%\.x2go\pulse\.pulse\%COMPUTERNAME%-runtime\pid
and delete it during x2goclient.exe's initialization phase.
IOW: It should only happen the monent x2goclient.exe starts, not every time you pick a new session from the sessions list when x2goclient.exe is already running.
I'm not sure if that's the proper solution to the problem, so I'm tagging it "workaround".
-Stefan
Am 16.04.2012 18:03, schrieb Stefan Baur:
Hello Stefan,
Can you check in your task manager if pulseaudio running on the client while your firefox hanging? I can imagine that it's not an x2go problem. Flash player can open connection to pulseaudio server and if you closing X2Go Client the server exists not any more. It can happens if you not closing your browser before suspending session. After new start of client you can not simple resume connection to pulse server, you should open a new one.
-- Oleksandr Shneyder Dipl. Informatik X2go Core Developer Team
email: oleksandr.shneyder@obviously-nice.de web: www.obviously-nice.de
--> X2go - everywhere@home
Hi Alex,
I believe you're looking for the problem in the wrong location. (Or maybe you misunderstood my bug report.) The way I see it, pulseaudio on the client just flat out refuses to run while %USERPROFILE%\.x2go\pulse\.pulse\%COMPUTERNAME%-runtime\pid exists.
Proof for my theory: When I close all x2goclient.exe-related tasks (ssh and whatnot) and run x2goclient.exe again I still have no sound when reconnecting.
BUT: as soon as I close x2goclient.exe, manually delete the pid file and restart x2goclient.exe, I *do* have working sound when reconnecting.
Of course, suspending *while the video is running* will have the effect described by you, but that's *not* the issue I'm reporting. I'm waiting for the video to finish (I was originally tryingo to find out if the pulseaudio stability issues when playing long videos are gone), so there is no active application like flashplayer trying to push data to pulseaudio.
-Stefan
Am 16.04.2012 18:54, schrieb Oleksandr Shneyder:
Am 16.04.2012 19:25, schrieb Stefan Baur:
okay, it's strange. This why I asked you if you can see pulseaudio in task manager :) In my case there is no problem starting pulseaudio if %USERPROFILE%\.x2go\pulse\.pulse\%COMPUTERNAME%-runtime\pid exists and I cannot reproduce your issue. I'll provide you a new binary tomorrow and you can check if the problem still exists.
Oleksandr Shneyder Dipl. Informatik X2go Core Developer Team
email: oleksandr.shneyder@obviously-nice.de web: www.obviously-nice.de
--> X2go - everywhere@home
Am 16.04.2012 21:05, schrieb Oleksandr Shneyder: [......]
Hello Stefan,
please test this version: http://code.x2go.org/releases/binary-win32/x2goclient/x2goclient-3.99.2.1-rc...
Oleksandr Shneyder Dipl. Informatik X2go Core Developer Team
email: oleksandr.shneyder@obviously-nice.de web: www.obviously-nice.de
--> X2go - everywhere@home
Am 17.04.2012 12:28, schrieb Oleksandr Shneyder:
Seems to fix this particular issue. I tried closing and re-opening client, no more issues. Haven't tried rebooting yet, and haven't looked for more bugs. Will keep testing...
-Stefan
Am 17.04.2012 12:28, schrieb Oleksandr Shneyder:
please test this version: http://code.x2go.org/releases/binary-win32/x2goclient/x2goclient-3.99.2.1-rc...
I am unable to start the client on Windows XP (it works on Windows 7 and Vista):
Googling this error number reveals that you should switch from debug to release build when building/compiling.
This is a serious issue - I have at least 350 clients still running XP (which is still officially supported by M$, unlike Mac OS X 10.5 by Apple *wink*).
Aside from that, the client looks good on Vista and 7, no more sound issues.
@Alex can you try to fix this issue ASAP? If you could provide me a -rc3 today that does not introduce further changes, I can check if it works on XP and give you feedback today (assuming you're planning an official release day today).
-Stefan
Hi Stefan,
On Mi 18 Apr 2012 12:57:03 CEST Stefan Baur wrote:
This sound like a VC++-redistributable runtime issue. I had the same
effect with PyHoca-GUI. I have not dived fully into that, but placing
this file into the folder
%programfiles%<application>Microsoft.VC90.CRT solved my Python
specific issue...
http://code.x2go.org/gitweb?p=pyhoca-contrib.git;a=blob;f=mswin/ms-vc-runtim...
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Hi Stefan,
On Mi 18 Apr 2012 14:47:45 CEST Stefan Baur wrote:
For PyHoca-GUI the files get shipped in
%ProgramFiles%PyHoca-GUIMicrosoft.VC90.CRT. So, in PyHoca-GUI case, no
system path.
I am not sure if X2Go Client uses the VC++ redist pack, so let's wait
for Alex...
Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Am 18.04.2012 15:06, schrieb Mike Gabriel:
Duh! Sorry, brain fart. I was thinking of %SystemRoot%. Indeed, if the file simply has to reside in the same directory as x2goclient.exe, this should work with portable mode as well.
-Stefan
Am 18.04.2012 18:21, schrieb John A. Sullivan III:
This could be because you have the files listed here http://code.x2go.org/gitweb?p=pyhoca-contrib.git;a=tree;f=mswin/ms-vc-runtim... elsewhere on the machine... (Assuming it is due to the reason Mike suggested in his reply.)
Do you think you could cross-check on a fresh XP Professional SP3 install (no other applications installed) and http://code.x2go.org/releases/binary-win32/x2goclient/x2goclient-3.99.2.1-rc...
-Stefan
Am 18.04.2012 18:25, schrieb Stefan Baur:
I've build this version on our new build server (W7) installed by Mike(thank you once again, Mike). This is a release build, not debug. I have no Windows XP to try it.
@list: have any one else issues running recent X2Go Client on Windows XP?
Oleksandr Shneyder Dipl. Informatik X2go Core Developer Team
email: oleksandr.shneyder@obviously-nice.de web: www.obviously-nice.de
--> X2go - everywhere@home
No problems running 3.99.2.1-rc2 on Windows XP. I have VC2005/VC2008/VC2010 redists all installed.
Cheers, Daniel
Am 18.04.2012 21:22, schrieb Oleksandr Shneyder:
I experimented a bit: It takes two files from http://code.x2go.org/gitweb?p=pyhoca-contrib.git;a=tree;f=mswin/ms-vc-runtim...
Microsoft.VC90.CRT.manifest msvcr90.dll
If I copy these into the x2goclient directory, the new client works (as in, starts up - haven't tried connecting yet) on XP, too.
What's strange is that the other two DLL files are not needed even though they are referenced in the manifest file.
@Alex + @Mike: Could you please work this out together? I'm not sure if all that is needed is to include these files into the archive that the installer unpacks into the x2goclient folder, or if that is an ugly hack.
Daniel Lindgren wrote:
No problems running 3.99.2.1-rc2 on Windows XP. I have VC2005/VC2008/VC2010 redists all installed.
So I guess the general question is: Can (=legal?) and should (=proper way of handling this issue?) we include the DLL/manifest files in the installer, or should we require the installation of the VC<something> redists/pull their official installer along and run it from within ours? Requiring the redists/forching their install through our installer probably will break portable mode, though, as it will install the files to the system directory and not the x2go directory...
Further info: The last installer to run on XP without this hack is: x2goclient-3.99.2.0-rc2-setup.exe
-Stefan
Hi Stefan,
On Do 19 Apr 2012 11:01:58 CEST Stefan Baur wrote:
The VC++ runtime library files can be re-distributed with X2Go Client
if needed. That's what they are for.
http://www.microsoft.com/download/en/details.aspx?id=29
However, there are different version of these library files available.
I ship the 2008 version as Python 2.7 is linked against that. Not sure
which component of X2Go Client relies on the redist-VC++-libs... not
sure what version either.
On systems that have the right version of redist-VC++-libs this bug
does not become evident.
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Am 19.04.2012 12:13, schrieb Mike Gabriel:
And this link is exactly what gets me worried. They are offering an installer for these files - so are we only allowed to redistribute the installer, which then has to run during x2goclient's setup (=goodbye setup-free portable mode), or are we allowed to redistribute individual files as well?
Well, I simply copied the ones you have in git and it worked. But I'm sure Alex will be able to tell us more about that if needed.
On systems that have the right version of redist-VC++-libs this bug does not become evident.
Which seems to be the case on stock installs (with current service packs/patches) of Windows Vista and Windows 7. XP (even with Service Pack 3) is too old, though.
Kinda funny, though: Vista was released in January 2007, VC++2008 in November 2007. So why it brings along VC++2008 redist support is beyond me.
-Stefan
Am 19.04.2012 11:01, schrieb Stefan Baur:
This version was built under Windows XP. Recent versions are built under Windows 7. I don't really like an Idea to provide msvcr90.dll with X2Go Client. It seems, that binaries built under Windows XP working without problem also on Windows 7. But I don't also like Idea to give up build environment that Mike built and install WindowsXP instead. I don't really know what is better. Any ideas?
Oleksandr Shneyder Dipl. Informatik X2go Core Developer Team
email: oleksandr.shneyder@obviously-nice.de web: www.obviously-nice.de
--> X2go - everywhere@home
Am 19.04.2012 21:17, schrieb Oleksandr Shneyder:
Out of curiosity, were you using the same Visual C++ build environment on XP and on Windows 7? If not, maybe it would be possible to install the old Visual C++ environment on the Windows 7 host?
Microsoft support for XP will end August 4, 2014, so we have to support this OS/x2goclient combination for a little more than two years - somehow.
-Stefan
Am 19.04.2012 21:34, schrieb Stefan Baur:
I don't using Visual C++ for building X2Go Client and don't have Visual Studio installed at all. This msvcr90.dll is kind of system library, I think.
Oleksandr Shneyder Dipl. Informatik X2go Core Developer Team
email: oleksandr.shneyder@obviously-nice.de web: www.obviously-nice.de
--> X2go - everywhere@home
Am 19.04.2012 21:45, schrieb Oleksandr Shneyder:
*Something* that you*re using to build the client insists on this library though, and it didn't do so when you built it on XP.
I could try to sniff out the old client to check if it attempts to use older versions of the same DLL (which could, in theory, be present on a default XP install), would that help?
-Stefan