graywolf

[graywolf]

The NoMachine client for OS X does not detect if CapsLock and Ctrl keys are swapped. I think the only thing you can do is to restore the original mapping of the keys on the server when you are connecting from an OS X client:

setxkbmap -option “”

To swap them again when needed:

setxkbmap -option “ctrl:swapcaps”

 

[graywolf]

I’ve just found something.

The NoMachine client failed parsing your options field in the XKB configuration:

“terminate:ctrl_alt_bksp,ctrl:swapcaps”

In order to work around this issue, arrange the options so that ctrl:swapcaps becomes the first item:

“ctrl:swapcaps,terminate:ctrl_alt_bksp”

This command (client side) will do the trick:

setxkbmap -option “” -option “ctrl:swapcaps” -option “terminate:ctrl_alt_bksp“

[graywolf]

I guess you are sharing the physical display. You need to add option ctrl:swapcaps to client as well as server host.

Check also keycodes on both hosts:

xmodmap -pke | grep -w “Control_L\|Caps_Lock\|37\|66”

With keys swapped, Control_L has code 66 and Caps_lock has 37.

Try also xev test tool to get more information.

If nothing helps, please send client side logs to issues (at) nomachine (dot) com

[graywolf]

Hello.

NoMachine checks the state of CapsLock and keeps it in sync for client and server. It seems that this check fails for some reason. Could you tell me more so I could try to reproduce?

• Are the two remote sessions virtual or real remote desktops?
• Which OS is running in client and server hosts?
• Which NoMachine product are you using? Which version?

[graywolf]

NoMachine detects the Ctrl/Caps swap reading the XKB properties on the client host. How did you swap the keys? If you did it with xmodmap NoMachine does not detect they are swapped. I’d prefer using setxkbmap in this way:

  setxkbmap -option ctrl:swapcaps

You can check how that command affects the XKB properties:

xprop -root | grep XKB

 

[graywolf]

Hello bratell

 

Please run the following commands through the remote session:

xkbcomp -xkb $DISPLAY xkbcomp.out
xmodmap -pke > xmodmap.out
xprop -root | grep XKB > xprop.out

and let we look at files xkbcomp.out, xmodmap.out and xprop.out

Try also

setxkbmap se

and check if something changed.

 

 

[graywolf]

Hello,

have you upgraded to 4.4.1? Still suffering the problem?

In order to receive the debug library, write to issues (at) nomachine (dot) com.

Please specify:

• The NoMachine software version
• If you need the build for Linux 32 or 64 bit.

 

[graywolf]

Hello,

could you provide client and server log files? You can follow this guideline: https://www.nomachine.com/AR07K00677

If you prefer to provide logs by mail send to: issues (at) nomachine (dot) com

 

[graywolf]

Hello,

I think identifying the applications grabbing the pointer and the keyboard could help.

Let me send you a library logging that information.

[graywolf]

The X.org server provides a way to create an xorg.conf automatically. Try this command: X -configure :2

Then edit the resulting xorg.conf and place it in the folder /etc/X11/

[graywolf]

So you are experiencing problem with both client and server running NoMachine 4.3.30 on Ubuntu 14.04 and Gnome 3 desktop. Am I getting this right?

I’m suspecting that something happens to Ctrl keys on your client. Could you get this info:

• xev output on client side generated pressing and releasing Ctrl key
• output of xmodmap -pke command (client side)
• the file key.map generated by command xkbcomp -xkb $DISPLAY key.map (client side)

[graywolf]

Werner, have you upgraded both client and server? Fixes to copy and paste in 4.3.30 are client-side only.

Could you provide more details about:

• The operating systems of the client and server hosts
• The desktop environments (Gnome, KDE, etc) in use and their versions
• The applications from/to you tried to copy/paste unsuccessfully.

Thank you.

[graywolf]

1. Is there a setting for “fullscreen across all monitors” in the player.cfg?  I’m setting “Window state” to “fullscreen” in the config file and the client only uses one monitor.

Not at the moment.

2. Is there documentation for the settings?  For example, how do the “Background *” and “Wave background image” values work?

No. The .cfg configuration files are generally for internal use of the software. The preferred way for configuring the NoMachine client is the graphical interface.

3. Despite setting General/LinkQuality in a saved configuration to 9, the value won’t “take”.  It is necessary to drop the value down, apply it, then push the value back up and apply it.  Connecting seems to always connect at some default lower value.

Could you send the server and client logs from a session showing this issue? You can send them to issues (at) nomachine (dot) com.

As a follow-up to point (1) – I’m finding the full screen behaviour is very strange.  I’ve a two screen set-up and setting the size via both -geometry on the command line and the “Window geometry” in the player.cfg results in it popping up the correct size for about half a second, before it jumps to the right, making the right side of the window completely inaccessible.  This is all running without a window manager – I’m trying to set up a kiosk-style environment.

I’ve just tried and reproduced a similar issue. We’ll address this problem.

[graywolf]

Hello.

I didn’t reproduce this issue. Could you tell me more:

The NoMachine products and versions in use on client and server.

Operating system and desktop environment in use on client and server.

If server is Linux: are you connecting to a physical or a virtual display?

Can you provide specific instructions to reproduce the issue?

[graywolf]

Unfortunately, nobody has ever asked us for this, so I haven’t more useful suggestions for you.
Have you tried the Gnome mailing lists? They might have some suggestions.

[Author]

Posts