The primary reason for this error is that xmodmap does not properly handle the swapping of key mappings between CapsLock and Shift+CapsLock keys. When these keys are swapped, xmodmap returns an error bell instead of executing the intended action.Another possible cause could be a conflict with other

How do I fix: Manually reassign key mappings?

Step 1: Open a terminal window and run the command `xmodmap -e 'clear Lock'` to clear any existing mappings for CapsLock.Step 2: Run the command `xev | grep -A10 keycode 66` to check the current key mapping for CapsLock. This will show you the keysymbol being passed to X.Step 3: Manually edit the xm

Software⏱️ 3 min read📅 2026-06-15

How to Fix: xmodmap: `Shift+CapsLock` -> `Delete` returns error bell

xmodmap issue with CapsLock and Shift+CapsLock mappings.

Quick Answer: Check if the keyboard layout is set to English_US, as it affects the keycode for CapsLock.

📋 Table of Contents

⚠️ Common Causes
🛠️ Step-by-Step Verified Fixes
✨ Wrapping Up

The error 'xmodmap: `Shift+CapsLock` -> `Delete` returns error bell' affects users who have customized their keyboard layouts using xmodmap. This issue occurs when the mapping of CapsLock and Shift+CapsLock keys is swapped, causing unexpected behavior.

This error can be frustrating for users as it prevents them from using certain keyboard shortcuts correctly. In this guide, we will walk you through the troubleshooting steps to resolve this issue.

⚠️ Common Causes

The primary reason for this error is that xmodmap does not properly handle the swapping of key mappings between CapsLock and Shift+CapsLock keys. When these keys are swapped, xmodmap returns an error bell instead of executing the intended action.
Another possible cause could be a conflict with other keyboard settings or software that interfere with xmodmap's ability to map keys correctly.

🛠️ Step-by-Step Verified Fixes

Revert CapsLock and Shift+CapsLock key mappings

Step 1: Open a terminal window and run the command `xmodmap -e 'clear Lock'` to clear any existing mappings for CapsLock.
Step 2: Run the command `xmodmap -e 'keycode 66 shift = Delete BackSpace'` to restore the original mapping of Shift+CapsLock to Delete+Backspace.
Step 3: Verify that the keyboard layout is correct and that the keys are working as expected.

Manually reassign key mappings

Step 1: Open a terminal window and run the command `xmodmap -e 'clear Lock'` to clear any existing mappings for CapsLock.
Step 2: Run the command `xev | grep -A10 keycode 66` to check the current key mapping for CapsLock. This will show you the keysymbol being passed to X.
Step 3: Manually edit the xmodmap file (usually found in `/etc/X11/xorg.conf.d/`) to reassign the keysymbols for CapsLock and Shift+CapsLock. You can do this by adding or modifying lines similar to `xmodmap -e 'keycode 66 shift = BackSpace Delete'`.

✨ Wrapping Up

To resolve the error 'xmodmap: `Shift+CapsLock` -> `Delete` returns error bell', you can either revert the CapsLock and Shift+CapsLock key mappings or manually reassign them using xev. By following these steps, you should be able to restore your keyboard layout to its original state.

Did this fix your problem?

If not, try searching for specific error codes.

🔍 Search Error Database

❓ Frequently Asked Questions

🛠️ Related Fixes

How to Fix: Pc crashes shortly after launching game (rainbow

Fix Pc crashes shortly after launching game (rainbow six siege). Compl

How to Fix: Installing an APK on a locked down phone

Installing an APK on a locked down phone: Try using a rooted device, e

How to Fix: New PC build- no signal and no clue

Fix New PC build- no signal and no clue. Complete troubleshooting guid