graywolf

[graywolf]

I think the virtual display is retained. Restarting the NoMachine server is the simpler thing you can do, use this command:

sudo /usr/NX/bin/nxserver –restart

 

[graywolf]

Hello. I think this problem is the same reported in trouble report TR08N07113.

Check “Notify me when the TR is closed” to get updates.

[graywolf]

I connect remotely to the physical desktop ; but the resolution is 640×480 by default and i cant modify it ; glxinfo is correct ; but the screen is not usable.

how we can modify the size and resolution of the screen ? Is it possible ?

Available resolutions when attaching to the physical display don’t depend on NoMachine, but on what is allowed by the graphics card and/or the X server configuration.

By the way, it doesn’t matter. VirtualGL needs that to offload the rendering, but you should never access like it was a usual display because its X authority is relaxed or disabled. See here: Why VirtualGL requires access to the display :0.

I have configured virtualgl according to AR11K00737 but in this environment how can we run openGL applications without the command vglrun?

The same article you mentioned suggests to change key EnableVirtualGLSupport to enable VirtualGL for all application. If I understand well, you aren’t goint to enable VirtualGL for all, but you need it for some specific program and you’d like to avoid typing “vglrun”. In that case I’d suggest to create aliases in the user’s shell, so that command “my-3d-program”  actually launches “/usr/NX/scripts/vgl/vglrun my-3d-program”.

[graywolf]

Hello,

just to be sure, could you tell me the actual versions of NoMachine in use on client and server?

Could you confirm the client is running on OS “El Capitan” and server on Linux? Which Linux distro?

The original report was that previous content was pasted in place of the correct one. Is the correct content placed if you retry to paste (without copying again) after a few seconds?

Do you mind creating a screencast showing the problem and the second-try paste (send it to forum (at) nomachine (dot) com)?

[graywolf]

Trouble Report is here:

https://www.nomachine.com/TR12N07403

[graywolf]

Thank you for reporting. I’m going to open a Trouble Report about this.

[graywolf]

Do you mean the problem is with Alt+Numpad combinations, i.e. ones providing chars basing on their ASCII code, for example Alt+126 = ~ (tilde)?

 

[graywolf]

Please change /usr/NX/etc/node.cfg to have SessionLogClean 0.

Then replicate the problem and issue setxkbmap -print again.

Check also output from commands:

echo $DISPLAY

xprop -root | grep XKB

Send content of /usr/NX/var/log to us (you can mail to forum (at) nomachine (dot) com).

[graywolf]

Hello. The actual frame rate depends on many things related to hardware, software and  network. If you are on a gigabith ethernet, the network won’t affect the performance.

By the way, whatever the source is, the framerate of the stream that NoMachine carries from server to client can be chosen among the two values 30 or 60 frames per second.

You can change it in the server settings:

Show the server status -> Server Preferences -> Performance -> Request a specific frame rate

 

Attachments:

1. 

   fps.png
   

[graywolf]

I always use the client in fullscreen mode. After some more digging, I can confirm my F-keys are sent from client (Linux) to server (MacOS) as mere F-keys: F11 and F12, which are mapped to “show desktop” and “show dashboard” work well. What I feel is missing, is a method to map keys to the actions implemented by default in the Mac keyboard (the big icons in the F-keys), for example an emulation of the Fn key.

OK. Definitely this is something to be implemented, it didn’t get broken because of the software update.

[graywolf]

I discovered that F-keys in my local keyboard (Linux OS) behave like fn+F-key in the remote keyboard (macOS).

So forget what I wrote about fn+F9. Just press F9 and you should get Mission Control. But you wrote F9 is caught by your Linux desktop. It looks like “Grab the keyboard” is not enough. Try to run client in full screen mode (this completely grabs the keyboard). If nothing changes, remap the keyboard shortcuts of your Linux desktop.

Try also this: edit configuration file /Applications/NoMachine.app/Contents/Frameworks/etc/node.cfg to have:

DisplayServerExtraOptions "-oldeventapi 0"

and check if behavior changes.

[graywolf]

Let me suggest to update the client as first thing.

Then, if problem keeps occurring it’d be very helpful if you identified any pattern to reproduce such problem on a regular basis.

For example, did you notice if problems occur when you switch NoMachine and Windows Desktop forth and back with Alt+Tab? This could make Windows catch some key event and would explain why you sometimes get “Q” instead of “@”.

About the case of “stuck AltGr”, maybe do you get “omega” in place of “@”? That would indicate the Shift key is stuck.

And about the windows that get closed, can you tell me the sequence that is supposed to close them (for example, Gedit quits on “Ctrl+Q”, Gnome Terminal on “Shift+Ctrl+Q”).

Anyway, it is possible you can improve the situation enabling the option “Grab the keyboard input”.

 

 

[graywolf]

Uninstall the NVIDIA proprietary driver, then reinstall the package mesa-libGL from the RedHat repository. Let me know if it worked.

If you need the proprietary driver (for better performance on the physical screen or if you mean to use VirtualGL) I’ll provide a more complicated how-to.

 

[graywolf]

Hello,

can you tell me which NoMachine version worked for you, before the update?

Ctrl+(Left/Right/Up/Down) Arrows does not activate Mission Control functions (switch to left/right Spaces, windows list).

I tried this with 5.1.54, no problem. I suspect those combo do nothing if  Spaces are not enabled or have only one Space.

Ctrl keyworks well in terminal (e.g., Ctrl-C sends interrupt, Ctrl-R starts history search, etc.).

So you have no problem with Ctrl key.

Fn keys do not activate the corresponding functions mapped in MacOS (Mission Control, Volume Control).

Mission Control, Volume Up/Down, Brightness actually don”t work. But Mission Control pops up if I use F9 (that means I have to press two keys: fn + F9). But I see previous version of NoMachine had the same behavior. Did they work in old version you used before the update?

 

• This reply was modified 7 years, 6 months ago by graywolf.

Attachments:

1. 

   applekbd1.png
   

2. 

   applekbd_F9.png
   

[graywolf]

You can unlock Connection preference even if you are logged in as standard user: in such a case you have to fill the fields of authentication box with administrator’s username and password.

If it didn’t work, please let me know:

• The the OS kind and version of the machine where you found the problem
• The version of NoMachine in use
• Any relevant error message. They could be recorded in log files, so create a zip archive including folders /Library/Application Support/NoMachine/var/log and /Users/<standard user>/.nx

 

[Author]

Posts