Forum Replies Created
-
Posts
-
The problematic part at this point is between the Intel driver and libva – which we can’t do much about it, because it’s not a part of NoMachine. We can only provide instructions on how to make it work. Even wth NoMachine OUT of the picture, it’s a struggle in general to make Quicksync work on Linux.
1. Installed intel media driver as mentioned in https://www.nomachine.com/AR09O00938 ( except kernel changes )
Kernel changes are fundamental to make it work. The steps we’ve got in article are from Intel itself, so there’s a reason they included changes to the kernel to make it work.
When connecting to the laptop, you are attaching to its physical display, so on the client you can only see the monitors that are physically available on the server.
Then we’ll need the logs. This would help us to understand what the problem is and why it’s happening. Thanks!
The idea is to have a Graphic Workstation where 3 persons/users should have separate sessions.
NoMachine Windows products offer remote access to the physical desktop of the remote host. I.e all users connecting will see the same desktop.Having 3 separate sessions for 2 users is possible with any of the Terminal Server for Linux products.
When connecting to the physical desktop, the maximum resolution you can get is the maximum resolution supported by the remote graphics card (not what is on the connecting client).
Cannot resize the remote screen to my local monitor’s resolution
https://www.nomachine.com/AR02M00836Please try the following and let us know if it helps. Connect from Windows 10 and disable the hardware decoding:
i) inside the NoMachine session open the menu (ctrl+alt+0 or click on the page peel in the upper right corner).
ii) Access Display -> Change settings and tick the ‘Disable client side hardware decoding’ option.
iii) Then on Windows 10, launch the client and click on Settings -> Player preferences -> Privacy tab and select ‘Don’t delete log files on exit’
iv) Connect to the server and reproduce the black screen problem.
v) On Windows 10, create a compressed archive of the .nx directory in the user’s home.
The .nx folder is hidden. To find it, write the following in the address bar or the file browser: %USERPROFILE%\.nx Send the log archive to us as email attachment to forum[at]nomachine[dot]com making sure you use the title of the topic as the subject of your email.
Thanks!
NoMachine on Android doesn’t yet support H.264 acceleration, but it is planned. Please consult its feature request here:
Adding support for GPU accelerated H.264 hardware decoding on Android devices
https://www.nomachine.com/FR12M02991You should install Enterprise Terminal Server, not Terminal Server. Uninstall the Terminal Server package and download Enterprise Terminal Server.
Further reading:
https://www.nomachine.com/product&p=NoMachine%20Enterprise%20Terminal%20Server
https://www.nomachine.com/adding-terminal-server-nodes-to-enterprise-terminal-server-via-the-user-interface
Should I purchase Terminal Server Node Subscriptions with Enterprise Terminal Server? – https://www.nomachine.com/AR03R01079The only way we can help is to insist on receiving the logs from both client and server sides, with debug enabled.
– on the connecting client, follow https://www.nomachine.com/DT10O00163#2
– on the computer you want to connect to, follow https://www.nomachine.com/DT10O00163#1
– reproduce the problem
– gather up logs and submit as before
Sorry for the late answer. Exit code 8 is output from your Osascript, what does the Osacript manual say 🙂
On your connecting client, you have Enterprise Client installed. We would need to know what the OS is on the remote side, the computer/server you are connecting to. If you’re not in charge of the Linux box, please get this information from the administrator who is.
Results of tests show that it would not be powerful enough to run as a NoMachine server. As a client device it could be possible, just, but it’s not a device we would recommend, I’m afraid.
@russellaugust, if you are able to reproduce this issue using the latest 6.11 version, you should provide the output that fra81 requested in his reply. Otherwise, full logs from both sides of client and server would be useful.
There is a Trouble Report for this issue:
Termination of virtual session causes GDM crash
https://www.nomachine.com/TR06R09761Please sign up to receive a notification of when a fix has been released.
Logs received July 7th. Environment details both client (Ubuntu 18.06) and server (Ubuntu 16.04).
But didn’t show enough information. Debug should be enabled on both client and server sides, please see instructions on how to do this. Send them to forum[at]nomachine[dot]com like last time.
The logs didn’t show anything useful. For now please look at this article here:
Troubleshooting the error message ‘Connection refused’
https://www.nomachine.com/AR09O00937and follow the tips outlined there.
There’s also this article if you’re connecting to the server when it’s behind a NAT.
https://www.nomachine.com/AR11L00827