Right click context menus appear on incorrect monitor

[lo_pan]

Hi all,

Using 7.6.2 client on arch Linux, Gnome 40.4.0 on x.org 1.20.13.  3x UHD monitors, in the display number order of 2, 1, 3 with 1 being the main monitor.

NX server is 7.6.2 workstation running on a headless or single monitor (below behavior is the same) Ubuntu 20.04.3, Gnome 3.36.8 on x.org 1.20.11.

When I run chrome, slack, vs-codium, etc… on the nx server in a virtual display and use it on the client. Whenever I right-click within chrome, no matter which of the three client monitors the application is on, the resulting right-click context menu will appear on monitor 2 of the client, being the leftmost monitor.  The same occurs with the “file” menus of applications when I left click, or press alt f.

Can anyone offer suggestions?

thanks

[Carin]

Hi lo_pan,

Can you let us know if you’re starting those applications in a custom session, by configuring a single application or a console window? Thanks!

[lo_pan]

thanks for responding Carin!

I’m starting the applications as custom sessions, configured as single applications.

I appreciate any assistance you can provide.

[graywolf]

Hello lo_pan. I was not able to replicate that issue. Would you post the output of command xrandr -q from your client system?

[lo_pan]

Sure thing mate, please see the attached.

Attachments:

1. xrandr.txt

[graywolf]

It looks OK. Would you post the content of files $HOME/.nx/node/C-*/options from the server-side host? I’d like to check whether geometry setting is correct there.

[lo_pan]

No worries mate, I appreciate your help.

I am unsure if any of the below should be redacted.  Please let me know if so, or feel free to redact for me if possible.

$ find ~/.nx/node/C-* -name "options" -exec cat "{}" \+
nx/nx,keyboard=evdev/us,cpus=24,hwenc=1,encmode=auto,threads=auto,priority=realtime,geometry=3696x2032,client=linux,copysize=0,audioin=5:7:opus:socket-/home/lo_pan/.nx/nxdevice/D-1003-6AB4F2CDFD06D37CC614BA966AACBA9F/audio/native.socket:1,voiceout=5:11:speex:socket-/home/lo_pan/.nx/nxdevice/D-1003-6AB4F2CDFD06D37CC614BA966AACBA9F/audio/native.socket:1,volume=0,devicesmartcard=1,deviceports=1,devicenetwork=1,lightweight=1,legacykb=0,slave=1,cache=16M,images=64M,link=7,type=xsession-default,clipboard=both,cleanup=0,accept=127.0.0.1,product=LWSN/LI07S02957,shmem=1,backingstore=1,shpix=1,cookie=1CE4494FB84FEDBE44B25671CEE3B9A2,id=workbox-1003-6AB4F2CDFD06D37CC614BA966AACBA9F,render=1,multipass=1,networkadaptive=1,encryption=1,proxy=38/38,monitor=8,rtremoteport=4610,rtremotehost=192.168.1.238,rtkey=E82AB8649147BCDB1C8929650A82244B,rtiv=5112BFB1521837FF7586FD296A1F1672,rekey=32G,deblock=1,rtlocalport=4011,downsampling=0,mode=1,shadowmode=2:1003
nx/nx,keyboard=evdev/us,cpus=24,hwenc=1,encmode=auto,threads=auto,priority=realtime,client=linux,copysize=0,audioin=5:5:opus:socket-/home/lo_pan/.nx/nxdevice/D-1004-B7B691E8BC1ACCFE85EC59CEB8DBFDB9/audio/native.socket:1,voiceout=5:11:speex:socket-/home/lo_pan/.nx/nxdevice/D-1004-B7B691E8BC1ACCFE85EC59CEB8DBFDB9/audio/native.socket:1,volume=0,devicesmartcard=1,deviceports=1,devicenetwork=1,lightweight=1,legacykb=0,slave=1,cache=16M,images=64M,link=5,type=rootless,clipboard=both,cleanup=0,accept=127.0.0.1,product=LWSN/LI07S02957,shmem=1,backingstore=1,shpix=1,cookie=9D710E479DEF8877F4B98C4D3674EF57,id=workbox-1004-B7B691E8BC1ACCFE85EC59CEB8DBFDB9,render=1,multipass=1,networkadaptive=1,encryption=1,proxy=51/51,monitor=8,deblock=1,downsampling=0,mode=1,shadowmode=2:1004

[chidstar]

Hey lo_pan and graywolf – sorry to jump in here, I was looking at this thread and it might help solve an issue I’m having – how did you get NoMachine to recognise your 3 monitors? I currently just have 2 (laptop and 1 plugged in) I have NoMachine on my local (ubuntu 20.04) and a VM on the cloud, same OS, with xcfe as my desktop environment. But I’m having the issue where when I click “resize remote displays” on the options and go full screen, it treats both devices as on giant monitor.

I’ve attached my output of xrandr -q and the options from the remote server.

Any input you can give will be helpful!

Thanks

Attachments:

1. xrandr-1.txt
2. server-options.txt

[lo_pan]

chidstar – I have no idea mate. Your issue appears different to mine though, you should probably make a separate thread so it gets more eyes.

[fra81]

@lo_pan

We reproduced the issue in our labs and it will be fixed in the next release. Thanks for reporting!

 

@chidstar

You probably mean this feature: https://knowledgebase.nomachine.com/FR12K02799. This is already implemented, but only in virtual desktops, that are available in the NoMachine Terminal Server product line (e.g. NoMachine Workstation). When connecting to a physical desktop, you are limited by the number of monitors actually present on the server.

[lo_pan]

@fra81

Excellent! I’m glad you could reproduce the issue.

I look forward to the next release.

Thanks NoMachine team, I appreciate your assistance

[chidstar]

@fra81 thank you for your reply!

 

To be clear: I’m connecting from a physical desktop with 2 monitors, to a virtual machine on the cloud. I expected to be able to utilise my 2 monitors as 2 separate displays for that virtual machine through the NoMachine client (I have this downloaded on both systems https://www.nomachine.com/download/download&id=5 which I believe is part of the product line you’re talking about, correct?) but at the moment, the “resize remote monitor” and “full screen on all monitors” make my 2 displays = 1 giant 47″ display, which is not what I want.

Am I not able to achieve this with my setup?

Thanks

[fra81]

Even if you are connecting to a virtual machine, NoMachine is still connecting to the “physical” display of that machine. The fact the hardware is virtualized doesn’t change the bottom line: if the machine is configured to have one monitor, the applications running there will “see” that one monitor.

I have this downloaded on both systems https://www.nomachine.com/download/download&id=5 which I believe is part of the product line you’re talking about, correct?

The product line I’m talking about is not free but it is available for evaluation. See for example the Workstation: https://www.nomachine.com/download/linux&id=13. This product enables the possibility to create a virtual display (virtual desktop), that can have any number of virtual monitors.

[chidstar]

@fra81 thank you very much, I’ve been messing around with it a bit more and I think I understand what’s happening. The free version doesn’t have that capability, and from what I can tell, only the Workstation product does. I’ve evaluated the Enterprise Desktop version and it doesn’t allow multiple virtual monitors, which is a bit odd. But it seems as long as Workstation is installed on the remote server, it recognises the multiple displays from a physical desktop you’re connecting from, no matter what version is being used. That at least has solved that mystery so I’ll ask no more questions on this thread and open a new one if I have more.

Thanks again for your help!

[Britgirl]

” I’ve evaluated the Enterprise Desktop version and it doesn’t allow multiple virtual monitors, which is a bit odd”

Enterprise Desktop indeed does not permit multiple virtual Linux desktops on the same machine. This is a feature of the Terminal Server family, so Workstation is the product for you, as you rightly identified and as Francesco already suggested  😉

[Author]

Posts