---
title: "Field Input Using Linux Machines "
url: "https://dm0bkdes5q7a2ls.productfruits.help/en/article/field-input-with-linux-machines"
language: "en"
last_updated: "2026-01-31T00:28:21.887Z"
---

# Field Input Using Linux Machines 

When entering values into fields in Spirion Sensitive Data Platform from a Linux machine, be aware of how Linux treats the forward slash (/) character.

**Note to all Linux users**: When you click the forward slash character (**/**) from your numeric keypad - with the **Num Lock** function on - Linux treates the forward slash character (**/**) as a division symbol and assigns the forward slash character a different ASCII number.

This behavior occurs because Linux often interprets the numeric keypad's divide key (**/**) as the mathematical division symbol (**÷** or**`÷`**) or as a specialized keypad operator, rather than a simple forward slash, when **Num Lock** is active. 

Here are the most effective ways to fix this in Linux, ordered by ease of use. 

## Method 1: Change Keyboard Layout Options (Easiest) 

Most Linux distributions (Mint, Ubuntu, Gnome/KDE) enable you to force the numpad to always enter digits/standard symbols. 

1.  Open **System Settings** > **Keyboard** > **Layouts** (or "Input Sources").
2.  Click **Options...**
3.  Look for **Miscellaneous compatibility options** or **Numeric keypad**.
4.  Select **"Numeric keypad keys always enter digits"** or **"Default"**.
5.  *For* ***KDE****:* System Settings > Input Devices > Keyboard > Advanced > Miscellaneous compatibility options. 

## Method 2: Remap with `xmodmap` 

If the settings GUI does not work, you can force the key to map to the slash symbol (`/`) using `xmodmap`. 

1.  Open a terminal.
2.  Create a file named `.Xmodmap` in your home directory:  
    
    ```
    xmodmap -pke > ~/.Xmodmap
    ```
    
3.  Edit the `~/.Xmodmap` file and find the line for `KP_Divide`.
4.  Change it to:  
    
    ```
    keycode 106 = slash slash slash slash slash slash slash
    ```
    
    *(****Note****: Keycode 106 is common for numpad slash, but may differ. Use* *`xev`* *to find your actual keycode if necessary).*
5.  Apply the change: `xmodmap ~/.Xmodmap`.
6.  Add `xmodmap ~/.Xmodmap` to your startup applications to make it permanent. 

## Method 3: Fix VS Code Specific Issues 

If this only happens in VS Code, it is a known keybinding issue where the keypad is misinterpreted. 

1.  Open VS Code settings (`Ctrl+,`).
2.  Search for `"keyboard.dispatch"`.
3.  Change the setting from `"code"` to **`"keyCode"`**.