Forum Replies Created
-
Posts
-
No, it is not possible.
You can try to force the application to use a high DPI. On the server side, edit /usr/NX/etc/node.cfg and change
#DisplayAgentExtraOptions “-nocomposite -noshpix”
to
DisplayAgentExtraOptions “-dpi 150”
(change 150 to the desired DPI).
Be aware that would affect any application, in floating window mode as well as in virtual desktop mode.
Hello.
Are you trying to share the physical screen of the server? Or are you getting this issue in a virtual desktop session?
Are you using programs installing hotkeys on the client or server?
Could you provide more information about the desktop environments and the window managers you are using?
Hello, I can reproduce the same issue on Ubuntu 14.04 server and Windows client.
The following Trouble Report has been opened: https://www.nomachine.com/TR04M05371
Hello.
Forwarding a USB mouse to the remote computer could help. I’d suggest reading this post: https://www.nomachine.com/forums/topic/world-of-tanks-mouse-capture#post-6224
Please confirm you are trying to access an existing KDE desktop running on the physical display of your Linux server.
In that case, I need you log in to your server using ssh, with the same user owing the KDE session.
Then run the following commands:
DISPLAY=:0 (assuming your physical desktop is using display :0)
export DISPLAY
xmodmap -pke > xmodmap.out
xkbcomp -xkb $DISPLAY xkbcomp.out
xprop -root | grep XKB > xprop.out
Also this would be useful:xev > xev.log
and try to press the “qwerty” keys in the test window that will pop up in the remote desktop.
Let me have a look of the .log files.
Hello, as I wrote about a related topic,
I’d like to look at file under /usr/NX/var/log and $HOME/.nx directories, from client and server.
Here you find detailed instruction for creating archives from those dirs:
https://www.nomachine.com/AR07K00677
It would be also interesting to know the keycodes reported by xev tool for the troublesome keys.
@xcribblesx : I guess you got it from client side. Nothing abnormal in those reports, by the way.
I’d like to look at file under /usr/NX/var/log and $HOME/.nx directories, from client and server.
Here you find detailed instruction for creating archives from those dirs:
https://www.nomachine.com/AR07K00677
It would be also interesting to know the keycodes reported by xev tool for the troublesome keys.
Hello, could you try to turn off image compression? Just edit /usr/NX/etc/node.cfg and change ProxyExtraOptions in this way (remove the heading “#”):
ProxyExtraOptions pack=none
Be sure you are in “lightweight” mode, i.e. check the line in node.cfg:
AgentLightweightMode 1
Start a new session to use the modified settings.
Could you run these commands on client and server:
xmodmap -pke > xmodmap.out
xkbcomp -xkb $DISPLAY xkbcomp.out
xprop -root | grep XKB > xprop.out
and provide files xmodmap.out xkbcomp.out xprop.out ?
I never encountered this issue. Have you got any steps to reproduce?
Have you noticed whether any application waiting for user input were hidden under the NoMachine fullscreen window?
I tried a few things. I didn’t find a stable solution yet but I tried to forward a USB mouse to the remote computer and it worked quite well.
While connected to the remote computer, open the NoMachine menu (Ctrl+Alt+0) chose Devices then Connect a USB device, find your local USB mouse and click Connect. Now the mouse input work in WoT as you expect.
The mouse won’t work in the local computer while connected to the remote. So if it is your only pointing device DO NOT check the option Grab the keyboard input, otherwise you have no way to close the NoMachine window.
When you want to quit and recover your mouse for local input, just kill the NoMachine client using the hot key Alt+F4.
Would you try a development version that could help with this issue? Please contact us by mail: forum (at) nomachine (dot) com.
The Windows ctrl key is mapped to the OS X ctrl key, so no special configuration is needed.
May I ask you the OS X version in use?
Are you getting problems with all applicatiions or with something in particular?
Did you check if you have any program using ctrl as “hot key” running in the background?