Forum Replies Created
-
Posts
-
From an earlier comment of your “When I disabled it before, I only did it on the Windows machine. Should I have also disabled it on the Linux (server) machine?” – no it was not necessary 🙂
HW decoding is a client-side setting (the device you are connecting from), so in your case you only needed to disable it on your Windows computer.
Hi, disabling HW decoding on the client is done in the Player configuration, apologies if this was not made clear:
You need to edit the file $HOME/.nx/config/player.cfg and set the configuration key “Enable hardware accelerated decoding” to “disabled”.
The options are:
– true: hw decoding enabled
– false: hw decoding disabled (but libraries for hw decoding are loaded)
– disabled: hw decoding disabled (libraries for hw decoding are never loaded and the checkbox is greyed out inside menu panel)You can also toggle HW decoding from the connection menu (during the session), but this will toggle between true and false, see above).
Can you confirm that the player.cfg file has “disabled” next to the Enable hardware accelerated decoding key?
Each of those Linux system bash exit codes could relate to a number of different processes, such as nxexec run by nxserver, nxrunner run by nxnode, gnome run by node and so on. It would be better to see the logs of a session in which you have encountered a problem i.e a recent dropped or lost session and not one from 1 year ago to give you the reasons for specific exit codes during the loss of a session. Some examples are, exit code 11 generally means that the process crashed for segfault, exit code 9 that terminated by SIGKILL, exit code 15 that terminated by SIGTERM (more gracefully). The description within the logs should suffice and where it doesn’t, we can of course improve.
Hi, we are aware of an issue related to Wayland and the workaround for the moment is to disable Wayland and user X.org. Can you send us the logs of the remote Kubuntu server so we can check it’s the same issue we are currently investigating? Please consult the following document for instructions on how to extract the logs and submit them here, or send them directly to forum[at]nomachine[dot]com making sure to use the title of this topic as the subject of your email. Thanks!
We also removed all the CPU-based and CPU-core-based pricing which, given its 2022, was really anacronistic.
Hi, with the next update. Pixel 7 most likely requires an app that uses the more recent SDK. Please read our notice here:
https://forums.nomachine.com/topic/nomachine-for-android-and-ios-users-read-here#post-40608
I’ve sent everyone who has contacted us regarding this thread the link, including those whose replies are not visible :-p If other users are reading this and are encountering the scrolling issue and would like to try the .dmg package which includes the fix, please contact us directly via the website (footer->Contact Us ->General Enquiries) and submit your request. We’ll send you the link 🙂
Hi, here is an update.
Logs that were submitted showed that HW encoding was not in use with v8, but there were also logs for v7 and in those we also saw the HW encoding was not in use 🙂
Nothing has changed between versions how HW vs SW encoding is handled. They only think we can think of is that the “Info” that is printed in the GUI about the codec was improved (i.e made clearer) in version 8, and so it’s possible that when you were using v7, you thought HW encoding was being used when in actual fact it wasn’t.
Given that we cannot reproduce the issue, the only way to check that you were using HW encoding in a v7 session is for you to send us fresh logs. We’ll then check them. So to receive earlier v7 packages can you drop us an email to forum[at]nomachine[com] specifying which package you want (deb, rpm or targz) so we can send you a download link? Thanks!
Yes, well.. When entering the server in Guest mode, you don’t need an account, you are completely anonymous, except for the IP address, the network you come from. With Visitors mode, you log in to the Cloud Server with your system account, so the Cloud Server knows who you are and will also pass over this information, but without you having to make a new login on the target node. This is useful because, with Visitor logins, the user doesn’t need to have a system account on the node (and indeed they login to the node as a guest), but you actually consider the user as a user coming with a system login since the user actually logged in to the Cloud Server.
Hi, there was an image pasted in your topic which was removed. Is it possible for you to attach it in a follow up, or even send directly to forum[at]nomachine[dot]com and I will attach it to your original topic. Thanks!
Hi all,
thanks everyone for reaching out to us over the weekend. I have contacted all those who’ve posted to this thread now, so please check your inboxes. Happy nomachining 🙂
We’ve sent an email to everyone in this thread, a couple of emails bounced so if you have not received anything, please contact us directly for a macOS package which includes the fix. Thanks!
Hi, thanks for taking the time to report this. Does the player window show an error or does the session window just close?
Are there any core files generated that you can share with us?
Hi, glad to know you find the server activity helpful. That was the exact reason behind adding the ‘server activity’ feature: to allow admins to keep an eye on NoMachine connection numbers, users, average connections etc even what files are being transferred. Showing the history of connections is the next step in improvements we will be adding to the server admin GUI. Watch out for that in one of the upcoming releases.
You should submit that screenshot to forum[at]nomachine[dot]com, the link was removed because it was unavailable. You say that you are using the latest version of NoMachine, which is version 8. I assumed you were referring to the server side. Please confirm what NoMachine product and version is installed on the server side. Thanks.