The Problem

The Cause

The Fix

The Fallout

Takeaway If you heavily customize your keyboard shortcuts, you’ll eventually hit this: one mapping silently breaks another. It took me years to get my setup where I wanted it. My daily stack looks like this: That’s multiple layers, each with its own shortcuts, buffers, and behaviors — all stacked on top of each other. Copy/paste alone can come from different sources (vim, tmux, system clipboard, browser), and you need to stay in control of which layer you’re interacting with. Everything works — until it doesn’t. At some point, I mapped my Super (Win) key to Hyper. In GNOME, this lives here: My setting looked like this: This used to work fine. GNOME even allowed shortcuts like: But in newer GNOME versions (around 48), this breaks. GNOME no longer properly recognizes Hyper as a usable modifier for shortcuts. So if you remap your Super key to Hyper, you effectively lose it as a shortcut key in GNOME. Remove the Hyper mapping and go back to default Super behavior: This is the annoying part: Hyper might look like a clean “extra modifier” on paper — but in modern GNOME, it’s effectively dead. If you rely on GNOME-level shortcuts: Otherwise, you’ll end up debugging “why nothing happens” again in a few years. Templates let you quickly answer FAQs or store snippets for re-use. Are you sure you want to ? It will become hidden in your post, but will still be visible via the comment's permalink. Hide child comments as well For further actions, you may consider blocking this person and/or reporting abuse