[BUG] Shortcuts don't work

[nipnipj]

Shortcuts are set but they do no work.

OS: Cachyos
DE: KDE Plasma 6.5.0
WM: KWin (Wayland)
Electron version: 38.4
Crossover version: 3.4.0

[lacymorrow]

Why/how are you using Electron 38.4?
The app is only using Electron 14 right now...

[lacymorrow]

Linux Wayland limitation. uiohook-napi (the module CrossOver uses for global hotkeys) does not work under Wayland due to security restrictions — Wayland intentionally prevents apps from capturing global input events.

Workaround options:

1. Run CrossOver under XWayland: ELECTRON_OZONE_PLATFORM_HINT=x11 crossover
2. Switch your session to X11/Xorg temporarily
3. Use KDE's global shortcuts system if possible

This is a known upstream limitation of uiohook-napi. Wayland native support would require a different input hook approach.

[lacymorrow]

📋 Tracked in Paperclip as LAC-1325. This issue has been added to our internal project management system and will be reviewed by the engineering team.

[lacymorrow]

Shortcuts via uiohook-napi don't work on Wayland — the library relies on X11 input hooks (XRecord/libxkbcommon-x11) which aren't available in a native Wayland session.

Workaround: Force CrossOver to run under XWayland:

DISPLAY=:0 crossover

Or launch Electron with X11 platform explicitly:

crossover --enable-features=UseOzonePlatform --ozone-platform=x11

On KDE Plasma you can also set ELECTRON_OZONE_PLATFORM_HINT=x11 in your environment.

This is a known limitation with uiohook-napi on Wayland — native Wayland support would require a different input hook mechanism (libinput or portal-based), which isn't currently implemented.

[nipnipj]

Shortcuts via uiohook-napi don't work on Wayland — the library relies on X11 input hooks (XRecord/libxkbcommon-x11) which aren't available in a native Wayland session.

Workaround: Force CrossOver to run under XWayland:

DISPLAY=:0 crossover

Or launch Electron with X11 platform explicitly:

crossover --enable-features=UseOzonePlatform --ozone-platform=x11

On KDE Plasma you can also set ELECTRON_OZONE_PLATFORM_HINT=x11 in your environment.

This is a known limitation with uiohook-napi on Wayland — native Wayland support would require a different input hook mechanism (libinput or portal-based), which isn't currently implemented.

Shorcuts are working on cachyos with --enable-features=UseOzonePlatform --ozone-platform=x11

[lacymorrow]

📋 Tracked in Paperclip as LAC-1748. This issue has been added to our internal project management system and will be reviewed by the engineering team.

[lacymorrow]

📋 Tracked in Paperclip as LAC-2529. This issue has been added to our internal project management board and will be reviewed. View in Paperclip

[lacymorrow]

Tracked in Paperclip as LAC-1325. This issue has been added to our internal project management system and will be reviewed by the engineering team.

[lacymorrow]

Triaged. Grouped with related reports and tracked internally as LAC-2659.

[lacymorrow]

Two related landings that may help here:

• #517 (merged) now surfaces a notification when globalShortcut.register() fails silently — helpful for diagnosing whether the OS/compositor is claiming your key combo.
• #524 (merged) expanded the readme's Linux section, including an X11-vs-Wayland note. On KDE Plasma Wayland, Electron's globalShortcut API has known limitations — switching to an X11 session (or launching CrossOver with --ozone-platform=x11) is worth a try.

Leaving open pending your retry with the new build. Part of CrossOver merge/close audit (LAC-3662).