https://bugs.kde.org/show_bug.cgi?id=433056

            Bug ID: 433056
           Summary: Holding down a key doesn't get interpreted as key
                    repetition (broken by yesterday's plasma updates)
           Product: neon
           Version: unspecified
          Platform: Neon Packages
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: Packages User Edition
          Assignee: neon-b...@kde.org
          Reporter: geisse...@gmail.com
                CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

SUMMARY
Before the updates from 16th Feb afternoon, when holding down a key for a
longer time, it got correctly interpreted as repeated key presses, so that
holding down a key would repeat that character or action with a fixed speed as
long as the key is pressed. This is very useful for del/backspace in particular
and definetely the desired behaviour.
Yesterday's updates to Plasma 5.21 broke that. Holding down a key only triggers
the action one time, and does not recognise that it should actually be
repeated. I personally find this behaviour rather disturbing for my workflow.

STEPS TO REPRODUCE
1. Use up-to-date KDE Neon User
2. hold down a key (space or backspace, for instance)
-> the action won't be repeated as it should

OBSERVED RESULT
When holding down a key, it gets interpreted as one single key press and is not
repeated

EXPECTED RESULT
While a key is held down, its actions should be repeated.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.21
KDE Plasma Version: 5.21.0
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
Kernel Version: 5.4.0-65-generic
OS Type: 64-bit
Graphics Platform: Wayland

ADDITIONAL INFORMATION
Both Wayland and X11 are affected
My input method is set to ibus as described in
https://bugs.kde.org/show_bug.cgi?id=411729#c4 (but reverting the environment
variables related to ibus didn't change anything)

Since I have no clue which of the many packages updated with the move to Plasma
5.21 is causing this bug, I decided to report this here in Neon issues.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to