I apologize if I post this in the wrong place, for now I’m not sure if this is a bug or user error.
Problem
I used CTRL+Q for other programs, I noticed that sometimes I can’t use my CTRL+Q for any apps including video games, although it felt more consistent nowadays. After days of frustration trying to figure out the root cause, I found out it was caused by Docker Desktop.
Solving Attempt
I found that CTRL+Q is “detach” for docker, so I edited config.json and add "detachKeys": "ctrl-@,ctrl-]". And it fixed the problem,… for a while.
More specifically, it only fixed the problem if I manually run Docker Desktop from start menu. If Docker Desktop ran as a startup app (Task Manager > Startup [tab] > [enable] Docker Desktop Launcher), docker will prevent any other apps to use CTRL+Q again.
Strange Behavior
The other anomaly is, if I don’t use custom detachKeys and close Docker Desktop, I will be able to use CTRL+Q even if Docker Desktop ran at startup. So I will be able to use CTRL+Q as long as Docker Desktop is not running.
BUT if I used "detachKeys": "ctrl-@,ctrl-]" and run Docker Desktop at startup, I will NOT be able to use CTRL+Q even if I close Docker Desktop.
Closing
Is this a bug? Is there a way to prevent docker from snatching CTRL+Q while still having it ran during Windows startup?
I don’t use docker keyboard shortcut anyway, if there is a way to disable all OS level shortcut I will do it.
Small feedback:
Personally I think CTRL+<KEY> should never be used for default OS level keyboard shortcut. If it prevent currently active window’s app to use such combination by default it should use SUPER key as modifier.
The config.json file is the docker client config file. It should not affect anything on Windows. The detach key is used when you use “docker attach” for example and you don’t want to stop the container, just detach.
I couldn’t find an app on my Windows that uses “CTRL + Q”, except Docker Desktop when I open the UI and I can close it with that. So it seems to be really strange and I think it must be a bug, so you can report it as @bluepuma77 suggested. If you do, please, share the issue link here for other users.
If I have to guess, I would say the issue could be caused by the optional Terminal feature in Docker desktop. At least that would be related to a terminal where the detack key would be relevant. So if you have that enabled, you can try to disable it.
I removed detachKey, and sometimes it works sometimes it doesn’t. And since the problem still sometimes happened even if I added “detachKey”. It probably just luck and it doesn’t affect anything.
I don’t touch this feature at all. “Enable Docker terminal” is left unchecked in the setting.
I recommend to update Docker to latest version and test again. There have been some releases, so there are updates and bug fixes. Then also update your issue.
Actually now I’m not sure if it’s Docker issue anymore.
The first app I suspect is Windhawk because it got fixed when I exit Windhawk, but after restart I can’t reproduce it anymore. But instead, it happened on Docker.
I suspect that it was actually caused by docker and that the reason it got fixed after I closed Windhawk is because it took quite a while for docker to quit. Because I close Windhawk after closing Docker.
However now I can’t reproduce it with Docker anymore. But instead it happened on other app. It currently happened on Clash Verge.
It might be Windows issue as I have used CTRL+Q in a video game on Linux for years and I never experienced this problem. But when I asked in Starcraft hotkey forum (TheCore), it seems like I’m the only one who experienced it. When I google CTRL+Q it seems like quite some people experience similar thing even the inconsistencies (magically fixed after restart) and it seems to be in different software forums.
It still could be some apps, but I don’t know which one is the culprit. And so my search continues.
I will close the Github issue then.