Forum Replies Created
-
Posts
-
We had a user trying to install on Samsung Galaxy 10:
http://pdadb.net/index.php?m=specs&id=2936&c=samsung_gt-p7510_galaxy_tab_10.1_wi-fi_16gb
and had the same issue. It too is Tegra 2. Client starts, screen turns black and then it closes.
Lenovo S6000 tablets have yielded good results at a 200 dollar price point.
4.2 has far more artifacts in lightweight mode versus 4.1 on Linux.
4.1 player & 4.1 server = very few artifacts
4.1 player & 4.2 server = very high level of artifacts and missing icons and sections of the screen
4.2 player & 4.2 server = slightly better level of artifacts, but still many areas not correctly rendered. You have to hover your mouse over these areas to force it to display.
@bratell In 4.1 we were seeing memory leaks and higher CPU with vp8, have you tried lightwight mode? The server and client footprints appear greatly reduced and it’s running faster for us in our use case.
I just confirmed that –exit (to minuses) is in fact in the 4.1 build. This was missing in earlier releases and seems to be working.
With the new version, I have found a UI way to do it and a hackish way.
** If you resize the canvas to the desired resolution prior to connecting, the session will attempt a 1:1 connection and add a new modeline for you automatically.
** In the .nxs file, you can find the Resolution XML line and modify it by hand.
In our case, we have a template .nxs file that is copied before nxplayer launch and the XML line is modified with sed to use 90% of the physical screen. This allows for dynamic connections regardless of workstation used. We also have disabled the resize handles so that users are not tempted to play with their canvas.
The 4.x seems designed more for end users to be able to do more…which in some cases has made it harder for system administrators.
This fact was confirmed too in our internal testing. You can only copy text *to* the Linux Server, images in the clipboard are not working at all.
Text
Linux Client OS -> Linux Server (GNOME) WORKS
Linux Server (GNOME) -> Linux Client OS NOT WORKING
Images
Linux Client OS -> Linux Server (GNOME) NOT WORKING
@hchan, Did you test the last release, 4.1.29 vs the previous 4.1 release. It just came out in the last few days. We’re seeing NX 3.5 performance on this latest set of patches, even on older hardware. Make sure that both client and server pieces are patched to this release as there were issues in both.
What I have found is the best way to debug these situations with NX is to see what’s happening behind the scenes. First thing you do is find what script is being run upon login from the .cfg files, usually this is something like /etc/gdm/Xsession or /etc/xdm/Xsession or similar. Then I add a line at the top like:
env | sort > /tmp/nxenv.log
This gives you information about the variables that have been set. Then on the next line you can do a /usr/bin/xterm, which bring up a console window. If this opens and works, then NX is having trouble interacting with the desktop in some way. You can then manually start the desktop environment by hand and watch the command spewage to see what happens. Good luck!
We want to turn it off server side for a few reasons:
1) (see attached file). We have a module that runs with a second security factor post login and before GNOME appears. The applet is not finding a tray and running as a window and sits over the top of our dialog. Web logins needed a second security factor besides just a password.
2) The items in the menu are not things we want our users to see or have access to. The icon sitting in the tray to alert of another connection would be OK as long as it didn’t cause the #1 issue, and we could remove all the menu entries.
Attachments:
