Forum Replies Created
-
Posts
-
The core dump you sent indicates a problem with hardware decoding on the machine you are connecting from. So the problem is there.
Make sure you:
1. Quit the Player (systray icon, right click, ‘Quit NoMachine player’)
2. Then disable hardware decoding on in the player.cfg -> option key=”Enable hardware accelerated decoding” value=”disabled”.
3. Restart the Player.
4. Try connecting again.Hi,
if you use the right side Alt/Option (instead of the one on the left) do the key works correctly? The right Alt acts as AltGr, which is the modifier needed in the combination to access those three symbols in the Swedish map (info obtained from your earlier topic).
If using the right Alt/Option is not comfortable, this command swaps left and right Alt keys:
setxkbmap -option lv3:lalt_switch -option lv3:ralt_altPlease check your email inbox for mails from me 🙂 It’s a regular dmg package with debug enabled to be installed on the server side. After installing it, reproduce the following issues:
1) Dragged content is misaligned when dropped, resulting in frustrating usability
2) Function keys are sometimes not registered, resulting in a “v” being typed instead of “cmd+v” being registeredZip up the logs and then send to us. You can just hit reply to the email you receive from me and send them that way. Thanks!
Could you both try disabling hardware decoding on the Player side? You can do this by editing the player.cfg file on the affected Mint client machine.
<option key=”Enable hardware accelerated decoding” value=”disabled” />
On Linux the player.cfg file is created in the user’s home/.nx/config directory: $HOME/.nx/config/player.cfg
You could try disabling hardware decoding on the Player side. That said, we released version 8 in the meantime, so I would update and check whether you are still encountering the same issue.
Hi, there are plans to add this, however it is not priority at the moment. It was handled recently in another topic, please see my response there:
https://forums.nomachine.com/topic/m1-mac-to-win10-shortcuts-not-working-right#post-41435
Yes, the “pacemaker (heartbeat)” is handled directly by nxserver. The shared IP is assigned to the host that is presently working as the master, so that the master host is working as the frontend of the cluster. In the case the master goes down (and the nxserver keeps the other host under control and checks the availability by itself), the shared IP is assigned to the slave host, so that the slave host becomes the new frontend of the cluster. The cluster product includes also load balancing functionality, but this load balancing, at the moment, is unfortunately limited, since all sessions are basically working only on the host that is master and thus only a limited set of functions can be spread across the two. This is going to change with the next version, that will be available soon, as part of an 8 update, where, after the session negotiation, connections will be “redirected” to the host that is less loaded, so providing the best load balancing. When will this be made available? W are presently working on the final tests. And this will be included in the subscription users already purchased.
To Doug, the logs of the client side do not show the issue (no correspondence to the server side logs). We need to receive the correct player side logs. What I suggest you do is make sure that “Don’t delete old log file in the player” checbox is enabled, reproduce the problem and send both server and player logs again. Thanks.
To MasterOfus, your issue seems to be a different issue which we are investigating and will come back to you soon.
Hi, in version 8 support for hardware encoding on macOS was released (for both Intel and M1). Let’s check if it is related to that, so on the Mac server please disable HW encoding: server settings -> server performance -> uncheck “Use hardware encoding”.
We would need you to enable debug, reproduce the problem and extract the logs again. The logs you attached were not complete, they did not include the node component.
Please see the instructions on how to do that: https://kb.nomachine.com/DT07S00243 and send them to forum[at]nomachine[dot]com. Use the title of this topic as the subject of your email.
It’s possible that the latest update 8.2.3 fixes the problem you have. So please try. If that doesn’t help, we would need you to enable debug, reproduce the problem and extract the logs.
Please see the instructions on how to do that: https://kb.nomachine.com/DT07S00243 and send them to forum[at]nomachine[dot]com. Use the title of this topic as the subject of your email.
Thanks!