[BUG] Keyboard Shortcut to Hide Background stop working.

[zachter]

Shortcut to lock CrossOver in place and hide background doesn't work every time. I hear a noise and it does nothing. I rebind it to CTRL+ALT+SHIFT+another key and it works again. Then when I re-launch the program that bind no longer works and I have to rebind it to another key. Then when that key no longer works I have to rebind it to another. Eventually I won't be able to bind it to a new key since it will eventually not work with all of the keys on my keyboard.

Any way to fix this?

Version 3.41
Windows 11

[lacymorrow]

Thanks for the report.

Diagnosed the root cause: Electron's globalShortcut.register() returns false when registration fails, but CrossOver currently ignores this return value. If registration silently fails on startup — which can happen on Windows when another app, the OS, or a game overlay has claimed the same combo — CrossOver never shows any error and the shortcut is simply inactive.

The "works after rebind but breaks on relaunch" pattern fits this exactly: rebinding triggers syncSettings, which calls unregisterAll() then re-registers. At that point the combo may be available (e.g. game not yet focused, other app hasn't grabbed it yet). After relaunch, registration happens earlier in the startup sequence, when the conflict is already present.

A few diagnostic questions that would help narrow this down:

1. Which game are you playing? Does it run in exclusive fullscreen? Some games or overlays (Discord, GeForce Experience, Xbox Game Bar) can pre-register shortcut combos.
2. Does the issue happen if you launch CrossOver without launching the game first?
3. If you open Task Manager or a shortcut conflict checker after CrossOver launches with a non-working shortcut, do you see another app holding the combo?

Short-term workaround: use CTRL+ALT+SHIFT + a function key (F1–F12) — these are less likely to conflict with games or Windows shortcuts.

Fix needed: check the return value of globalShortcut.register() and surface a notification when a shortcut fails to register, so users know immediately which combo has a conflict.

[lacymorrow]

Fix is in PR #517: #517

The root cause is confirmed: globalShortcut.register() returns false on silent failure but CrossOver was ignoring that return value. The PR:

• Checks the return value in registerShortcut() and logs a warning on failure
• Collects all failed accelerators in registerKeyboardShortcuts() and fires a user-facing notification listing the conflicting combos (e.g. "Could not register: Control+Shift+Alt+X. Another app may be using this combo. Try rebinding in Settings.")
• Wraps the notification in try/catch so early-startup calls before the renderer is ready degrade gracefully to log-only

For the reporter: the workaround in the previous comment still applies while the PR is pending review. If you can confirm which app is claiming the combo (Task Manager, ShortcutsDetector, or just trying with no other apps running), that would help nail down the repro.

[zachter]

Fix is in PR #517: #517

The root cause is confirmed: globalShortcut.register() returns false on silent failure but CrossOver was ignoring that return value. The PR:

* Checks the return value in `registerShortcut()` and logs a warning on failure

* Collects all failed accelerators in `registerKeyboardShortcuts()` and fires a user-facing notification listing the conflicting combos (e.g. "Could not register: Control+Shift+Alt+X. Another app may be using this combo. Try rebinding in Settings.")

* Wraps the notification in try/catch so early-startup calls before the renderer is ready degrade gracefully to log-only

For the reporter: the workaround in the previous comment still applies while the PR is pending review. If you can confirm which app is claiming the combo (Task Manager, ShortcutsDetector, or just trying with no other apps running), that would help nail down the repro.

I had a few apps open. Discord. SteelseriesGG, Medal. Will need to close them and check and get back to you.

[zachter]

I closed down all other running programs and still ran into the issue. This is even with setting the bind to CTRL+SHIFT+ALT+F1.

[lacymorrow]

This issue has been triaged and tracked in Paperclip as LAC-2406.