* John Kizer via openSUSE Users <users@lists.opensuse.org> [09-07-23 12:31]:
mh＠mike.franken.de wrote:
On Mittwoch, 6. September 2023 21:05:50 CEST John Kizer via openSUSE Users wrote:
mh＠mike.franken.de wrote: On Donnerstag, 11. Mai 2023 22:54:40 CEST mh@mike.franken.de wrote: Hi *, for some time now I have a problem with the keyboard on my notebook. It becomes extremely slow, i.e. only one or two keypresses are shown every 10 seconds. Special keyboard shortcuts like Alt-F4 or Ctrl-F5 are working as expected. Switching to a Linux console with Ctrl-Alt-[0-9] is still working, too. In the Linux console typing works without any problems then. Switching back to KDE again/still shows the problem. The only "solution" I found is to logout and login. For a while the keyboard then works as expected, until the same problem reoccurs. The intervals the problem shows up vary between once an evening to every 10 minutes. It happens in all programs one can type anything, i.e. OO Writer, graphical terminals or even dialog boxes of any kind. It happens with the internal notebook keyboard and also with an external USB keyboard. Machine: Type: Convertible System: Dell product: XPS 13 9310 2-in-1 v: N/A ´ openSUSE Tumbleweed 20230509 Any idea, what the reason might be and what to do against it? the problem still exists. After having tested everything, I could think of, and following some advice given here in the list, I have no idea, where to go next. I moved my home directory away and started over with an empty one. For a while the problem didn't occur, but after about 10 days it was back. I created a new user - and again: For a while the problems didn't occur, but after about 10 days it was back. I used xfce4 instead of KDE - and again, ... I tested all keys and detected, that only the character keys, the numeric keys and a few special keys like escape are affected, but only, if they are used to type text. If I use them to jump to a file in dolphin or a mail in kontact by typing the first character of an element, they are working without a problem. function and cursor keys always work as expected. Still there are no entries in the journal or any other log. Sometimes the problem gets worse while trying to debug it - KDE (xfce4) functions stop working, i.e. menus are no longer shown, systemsettings can't be started, logoff does not work, ... It seems as if the GUI slowly, but steadily is dying. Changing to a console, killing the session and login back in always solves the problem - until it reoccurs, which happens a few minutes to a few days later. A complete memory check doesn't show any problem. Anyone any further idea? TIA. Bye. Michael. I'm wondering if perhaps there's some connection between the keyboard layout/locale configuration and this issue - check out this link for what sounds like a possibly related issue and idea for a fix? https://www.reddit.com/r/pop_os/comments/u5ao31/comment/i517bsk/?utm_source= share&utm_medium=web2x&context=3 I defined "German (with deadkeys)" in Yast's keyboard settings, but as for KDE, I don't have any keyboard layout definitions in the list. I defined "American English" in "Regional settings" with everything else set to "German" and my environment contains LANG=en_US.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_CTYPE=en_US.UTF-8 LC_TIME=de_DE.UTF-8 LC_NUMERIC=de_DE.UTF-8 Not sure, what to change here? Should I add a German keyboard layout to the list? Thanks, John Kizer Thx for your hint! Bye. Michael.
Looking back at the original problem...what you're describing sounds a bit like the "Slow Keys" accessibility feature, too? Have you checked to see if that is perhaps accidentally getting enabled?
And because I think that's something that the X11 server itself handles, maybe try seeing if you notice the same issue when logging into KDE Plasma in the Wayland session?
Also, silly question probably, but your keyboard is actually physically a German layout keyboard, correct? (Thinking if it's not physically a German layout keyboard, that might throw off interpretation of inputs somehow...perhaps even by incorrectly sending a signal for shift that might trigger the "hold down shift for 8 seconds to enable slow keys" feature?)
Lots of guesses on my part, but hopefully something there might relate in some way to the solution!
Thanks,
John Kizer
I would look at what xset provides. just saying -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc