Windows How-To

Resolve Remote Desktop and VNC Conflicts With Gnome-Tweaks Keyboard Remapping

Address issues where keyboard remapping set in Gnome-Tweaks does not work as expected when using Remote Desktop or VNC connections.

Address issues where keyboard remapping set in Gnome-Tweaks does not work as expected when using Remote Desktop or VNC connections.

by Pallav Pathak

Keyboard shortcuts and remappings configured through Gnome-Tweaks often stop working or behave unpredictably during Remote Desktop or VNC sessions. This problem disrupts workflow, especially when custom key mappings are essential for productivity or accessibility. The issue typically arises because remote protocols like RDP and VNC handle keyboard input differently, sometimes bypassing local desktop environment settings and sending raw keycodes directly to the remote session. Addressing this requires a combination of configuration adjustments and understanding how these technologies interact with the Linux desktop environment.

Method 1: Adjust Keyboard Remapping at the Remote Session Level

Connect to the remote machine using your preferred Remote Desktop (RDP) or VNC client.
Once connected, open gnome-tweaks directly on the remote system (not the local machine). If it’s not installed, use the following command in a terminal to install it:
sudo apt install gnome-tweaks
In Gnome-Tweaks, navigate to the Keyboard & Mouse section and apply your desired remappings. For example, swap Caps Lock with Ctrl or adjust shortcut keys.
Log out of the remote session and log back in to ensure the remappings take effect. Some changes may require a full restart of the GNOME session.

Making changes on the remote system ensures that keyboard remappings are recognized within the context of the desktop session you are controlling, regardless of how the input is sent from the client.

Method 2: Use System-Level Keyboard Remapping Tools

Instead of relying solely on Gnome-Tweaks, use system-level remapping tools like setxkbmap or xmodmap on the remote machine. These tools modify keyboard layouts at a lower level, which can be more reliably recognized by remote protocols.
For example, to swap Caps Lock and Ctrl using setxkbmap:
setxkbmap -option ctrl:swapcaps
Add your chosen setxkbmap or xmodmap command to the startup applications on the remote system to apply remappings automatically at login.

System-level remapping increases compatibility with different remote desktop protocols, ensuring your shortcuts and key swaps persist across sessions and reboots.

Method 3: Adjust Remote Desktop or VNC Client Settings

Review the keyboard input settings in your Remote Desktop or VNC client. Some clients offer options such as “Send special keys directly to remote” or “Use local keyboard layout.”
Experiment with these settings to see which configuration allows your remapped keys to function as expected. For example, enabling “Send special keys directly” may bypass local OS mappings and send raw keycodes, which can interfere with desktop-level remapping.
If available, match the keyboard layout on the client and remote systems to minimize translation errors.

Optimizing client settings can resolve conflicts where remappings are lost in translation between local and remote environments.

Resolving conflicts between Remote Desktop, VNC, and Gnome-Tweaks keyboard remapping usually requires making changes directly on the remote system or adjusting client settings. Testing different approaches will help you find the most reliable setup for your workflow.

Keep reading

More from Windows

All Windows guides →