Forum Replies Created
-
Posts
-
Nilsonaj, thanks for the additional logs. They indicate a possible issue with Wayland. What DE are you using? Our test on the fly was with Gnome and everything works.
Vhitoc, we would need the server side logs as per the instructions given previously.
However, we are aware of an issue when using KDE when Wayland is the display server. You could try using an alternative desktop environment first maybe? If that doesn’t help, maybe switch over to X.org?
Hello,
We do have a Virtuoso installation because we are partners with Cadence, but we were not able to reproduce any “dimming” with the latest version 8. That said, we are unfamiliar with
geHiSetSelProtectionEFandgeUnsetAllSelProtection, so steps to reproduce would be very useful in this case.Given your questions are specifically related to version 7 which is only available to subscribed customers now, your issues would need to be addressed by our support team. You can either open a support ticket if you have a subscription, or submit a contact request (Contact us in the footer of the website) if you are using evaluation software, and then follow up with a recording and steps to execute in Virtuoso, along with the version of Virtuoso you are using.
This is the first time we have received such a request: to blank the screen but not the mouse attached to the computer whose screen you just blanked 🙂
The non-disabling of the mouse is not a configurable option. The majority of our users use remote screen blanking as a security feature, to prevent people in the vicinity of the computer from seeing and interacting with the computer. Although splitting the mouse input from the blanking of the screen can probably be done, it would create confusion in our honest opinion and is not what most NoMachine users expect.
The scenario you described is very clear, and, indeed, such notifications can be “disturbing”, for example in a video where just a random set up of ads are displayed, so with no user interactions. We can easily add an option to the server to disable all such notifications, but whether this can be a potential security threat must be considered carefully, such as if a user might surreptitiously enable such an option, with the owner of the computer being unaware of it.
But one thing we want to understand, to fully “get” the scenario we are talking about. Are these headless computers used to display ads or something similar? If they are headless, to whom is the screen output being displayed, who is going to see these screens? (screens that are not there, given that these machines are headless).
And also, if there is not any physical screen, the user who’s watching the computer output is supposed to be only a remote user…
But if it’s like this, why? I mean…To resolve your problem, and to give to users “a solution” that is applicable to all your similar cases, we need to perfectly understand what your “specific case” is 🙂Why it’s possible to hide the icon in the system tray and not the notifications…
Well, because the notifications are there exactly to inform the LOCAL user, or anybody connected, that there is now somebody else looking at what YOU, the user, are doing. It’s a serious and important security feature!
The fact there is NoMachine running, and so the NoMachine icon is in the system tray, i.e NoMachine is running, but not currently “exporting”, not showing the screen to somebody else, it’s a much less critical situation. This is why we allow people to do that. But we don’t omit to tell people “Hey, beware! Somebody is looking at your screen!”.
Look at any other remote desktop system, like the one of Apple Mac or similar. You can’t even disable the tray icon and even less so (like in our case) the “Somebody is connected” icon or the “Somebody connected” popup.
Look at the problem from this other standpoint: me, in my company, set NoMachine to stay hidden and to never say to the user in front of the screen that somebody connected. I can use NoMachine as a powerful spying tool, and see what everybody is doing, at any time, without the user in front of the computer ever knowing. It would make NoMachine a powerful tool to commit a crime.
Hi, hard to say without seeing the logs.
Please submit both Player and Server logs as per the instructions here:
https://kb.nomachine.com/DT07S00244
and send them to forum[at]nomachine[dot]com. Thanks!
Hi, our developers are working on that issue right now. A solution will be released in one of the upcoming maintenance releases.
We checked on the fly and didn’t reproduce your issue.
NoMachine service 8.4.2 -> do you have the Free Edition installed or something else?
If I connect directly to the computer everything works just fine.
Do you mean if you connect with NoMachine to the physical desktop everything works fine? Please clarify this point.
When I access the computer through NoMachine from a Windows NoMachine client
Are you connecting to a virtual desktop? Can you submit screenshots or a recording from session start to the point where you reproduce the problem.
We prepared an article which also includes a section on trouble-shooting AMD drivers, please take a look:
How to use AMD HW encoder with NoMachine on Linux platforms
https://kb.nomachine.com/AR02U01190and follow the tips there. Do they help?
If you’ve updated to the latest version and cannot connect (since the original problem is solved), please open a new topic.
Also, the logs that you sent us, from Sophia which you say is the client, do not contain the logs I requested.
2) on the computer you are connecting from, tick the box ‘Don’t delete log files on exit’ option enabled in Settings -> Player -> Security. Otherwise the client logs will be missing or only partial.
Hi, thanks for taking the time to report this. It’s a known issue which can be tracked here:
Cannot login by NX protocol and private key when option ‘Import the private key to the connection file’ is checked
https://kb.nomachine.com/TR05S10271We have had a similar case with another user also using an AMD GPU (albeit a different model). We’ve not been able to reproduce this problem with any of the test set-ups we have (and we have many!). We cannot say if you are experiencing the same problem, but we can give some pointers to check.
The first thing you need to do is make sure that the resolution is not higher than 1920×1200. Higher resolutions are not supported yet because of problems with some AMD drivers
Then make sure you have the correct drivers and that they were installed correctly:
The drivers can be found here https://www.amd.com/en/support/linux-drivers and to install, run
sudo apt-get install ./amdgpu-install_5.4.50401-1_all.debAnd after that:
sudo amdgpu-install --usecase=amfDoes this change anything?
By the way, your attachment (was it the server log?) did not attach, so send it to forum[at]nomachine[dot]com.
Please follow the tips in this article:
How to use AMD HW encoder with NoMachine on Linux platforms
https://kb.nomachine.com/AR02U01190