Ok, another update after 24 hours more of trial-and-error:

I have tried many combinations and STILL no gnome desktop for Likewise users! I don't understand it, I have tried: -10.10 maverick with Likewise 6.0 and x2goserver-one 3.01-1 -10.10 maverick with Likewise 5.3 and x2goserver-home 3.01-1 -10.04 lucid with Likewise 5.4 and x2goserver 3.01-5

Also, I have tried using unspecified domain and default domain (e.g. either "DOMAIN\username" or just "username" when using default domain), same result either way. Authentiction is successful, but no desktop!

And every time, perfect success with local users (full GNOME desktop), blank/black screen with Likewise users, no matter what x2go client (Linux, Mac, Windows, 3.01-04 all the way through latest 3.01-14)

Ivan, you are for certain using 10.10 maverick and LW 5.4 and x2goserver (not home/one) and you have never seen this black screen issue at all?

I'm determined to get this working as I know we will have audio if we can get it!

-----Original Message----- From: x2go-dev-bounces@lists.berlios.de on behalf of Ivan Boyadzhiev Sent: Wed 12/15/2010 3:21 PM To: x2go-dev@lists.berlios.de Subject: Re: [X2go-dev] x2go with likewise-open (ldap) questions

Hi Neil,

I am using 3.01-08 for Ubuntu as client. This is the one that downloads by default from the debian library. I have also tried it with 3.01-04 for Windows and for Mac, but same results. I will try 3.03-13 and see if there are any differences, but I doubt it.

Ok, you have really old clients. I have successful login with 3.01-13 in my Windows 7 I took it from here: http://x2go.obviously-nice.de/deb/pool-untested/x2goclient/x2goclient-3.01-1... I also have Ubuntu 10.10 as client, located on VMWare image. There I successfully connected and worked (had no sound, but this is something further). The client version is 3.01-14 (latest). I took it from here: http://x2go.obviously-nice.de/deb/pool-heuler/x2goclient/x2goclient_3.01-14_...

From your tests, it is clear that you have client version problem, and nothing with authentication.

...

4. If authentication is good, but there is blank/black screen, then try another: OS, Client, Client version. As I said above, the latest version doesn't work in my scenario. Hint: Don't try to connect with client from the same server, as it is not possible. If you use Windows, try to find other OS, install other (virtual if possible) Windows, Linux, whatever is easy for you.

Again, I have tried it with clients on Linux, Mac, Windows, all the same result: full GDM desktop with audio for local accounts, blank screen (but all successful messages in the log) for LW/LDAP users.

Here is the moment to ask which version is your x2goserver. I'm using

3.0.1-5 for x2goserver; 3.0.1-1 for x2goserver-home; 3.0.1-1 for x2goserver-one. I've installed it through the repository added this line to /etc/apt/sources.list (then apt-get update): deb http://x2go.obviously-nice.de/deb/ lenny main.

I guess (still didn't check) there is newer server version, but I used the official way through the repository. I guess this is stable one?

Bottom line: please, try to setup your x2go server and client as my versions.

---

BTW, as I'm fearing that if/when I get this issue resolved with the black screen showing up, that I will then have the audio problems, I will add these comments: -I have Likewise Open setup to connect to our domain as the Default Domain, thus all of our uid's do not use the format DOMAIN\user. Before, we all used these IDs, but since we currently only have one domain, I have set LW to use the default domain and so now we can login with just "user". This also affects our directories and thus my .x2go sessions look like: /home/local/DOMAIN/nwhunt/.x2go/C-nwhunt-51-1292422868_stDGNOME_dp32 rather than /home/local/DOMAIN/nwhunt/.x2go/C-DOMAIN\nwhunt-51-1292422868_stDGNOME_dp32 And within that directory are indeed the pulse audio files you mentioned were NOT there when you included the ~/.x2go/C-DOMAIN\userid-.... .pulse-client.conf .pulse-cookie

I will report back if I find anything more.

That's good, still it is better to have this issue resolved in case you have to connect to more than one domains. Currently I am using old likewise-open 5.4.0.42111, but now I will install the version 6.

P.S. As you can check the thread, the root cause of sound (and future share) problems is found, and even the source code is found, now development can check from their side and easily provide fix. But as you wrote above, with this configuration, you will not going to face sound problems.

Best Regards Ivan

This e-mail and any attachments are for the intended recipient(s) only and may contain proprietary, confidential material. If you are not the intended recipient, (even if the email address above is yours) do not use, retain, copy or disclose any part of this communication or any attachment as it is strictly prohibited and may be unlawful. If you believe that you have received this e-mail in error, please notify the sender immediately and permanently delete. This email may be a personal communication from the sender and as such does not represent the views of the company.

Ok, another update after 24 hours more of trial-and-error:

I have tried many combinations and STILL no gnome desktop for Likewise users! I don't understand it, I have tried: -10.10 maverick with Likewise 6.0 and x2goserver-one 3.01-1 -10.10 maverick with Likewise 5.3 and x2goserver-home 3.01-1 -10.04 lucid with Likewise 5.4 and x2goserver 3.01-5

Also, I have tried using unspecified domain and default domain (e.g. either "DOMAIN\username" or just "username" when using default domain), same result either way. Authentiction is successful, but no desktop!

And every time, perfect success with local users (full GNOME desktop), blank/black screen with Likewise users, no matter what x2go client (Linux, Mac, Windows, 3.01-04 all the way through latest 3.01-14)

Ivan, you are for certain using 10.10 maverick and LW 5.4 and x2goserver (not home/one) and you have never seen this black screen issue at all?

I'm determined to get this working as I know we will have audio if we can get it! <snip> Oh, wait a second . . . Ubuntu. Does Ubuntu still use dash as the default shell? If I recall correctly, there are some calls in the X2Go

On Thu, 2010-12-16 at 21:21 -0500, Neil W. Hunt wrote: scripts that work in bash but fail in dash. If you change the symbolic link /bin/sh to point to /bin/bash instead of /bin/dash, does it work?

I would also suggest to the devs to change the scripts to use #!/bin/bash rather than #!/bin/sh as the scripts do invoke bash specific statements - John

Hi Neil,

2010/12/17 Neil W. Hunt <nwhunt@vsticorp.com>

Ok, another update after 24 hours more of trial-and-error:

I have tried many combinations and STILL no gnome desktop for Likewise users! I don't understand it, I have tried: -10.10 maverick with Likewise 6.0 and x2goserver-one 3.01-1 -10.10 maverick with Likewise 5.3 and x2goserver-home 3.01-1 -10.04 lucid with Likewise 5.4 and x2goserver 3.01-5

Also, I have tried using unspecified domain and default domain (e.g. either "DOMAIN\username" or just "username" when using default domain), same result either way. Authentiction is successful, but no desktop!

And every time, perfect success with local users (full GNOME desktop), blank/black screen with Likewise users, no matter what x2go client (Linux, Mac, Windows, 3.01-04 all the way through latest 3.01-14)

Ivan, you are for certain using 10.10 maverick and LW 5.4 and x2goserver (not home/one) and you have never seen this black screen issue at all?

I'm determined to get this working as I know we will have audio if we can get it!

I've finally managed to reproduce your problem :). I've just received black screen, no sound just after my login. Test it, and it is happening every time under specific circumstances. What are they? I'm using:

• Ubuntu 10.10 x2goserver 3.01-5 and 3.01-1 as written above as server
• Likewise-open 6.0.0-1 (dpkg -l | grep likewise) as LDAP, joined with default Domain
• Windows 7 with x2goclient 3.01-13 as client

As result when I login with:

• USERNAME@DOMAIN (although it is already defined as default in Likewise-open), I face black screen, no sound, and the display at the title is nowhere in the server side
• USERNAME, I can login successfully with sound, folder share, terminate, etc...

Please, check at your end. I have never faced this problem with Likewise-open 5, even when I had always to login with USERNAME@DOMAIN there, as there doesn't have default domain join.

P.S. It is good side that I had experienced that, and that I can reproduce it, as I could make future investigations of your problem.

Best Regards Ivan

Here is all the good news:

Thanks for the suggestion about /bin/sh pointing to /bin/bash rather than /bin/dash. As soon as I changed that, regardless of Likewise or Ubuntu version, we are up and running! No more black screen and full audio sound when using default domain (I understand the code changes will happen so we don't have to use default domain but instead and use DOMAIN\username in the future).

We are very excited about rolling this out at our organization and will be in touch in the future.

Neil

-----Original Message----- From: x2go-dev-bounces@lists.berlios.de on behalf of Ivan Boyadzhiev Sent: Fri 12/17/2010 10:02 AM To: x2go-dev@lists.berlios.de Subject: Re: [X2go-dev] x2go with likewise-open (ldap) questions

Hi Neil,

Ivan, you are for certain using 10.10 maverick and LW 5.4 and x2goserver

...

(not home/one) and you have never seen this black screen issue at all?

Here is the update:

Ubuntu 10.10 always. Currently LW 6 (LW 5.4 in the past) and x2goserver as this output: USER@HOSTNAME:$ dpkg -l | grep x2goserver ii x2goserver 3.0.1-5 x2goserver (daemon and tools) ii x2goserver-home 3.0.1-1 x2goserver-one (One Node Edition - for single server usage) ii x2goserver-one 3.0.1-1 x2goserver-one (One Node Edition - for single server usage)

Best Regards Ivan

This e-mail and any attachments are for the intended recipient(s) only and may contain proprietary, confidential material. If you are not the intended recipient, (even if the email address above is yours) do not use, retain, copy or disclose any part of this communication or any attachment as it is strictly prohibited and may be unlawful. If you believe that you have received this e-mail in error, please notify the sender immediately and permanently delete. This email may be a personal communication from the sender and as such does not represent the views of the company.

John,

we are a software development organization, mainly Java-based, and like most organizations we predominantly have full Windows desktops for all of our users. We are looking to move towards a Linux-based thin client environment in the following way: -we've been evaluating x2go vs. FreeNX and while both are extremely performant and desktop-like experiences, the audio support from x2go has pushed us this way -we predominantly deploy our applications on Linux, so by running Ubuntu as our desktop environment it's less change from dev to prod -we want to be able to more quickly roll out new software development tools so by having a standardized desktop environment that can be controlled centrally, it makes it much easier to do this -obviously we want to save money and by purchasing very thin desktop units and an open-source host OS such as Ubuntu, and convincing people that most of the functionality they require with the traditional MS Office suite can be found with OpenOffice, we see potentially dramatic cost savings -we are tying it into our Active Directory (hence all my Likewise questions) so it was imperative we got that working, which now we do -we are in the process of evaluating the x2gothinclient environment and trying to network boot into an x2go client. Right now, we just have a light Ubuntu OS on the local disk with a full screen windowing system that basically creates a kiosk mode and loads the x2go client full screen, so end users don't even know there's an OS underneath. But we really would like to move to the netboot environment, alleviate the need for local disks, and run the x2gothinclient settings - so you might hear from me again soon!

I just spoke to our CTO about how helpful you've all been and we're feeling very good about x2go and the community in general. If we could help with a donation or something like that, is there anything in particular that would helpful to you all?

Neil

-----Original Message----- From: x2go-dev-bounces@lists.berlios.de on behalf of John A. Sullivan III Sent: Fri 12/17/2010 10:52 AM To: x2go-dev@lists.berlios.de Subject: Re: [X2go-dev] x2go with likewise-open (ldap) questions

On Fri, 2010-12-17 at 10:36 -0500, Neil W. Hunt wrote:

Here is all the good news:

Thanks for the suggestion about /bin/sh pointing to /bin/bash rather than /bin/dash. As soon as I changed that, regardless of Likewise or Ubuntu version, we are up and running! No more black screen and full audio sound when using default domain (I understand the code changes will happen so we don't have to use default domain but instead and use DOMAIN\username in the future).

We are very excited about rolling this out at our organization and will be in touch in the future.

Neil

<snip> I'm glad that fixed it, Neil. It sounds like you are looking at a large deployment. Are the physical desktop clients primarily Windows? - John

X2go-dev mailing list X2go-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev

This e-mail and any attachments are for the intended recipient(s) only and may contain proprietary, confidential material. If you are not the intended recipient, (even if the email address above is yours) do not use, retain, copy or disclose any part of this communication or any attachment as it is strictly prohibited and may be unlawful. If you believe that you have received this e-mail in error, please notify the sender immediately and permanently delete. This email may be a personal communication from the sender and as such does not represent the views of the company.

On Mon, 2010-12-20 at 09:23 +0200, Ivan Boyadzhiev wrote:

Hi again,

I will push for a fix, as it seems I had same localuser on the server side. Everytime I logged in with my LDAP password actually logged me into the home folder of the user with all LDAP permission groups (still that was /home/USER and no domain was in the path). The sound was always present, file sharing, suspend, and terminate. Now, when I've removed the local user, and tested, even when I'm with default domain and Likewise-open 6, the user is getting created under /home/local/DOMAIN/User folder, and the username is again with DOMAIN\User and again: no sound, no file share, no session resume, even no session terminate.

Can you, please, check and give us some estimation of the fix? Sorry to push you, but now for each username that is in my LDAP i had to create dummy local account with whatever password or to create manually entry in /etc/passwd file in order to create the account without DOMAIN name. This is again manual efforts and makes x2go un-centralised. The fix should come sooner or later, better sooner.

P.S. In case you are busy, can you, please, send me instructions how you build the client for windows (I had already downloaded the qt for windows). This way I could debug the exact parameters that are send and fix the code, I could even provide patch (in a way of .diff), and build the code locally <snip> Here are our current notes for building the Windows client:

1. Download the Qt source from ftp://ftp.qt.nokia.com/qt/source/qt-win-opensource-4.7.1-mingw.exe
2. Download the OpenSSL libraries from http://www.slproweb.com/download/Win32OpenSSL-1_0_0c.exe
3. Download the X2go code from http://x2go.obviously-nice.de/deb/pool-heuler/x2goclient/x2goclient_3.01-14....
4. Install the above EXE into a suitable location eg. c:\Build\Qt and c: \Build\OpenSSL and X2go into c:\Build\X2GoClient. Install the OpenSSL DLLs to the OpenSSL binaries directory to make them easier to identify for the NSIS script.
5. From the Windows Start Menu run Qt 4.7.1 Command Prompt
6. Execute Configure.EXE -static -release -openssl -I C:\Build\OpenSSL \Include -L C:\Build\OpenSSL\Lib
7. Once the above has completed execute Mingw32-make sub-src
8. Download the libssh libraries from http://x2go.obviously-nice.de/deb/libssh/libssh-x2go.zip
9. Extract the ZIP file to a temporary location and the libssh.dll.a and include files need to be copied to the mingw installation, eg. include/libssh/* -> mingw/include/libssh/ lib/libssh.dll.a -> mingw/lib/
10. Cd C:\Build\X2GoClient
11. Copy x2goclientconfig.pri.client x2goclientconfig.pri
12. Edit Makefile.Release by adding "-static-libgcc -static-libstdc++" to the LFLAGS options
13. Qmake
14. Mingw32-make release
15. If all has worked a compiled client should now exist under the Release directory