Launcher makes screen unusable
Closed this issue · 4 comments
The launcher has a feature that makes anything other than the launcher unable to detect the mouse (for example, the hover effects on the taskbar don't work or the windows don't get focused).
This is completely fine, the problem is that sometimes it does that even if the launcher is closed, resulting in a completely unusable screen. You can't click, focus windows, type, or do practically anything other than the hyprland shortcuts (you can open a terminal with Super+Q but you can't actually type in it). Stopping and starting EWW doesn't fix this and the only way to get out of the frozen state is by logging out and in again.
You can trigger this bug by opening and closing the launcher a bunch of times (I usually use the shortcut), it appears to be somewhat random but it will happen.
It shouldn't matter but I'm on EndeavourOS and using AMD integrated graphics.
It turns out that the :focusable true property in windows.yuck line 31 is what is causing this issue. It's not a problem with this configuration, it's an issue with eww (issue #651).
As a workaround I've set the focusable property to false.
Edit: I suspect that there's something wrong with the launcher though but I'm investigating it: the launcher lags when I open it and sometimes running eww kill doesn't close some things like the taskbar
now that I have focusable set to false and I can use the computer after the launcher breaks I've discovered that it turns out that opening and closing it repeatedly causes another eww process to start, I don't know why though.
Ok, so after testing several things, I can't find what is creating the eww processes, but running ~/.config/eww/scripts/start.sh temporarily fixes the original problem.
In the end I've set the focusable property back to true (setting it to false made the search bar unusable) and I've set a shortcut to Super+R to reload eww (runs start.sh), this way I can reload eww as many times as I need.
forgot to close this, the version of the dotfiles where I had this issue is very old. The current one doesn't even use eww