LockerGnomeTech news and nostalgia for today's technology professionals
Subscribe

Search

Software

Orbit gives GNOME a global menu by sending keyboard shortcuts when apps won’t share menus

The extension keeps real exported menus where possible and documents the difference between native entries and curated fallbacks.

Chris pulls a desktop menu tile whose mechanical linkage depresses two keyboard keys, illustrating Orbit’s shortcut-based menus.
Illustration: LockerGnome

A global menu bar needs applications willing to hand over their menus. GNOME’s Orbit extension works around the uncooperative ones by building a menu from keyboard shortcuts and sending the chosen combination to the focused window. The menu is effectively pressing the keys for you. Desktop diplomacy has reached the keyboard-emulation stage.

The project README lays out three paths. Exported menus arrive over D-Bus through an optional companion daemon. Those can preserve details such as checkmarks and disabled items. Applications with no usable export can fall back to curated shortcut menus. Everything else gets window, workspace and session actions so the panel doesn’t sit there looking unemployed.

The documented shortcut collection covers 292 applications. That number describes shipped mappings, rather than a claim that every application exposes a complete native menu. Clicking a mapped command sends its keyboard combination; what happens depends on that shortcut still meaning the same thing in the current app and context.

Orbit calls the fallback “a menu built from the app’s documented keyboard shortcuts.” That’s a useful admission about the mechanism. A shortcut entry can be helpful without having all the state information a real exported menu carries. An item that looks clickable might still require the application to be in the right state.

The extension supports GNOME Shell 48 through 51, with Wayland throughout that range and Xorg only on 48. The companion daemon is optional for shortcut and generic menus. Getting exported application menus working can introduce toolkit-specific requirements, including modules or a switch that makes an application use XWayland.

Those differences matter on a real desktop. The README distinguishes Qt, Electron, Firefox, GTK and other application families rather than pretending one checkbox fixes all of them. Some listed integration paths have explicit testing limits. A familiar-looking top panel doesn’t erase the less glamorous plumbing underneath it (menus have meetings, too).

The shortcut mappings are editable in Preferences. Changing a built-in creates a user copy, leaving the original mapping intact, and individual applications can be disabled. That gives the fallback a practical repair route when a shortcut changes or a particular app proves more trouble than the recovered screen space is worth.

For someone who likes a global menu but runs a mixed GNOME desktop, the appeal is consistency with an escape hatch. The experiment can begin with the extension alone and add the daemon where real exported menus are useful. There is no need to treat every fallback as equivalent merely because it occupies the same spot on the screen.

This approach could outlast individual export integrations because keyboard shortcuts remain a second route into familiar commands. Its maintenance challenge is equally concrete: a curated command stops being useful when the application changes what the keys do.

The keyboard has joined the panel.

More Software

Every Software story →