Repository navigation
Macos switches to some random desktop after hitting the dmenu shortcut #41
Description
After updating to the latest macos I started having the following issue: at some point after running dmenu my shortcut for summoning dmenu starts to switch to some specific desktop instead of spawning dmenu. If I hit the shortcut key combination at that desktop it works fine, but on any other desktop it switches to that one specific desktop and doesn't spawn dmenu until I hit it again. It makes it very difficult to use because I want to spawn it on any desktop.
I can only fix it by killing dmenu and starting it up again.
I'm running Ventura 13.3.1.
Is anyone else having this issue? Any tips for debugging it?
Reacted by jream, Antonio Tralice, H.R. Shadhin and Paul Derscheid
Activity
unmanbearpig commentedon May 10, 2023
An update on this: it didn't happen for a few days after the last macos update, usually (but not always) it would happen multiple times per day. So it might be be fixed now, but can't tell for sure yet.
atralice commentedon Nov 24, 2023
Had the same issue. At some point when opening dmenu with the shortcut, it would go the one particular workspace and open there.
I closed dmenu and restarted and its working ok now.
Im running 14.1.1 (23B2082) Sonoma.
unmanbearpig commentedon Feb 23, 2024
I forked the project to add the features I want and I fixed this bug by switching to a different API for hotkeys. That API requires extra permissions, so it would be better to find a different fix, but it works for me.
Here is the repo https://github.com/unmanbearpig/unmenu
and my blog post about it https://unmb.pw/misc/2024/01/22/unmenu.html
oNaiPs commentedon Sep 28, 2026
The launcher is now shown as a non-activating NSPanel (commit 2546731 on main), and the app no longer calls NSApp.activate when the hotkey fires. Activating the app was what pulled you to whichever desktop the window had been bound to, so this should be fixed. A release with the change is coming; if you can build from main in the meantime and still see it, please reopen.