Britgirl

[Britgirl]

There is a bug we are aware of in Gnome that is documented here: https://forums.nomachine.com/topic/hang-after-password-entered#post-39200

Can you try the workaround there?

[Britgirl]

In the logs we see the following server.cfg key is empty, when it should not be: AvailableSessionTypes.

What should be written there is ‘physical desktop’. Without this, no display can be started. Why it’s empty for your v8 installation, but not for v7 is not clear since we cannot reproduce this behaviour. Please check your server.cfg file has AvailableSessionTypes physical-desktop indicated. Then restart the NoMachine server.

Further reference:

The server.cfg and node.cfg files explained
https://kb.nomachine.com/AR02N00877

point (2) about the ‘AvailableSessionTypes’ key

The AvailableSessionTypes key is present in both server.cfg and node.cfg and permits to define which types of session will be made available to end-users. When server.cfg and node.cfg are on the same host, the list of session types must be the same in both keys. These keys are automatically populated at installation time. If a new session type is added later, they have to be edited manually. Restart the server to make this change effective.

 

 

[Britgirl]

Apologies, I didn’t specify that the server must be restarted in order for the debug we need to be logged. Please resubmit at your earliest convenience.

We did also check on the fly to see if we can reproduce your issue, but were not able to.

[Britgirl]

Hi, ideally we would need to see logs with debug enabled on the server machine if that’s possible (with v8 installed).

Please follow the instructions here and submit the logs to forum[at]nomachine[dot]com.

https://kb.nomachine.com/DT11R00182, section “First Step: Enable Debug Level on the Problematic Host” and then proceed with the other steps.

Thanks!

[Britgirl]

sdegler, check your email inbox for attachments from us.

[Britgirl]

We found a similar problem reported on Fedora which was recently fixed. Please update if you have not done so already. https://kb.nomachine.com/TR09T10609.

[Britgirl]

Hi, can you tell us the iPad keyboard language and also the remote desktop keyboard layout?

[Britgirl]

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.

[Britgirl]

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_alt

[Britgirl]

hi Doug, send the server logs directly to forum[at]nomachine[dot]com.

[Britgirl]

Please 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 registered

Zip 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!

[Britgirl]

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

[Britgirl]

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.

[Britgirl]

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

[Britgirl]

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.

[Author]

Posts