-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keyboard input doesn't follow active window, when quickly swith between two workspaces back and forth. #5808
Comments
Here's another issue that I believe may be related. |
I have the same problem, I fixed it by install the latest version (hyprland-git), but my waybar and pyprland crashed, fortunately, they can be fixed by install latest version too |
I seem to be experiencing a similar issue in my environment. I'm leaving this comment so that others who might think it's a Fcitx issue can find this issue through search. I used to think as mentioned above, but it seems I might have had another issue. The following issue could be related. |
#5763 It is already fixed in git. You can either
|
Thank you so much!! I was very troubled by the same problem. The workaround solves it! |
Hyprland Version
System/Version info
Bug or Regression?
Bug
Description
Occasionally, when I navigate between workspaces, my keyboard inputs do not follow me but remain active in the last workspace I left. This issue occurs most frequently when I switch from a workspace containing a browser to one with a
terminal. Sometimes, the problem even arises within the same workspace when I switch between windows.
How to reproduce
Suppose I'm working with two workspaces( abbreviated as
ws
in this text).In
ws-1
, I have a browser open, and inws-2
, there's a terminal. Currently, I'm inws-2
.If I quickly switch to
ws-1
and then immediately back tows-2
, all my keyboard inputs are mistakenly sent to the browser inws-1
. To resolve this and redirect my inputs back to the terminal inws-2
, I am forced to switch again tows-1
and then back tows-2
, only then does the cursor respond in the terminal as expected.Crash reports, logs, images, videos
No response
The text was updated successfully, but these errors were encountered: