On this page
Hyprland
Wayland
Quickshell
QML
Two Desks, One Set of Hands
Deskflow Already Solved This — Just Not Where I Live
What It Actually Does
The Bug That Actually Mattered: Killing the Wrong Waynergy
The BugThe first version stopped waynergy the obvious way: find whatever process is named waynergy, send it a kill signal. That works fine right up until it doesn't — if a stale or blocked instance is sitting around anywhere on the system, "stop the current session" and "stop whichever one pgrep happened to match" are not the same instruction, and there was nothing distinguishing them.
The FixThe actual fix was to stop guessing by name and start tracking the specific process this plugin launched. waynergy runs detached — deliberately, so a plugin reload never kills a live session — which means there's no direct handle back to it. So the launch itself now goes through a small wrapper that backgrounds the process, captures its real PID, and writes it to a small state file. Every stop or status check after that verifies /proc/<pid>/comm still says waynergy before it trusts or signals that PID at all — closing off the exact race a plain name match couldn't see.
Verified Before ShippingI didn't just read that code and trust it. I ran the whole sequence by hand outside the plugin first — start it, capture the PID, verify the identity check, send the kill, confirm it actually stopped — before it went anywhere near the real UI. A clean-looking fix for a targeting bug is exactly the kind of thing worth not taking on faith.
The Other Bug: A Key That Wouldn't Let Go
SymptomThe second one is the one that actually prompted the fix, because I kept running into it myself: disconnect mid-keypress, and whatever key was down stayed down — logically held, as far as the OS on the receiving end was concerned — until I touched my desktop's own physical mouse or keyboard to clear it. Not dangerous, just genuinely annoying on a machine I was supposedly trying to make less friction, not more.
Root CauseThe reason turned out to be almost mundane: waynergy exposes a virtual input device, and if the connection dies mid-hold, that device never gets the clean release event it needs. Touching real hardware works because a fresh input event supersedes the stuck one at the OS level. Which meant the fix didn't need new hardware-level tooling at all — it needed the plugin to do the equivalent in software: detect the drop, and cleanly restart the session so that device gets torn down and rebuilt properly.
FixSo the plugin now actually checks that the connection is alive, not just that the process is running — a real TCP probe to the host, not an assumption — and if it stays unreachable for a few seconds (not on the first blip; a flaky network shouldn't trigger a restart storm), it stops and restarts waynergy on its own, up to a few attempts before it gives up and just tells me. No more reaching for a mouse to fix a keyboard.
Sharing Something Niche on Purpose
Try It Yourself
"The best fix for 'I have to touch real hardware to unstick this' turned out to be making the software let go properly in the first place."—Aryan Techie