Switch monitor with keyboard shortcut?

[cacophony555]

I like the new functionality that supports selecting between multiple monitors connected to the host, but it seems inefficient to have to go through several layers of menus to do the switch. Is there a keyboard shortcut for switching between monitor 1 and monitor 2?

Unrelated secondary question: I’ve noticed that when I quit NoMachine the nxplayer.bin*32 process continues to run. Is this intentional or a bug?

[Tor]

Hi cacophony.

We recently submitted to our testing team a client version allowing to switch selected monitor by using the shortcut Ctrl+Alt+N, where N is the monitor ID. Will that be fine for you?

As for the secondary question, if you’re running an Enterprise Client and that process never closes, it may be a problem. Could you please compress directories %USERPROFILE%\.nx\R-* and send the archive to forum[at]nomachine[dot]com? We’ll check logs to look for clues about the possible issue. Thank you!

[cacophony555]

Thanks for the reply!

Yes, using Ctrl+Alt+N to switch windows would be fantastic. When can I get this version? I assume I just need to update NoMachine on my client and can leave the server running the same version as before?

For my second question I don’t believe I’m running the Enterprise Client as I’m just using whatever free/default version for both the client and server. So in my case it’s expected that the process never goes away? That definitely seems wrong because it leaves an instance of the process running for every single run. In other words if I launch NoMachine, connect to remote machine, preform a few tasks (*you’ll see why this part is important in the next section) and then quit there will be one instance of nxplayer.bin*32 that never goes away. Then if I launch NoMachine again, connect to remote machine, perform a few tasks and then quit there will be two instances of nxplayer.bin*32 that never go away!

Another issue I noticed is that if I launch NoMachine, connect to remote machine and then try to close the NoMachine window before I’ve done anything on the remote machine then NoMachine will freeze and I’ll be forced to manually kill the process.

I’m sending a zip of my recent sessions from tonight (which demonstrate the two issues above) to the email you mention above.Thanks!

[Tor]

Hi.

Yes, using Ctrl+Alt+N to switch windows would be fantastic. When can I get this version? I assume I just need to update NoMachine on my client and can leave the server running the same version as before?

We’ll release it with the next update, if you keep enabled the automatic software updates check NoMachine will alert you when a new version will be available.

So in my case it’s expected that the process never goes away?

There are cases where it is normal that the process runs in background, but what you’re describing is something different. We could not reproduce it so far, so I’d be grateful if you can help us to get some information from that hanging process.
From logs you’ve submitted I’ve noticed that the client goes into a termination state, but there is something preventing it from closing completely.
A way to know what’s happening consists in getting a stack of running threads. You can do it by using a Windows tool called Process Explorer:

https://technet.microsoft.com/en-us/sysinternals/bb896653.aspx

Launch it as administrator (no need to install, it’s a standalone binary) then double click the hanging process in the list to open the properties window. Select the Threads tab then double click on each row, and copy the content in an e-mail (or take a screenshot if you prefer).

[cacophony555]

Ok, I just sent an email with a detailed account of exactly what I did and included the full list of threads as an attachment.

Here’s what I did:

– initiated connection to corporate VPN via Juno Pulse

– Launched 1st instance of NoMachine and opened connection to remote host
– entered password on remote host lock screen
– relocked remote host screen
– pressed “X” to close NoMachine window

– launched 2nd instance of NoMachine and opened connection to remote host
– White window for 10+ minutes which didn’t respond (this is the first time I’ve seen this freeze on initial connection)

– ran process explorer as Admin and copied thread detail for the two running nxplayer processes into nxplayer_process_1.txt and nxplayer_process_2.txt

– manually killed the hung process (process 2)

– launched another instance of NoMachine and opened connection to remote host
– when I got the remote host lock screen I immediately pressed “X” to close the window; the window did close successfully, but now I have two running nxplayer processes
– copied thread info into nxplayer_process_3.txt

[cacophony555]

Did the logs I sent help?

[Britgirl]

Hi, we got them. We’ll provide some feedback as soon as we can.

[Tor]

Hi cacophony.
We’re still digging into the information you’ve sent. In the meanwhile you may download NoMachine 5.0.47 introducing keyboard shortcuts to switch current monitor.

[cacophony555]

I just tried the monitor switching via CTRL+ALT+N and it’s fantastic. Thanks!

My only recommendation is to have the key sequence be CTRL+N or ALT+N. I switch monitors all the time and pressing all three keys is a bit awkward.

[Tor]

My only recommendation is to have the key sequence be CTRL+N or ALT+N. I switch monitors all the time and pressing all three keys is a bit awkward.

You can configure them by using the Shortcuts button in the Input settings dialog.

[Author]

Posts