Forum Replies Created
-
Posts
-
We’ve not been able to reproduce your issue with or without a keyboard attached to the RPi device.
Those logs you attached are from 2020 and they indicate a NoMachine 6.9 on Windows (player side by the looks of it). Make sure that this version is updated to the latest 8.11. Which Windows version is it exactly? Then on the Raspberry, which is on the server side also make sure that the NoMachine software is updated to the latest 8.11.
Then, we will need fresh logs of a new session once you have follow the instructions here, and the logs must be from both sides.
https://kb.nomachine.com/DT07S00243.Also, which specific Raspbian version? (please note this has since been superseded with Raspberry Pi OS).
We have a Trouble Report open for this issue which you can monitor using this link: https://www.nomachine.com/TR05V11150. A fix will be released in the next maintenance, NoMachine 8.12.
Hi, thanks for your feedback. We’ll look for ways to improve that behaviour for all displays and user habits because we understand that it can be annoying.
It was tested before I created this issue. It does not have any effect.
I see, I didn’t see you mention that earlier. Anyway, we are still unable to reproduce the problem with grabbing the keyboard on Plasme 6. But we did find a bug report on the KDE bugzilla. It seems very like your issue.
https://bugs.kde.org/show_bug.cgi?id=489113
For now, we suggest to downgrade to the environment that you said is working for you and wait for KDE to release a fix.
Can you start the player from a terminal instead like this?
/usr/NX/bin/nxplayer --activegrabBtw, Check what’s configured in your nxs file because this setting will override your global setting (configured in Player). You can check what’s in the .nxs file by locating it in the directory defined in the ‘Connections and recordings’ field from the Settings -> Player -> Folders panel of the User Interface.
What is the OS on the nxplayer side?
Did you try a reboot on the openSUSE side? Is the issue just the Alt F4 key or other Alt+ combinations? Are other keys affected?Please describe the steps you take to reproduce the behaviour.
Hi, the logs don’t report any errors. It’s better to send us the entire .nx folder from the server side with debug enabled first, before reproducing the problem again. Please follow the instructions here and re-submit, https://kb.nomachine.com/DT07S00243. Thanks.
Any issues in the production-ready Sequoia will become Trouble Reports, which we’ll publish, and they will of course be fixed 🙂
Dear macOS Users,
At the moment we are aware of some issues with permissions. It is possible that incompatibilities with this beta will be fixed when Apple officially releases it for production. Please bear in mind that NoMachine cannot officially support pre-release (beta) versions of operating systems. We do of course accept bug reports from users who are testing with these pre-release versions and we work to make sure we are compatible at the time of the general release, in this case macOS 15. We will of course investigate all issues reported and evaluate what fixes, if any, are necessary.
See here for our policies about beta versions: https://www.nomachine.com/AR03E00450
Hi, is it possible for you to send those logs to us so we can take a look? Send them to forum[at]nomachine[dot]com. Thanks.
Hi, sorry for the delay in coming back. It’s not good news. We looked at the last set of debug logs and they still don’t pinpoint to the specific problem. What we do know is that a parameter that NoMachine relies on when performing GPU encoding is not being recognized. The error is “Invalid parameter”, but we’ve not been able to pinpoint which specific parameter despite the high level of logs and we’ve been through every single parameter we use. These are our standard parameters, and permit GPU encoding across several dozens of combinations of macOS systems and hardware combinations with diverse video cards. It’s possible that this particular encoder doesn’t support one of the features that we need, hence the Invalid parameter error. As for the other apps which you say are using the GPU, they are most likely using a different set of parameters. We could of course continue debugging on our own by replicating your set-up to a tee, purchasing the hardware and AMD RX 560 and disabling the parameters one-by-one until we find which parameter is causing the issue. But it would not bring us to a solution because it would not be possible to change the way NoMachine uses the encoder. So, the workaround is to continue using software encoding (or if possible try an alternative GPU unit).
Hi, allowing all keys to get grabbed, except for Alt+Tab which should remain on the client is not possible, I’m afraid.
Check your permissions.
home/essin/.Xauthority not writable, changes will be ignored 368745 368745 2024-06-17 12:02:52 026.353 NXNODE WARNING! Cannot remove cookie for :3002 from /home/essin/.Xauthority. 368745 368745 2024-06-17 12:02:52 026.374 NXNODE WARNING! Error is: 13, Permission denied.It is just a warning, but maybe this is blocking the connection.
Check /home/essin/.Xauthority permissions and change the owner to essin (sudo chown essin:essin /home/essin/.Xauthority) or just remove the .Xauthority file (it will be re-created when you connect again).