Bug 426746 - keyboard input is slow on Wayland and can result in repeated characters, like "fireefoox"
Summary: keyboard input is slow on Wayland and can result in repeated characters, like...
Status: RESOLVED FIXED
Alias: None
Product: krunner
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Kai Uwe Broulik
URL:
Keywords:
: 427752 427775 (view as bug list)
Depends on:
Blocks:
 
Reported: 2020-09-19 19:48 UTC by Patrick Silva
Modified: 2020-10-30 07:54 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In: Plasma 5.20 and Frameworks 5.76


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Silva 2020-09-19 19:48:29 UTC
SUMMARY
I can reproduce on both Arch (Plasma 5.20 beta) and neon unstable.

STEPS TO REPRODUCE
1. start Wayland session
2. open krunner by presing alt+space
3. type some search term
4. delete typed characters by pressing backspace

OBSERVED RESULT
typed/deleted characters take a few seconds to appear/disappear
and some typed characters are repeated, resulting in things like "fireefoox"

EXPECTED RESULT
normal keyboard input

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.19.90
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.0

Operating System: Arch Linux
KDE Plasma Version: 5.19.90
KDE Frameworks Version: 5.74.0
Qt Version: 5.15.1
Comment 1 Rainer Finke 2020-09-26 16:15:33 UTC
Yes, it is terribly slow. I think this is a regression compared to Plasma 5.19.

Operating System: Arch Linux
KDE Plasma Version: 5.19.90
KDE Frameworks Version: 5.74.0
Qt Version: 5.15.1
Kernel Version: 5.8.11-arch1-1
OS Type: 64-bit
Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor
Memory: 31.4 GiB of RAM
Graphics Processor: AMD Radeon VII
Comment 2 Alexander Lohnau 2020-09-26 18:49:10 UTC
Also noted this and it seems like a regression. We are looking into it :)
Comment 3 Alexander Lohnau 2020-10-08 07:32:05 UTC
I have found the commit which caused this.

If you can't live without KRunner in the meantime you could try out the "Search" plasmoid and assign a shortcut to it.
Comment 4 Aleix Pol 2020-10-08 15:57:15 UTC
Git commit c212564f88513c29e420ffb192ac29a3707169b0 by Aleix Pol.
Committed on 08/10/2020 at 15:37.
Pushed by apol into branch 'master'.

krunner: improve the logic of the busy indicator

Only show it after a bit of querying (500ms), disable it as soon as the
query ends.

M  +6    -5    lookandfeel/contents/runcommand/RunCommand.qml

https://invent.kde.org/plasma/plasma-workspace/commit/c212564f88513c29e420ffb192ac29a3707169b0
Comment 5 Aleix Pol 2020-10-08 16:07:04 UTC
Git commit 9835ae1bbd822e1ae11143005dbec822aea4fb2b by Aleix Pol Gonzalez, on behalf of Aleix Pol.
Committed on 08/10/2020 at 16:06.
Pushed by apol into branch 'Plasma/5.20'.

krunner: improve the logic of the busy indicator

Only show it after a bit of querying (500ms), disable it as soon as the
query ends.


(cherry picked from commit c212564f88513c29e420ffb192ac29a3707169b0)

M  +6    -5    lookandfeel/contents/runcommand/RunCommand.qml

https://invent.kde.org/plasma/plasma-workspace/commit/9835ae1bbd822e1ae11143005dbec822aea4fb2b
Comment 6 Aleix Pol 2020-10-08 16:41:04 UTC
Git commit e0e7840a0307deaee7a0b63f341973f8e3508873 by Aleix Pol.
Committed on 08/10/2020 at 16:14.
Pushed by apol into branch 'master'.

BusyIndicator: Do not rotate when invisible

It seems like the "visible" property is catching there is the wrong one
and would still rotate while invisible.

M  +2    -1    src/declarativeimports/plasmacomponents3/BusyIndicator.qml

https://invent.kde.org/frameworks/plasma-framework/commit/e0e7840a0307deaee7a0b63f341973f8e3508873
Comment 7 Patrick Silva 2020-10-15 17:58:06 UTC
*** Bug 427752 has been marked as a duplicate of this bug. ***
Comment 8 Alexander Lohnau 2020-10-15 19:41:00 UTC
*** Bug 427775 has been marked as a duplicate of this bug. ***
Comment 9 Patrick Silva 2020-10-18 16:19:07 UTC
*** Bug 427921 has been marked as a duplicate of this bug. ***