Tor

[Tor]

Hey snejok!
If this is a feature someone forgot to inform me! 😀
Can you please send the information you can see in the ‘What to include’ box under the posts, and anything that may be useful to reproduce the issue?
Thanks!

[Tor]

Hey dhfx. 🙂

The commands you’ve suggested are correct, I’d just use the two-dashes options format because the single dash is deprecated.

/usr/NX/bin/nxclient –admin

As for the name, you can think at the player as a tool to “play” your remote content, whatever it is.

[Tor]

The only option that cannot be controlled from the interface is “SSH client mode”, documented here: https://www.nomachine.com/AR09L00813

Thank you very much for your feedback!

[Tor]

Hi MPDano.

Thank you for reporting this issue, we’ll improve the errors printed for this kind of problems.

• This reply was modified 10 years, 2 months ago by Tor.

[Tor]

Hi dhfx.

Currently there is not a way to disable the automatic scrolling. We’ve often evaluated it, but we’ve never implemented it because of the equation “most wanted features divided by UI available area”. 🙂
The quicker solution to this problem may be adding the option in the configuration file, so that you would need to change it manually. We’ll have to spend more time to understand how to change the UI to offer the possibility to change the option through a checkbox.
Would this be fine for you?

[Tor]

Ray, there must be a problem in the way the client determines if the server is running on Windows.

Do you mind sending us client side logs to issues[at]nomachine[dot]com ? You can read the paragraph “How to gather client side logs” in these guidelines: https://www.nomachine.com/AR07K00677

Thanks!

[Tor]

Hi rhand.

We’ve just released version 4.3 implementing shortcuts. By default you can use Ctrl+Alt+M to minimize. It can be changed from Input and Preferences dialogs.

[Tor]

Hi Ray308,

could you tell me the NoMachine version installed on the server? Is Windows a plain 2008, or a 2008 R2?

[Tor]

Hi byrne.

How effective is the hardware encoding on a Linux Terminal Server? If we use an Nvidia card in our Terminal server how many virtual desktops will benefit from hardware accelerated encoding? I assume there is a limit on the number of simultaneous streams that can be encoded on the card (8?). Is hardware encoding supported for VP8 or is it a h264 feature only? The Terminal Server evaluation lacks h264 support.

We don’t use hardware encoders. We use the hardware only on decoding side.

The seamless/rootless mode for running a single application seems to garble quite a lot of the graphics (e.g. the mouse pointer) and the performance of the graphics updates suffers (e.g. playing video) when compared to running the same application in a full desktop. Is this a known limitation? I am running an EL6 server/client.

Full desktop sessions can work either via the NX compression of X protocol (“lightweight” mode) or via H.264/VP8 encoding. Rootless sessions always work through a mix of compressed X protocol and VP8 encoding. This is not a limitation on performance generally, but there could be some difference under specific conditions and with specific applications.

Can the options in the !M tray icon be customised? For example if I disable the whiteboard in the node.cfg it still appears in the icon drop down menu (but does nothing). It’s the same for allowing uploads, if disabled it still appears in the icon dropdown. I’d be happy if the icon only gave the option to record the session or “download a file from the server” and nothing more.

In fact those unavailable items should not be visible. We’ve recently noticed the problem, a fix is ready and will be released soon.

Can the option to show the menu panel also be completely disabled? We don’t want users to be able to play with settings or try to create new connections.

We’re planning to implement this feature that may help you:

https://www.nomachine.com/FR05J02679

It is still not approved because we want to be sure to offer a flexible solution. For example in your case the ‘Disabled’ setting may not be correct because you don’t want to forbid the credential saving but just disable the menu panel.

[VGL] ERROR: Could not open display :0.
The X server is running on :0 using the nvidia module. Maybe it’s an auth issue? This is on EL6.

This is due to a failure connecting to the 3D X server. I suggest running again the vglserver_config script by adding command line options: +s +f +t.

Am I correct in assuming that VGL uses the graphic card in a Terminal Server to draw the GL which is then video encoded in the normal NX way and sent to the client? Could the VGL be sent and drawn on the connecting client instead? All our desktop clients have fast graphics cards so can we u utilise them to improve the display quality/speed? Does hardware decoding (h264) make a big difference to the desktop experience?

Our software uses VirtualGL to render OpenGL application in hardware on the server side. We don’t provide a channel forwarding OpenGL calls or GLX requests to the client side.

[Tor]

Hi Ray308.

We’re aware of this problem, it is a bug in Qt 5.2 and we’re currently working on it.

[Tor]

Hi Pheckphul.
Actually we don’t have problems to handle the middle mouse button on any platforms, so we can confirm that the problem in your case may be related to the Logitech T400, which we didn’t have the possibility to test.
When we talk about “middle mouse button emulation” we mean the behaviour that you can normally trigger by pressing left and right mouse buttons, which on Linux it is the same as pressing the middle mouse button.
This option is not available at the moment, but it is ready in our development version and will be released soon.

[Tor]

Hi NikNik.

We are aware of some problems of NoMachine mobile related to keyboard and mouse, they will be addressed soon in one of the next updates.

[Tor]

Hi.

We’re currently working on keyboard problems and some issues related to gestures. We’ll soon submit an update for review.

Thanks for your patience!

[Tor]

Hi donnek.

It appears that you left checked the option “Change the server resolution to match the client when I connect” in the last dialog shown when the session connects, or that the “Resize remote screen” option is enabled. In both cases the remote desktop tries to resize to the requested geometry or, if it is not a supported resolution, to the nearest smaller geometry that in your case may be 1280×720. In order to leave the remote desktop to the native resolution, be sure to disable the options above.
If you’ve dismissed the dialogs appearing when the session connects, you can either create a new connection or edit the configuration and check the box “Reset saved preferences and password”.

[Tor]

Hello dhy.
We’re aware of this problem, it is due to the way Qt handles the AltGr button on Windows. We were
already planning to do something for it, but we’ve opened a public Trouble Report that you may track:

https://www.nomachine.com/TR06L04476

Thanks!

[Author]

Posts