-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
GUI issues on Ubuntu 22.0.4 LTS #2703
Comments
From this phenomenon it looks and feels like a problem with the terminal or system settings? |
I agree |
I experienced the same behavior, but I was lazy and installed another terminal. I don't have the same issue there. As @wjiec mentioned, the issue could be terminal or system settings related. Previously I used this terminal emulator: https://gitlab.gnome.org/GNOME/console |
Thanks for the advice and tips. I've installed the Yakuake terminal and can confirm everything works normally there. I was also using Gnome previously. I'll leave it to the maintainers to decide whether this issue should now be closed or whether it should be kept open, either because there is still something somebody wants to look at or in case others come across the same issue. |
Describe the bug
First, thanks for this wonderful library! I'm experiencing some very strange behaviour which I hope somebody can shed some light on. The keys do not behave as expected, e.g. if I press the UP arrow several times and then switch to pressing the DOWN arrow, the first press of the DOWN arrow is interpreted as an UP and vice versa; and if I press CTRL+F to start port forwarding on a pod, the pod above the one I had selected is opened. The overall impression is that there is an event queue where the each event is only processed once a second event is added so that the first event is in penultimate position in the queue.
What is weirdest is that if I ssh into the same machine from elsewhere, k9s works exactly as expected.
I have checked with
evtest
that there is no obvious issue with my keyboard.To Reproduce
Steps to reproduce the behavior:
Historical Documents
Expected behavior
Normal key assignments / behaviour.
Versions (please complete the following information):
Additional context
This all worked fine until about a week ago.
The text was updated successfully, but these errors were encountered: