Bug 461619 - When using a chromium based application/browser typing is very laggy on Wayland.
Summary: When using a chromium based application/browser typing is very laggy on Wayland.
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: neon
Classification: KDE Neon
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords: usability, wayland-only
Depends on:
Blocks:
 
Reported: 2022-11-09 01:01 UTC by card_craft
Modified: 2025-09-20 12:31 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description card_craft 2022-11-09 01:01:44 UTC 
SUMMARY
***
Every time i use VScodium or brave browser everything i type gets very buggy and lagged. sometimes resulting in doubled letters or some not registering. 

STEPS TO REPRODUCE
1. Use a chroeium application (Brave/VSCode(ium))
2. type
3. wait for your characters to appear

OBSERVED RESULT
Laggy and incorrect typing experience

EXPECTED RESULT
perfect and instant typing

SOFTWARE/OS VERSIONS

Kde Neon

(available in About System)
KDE Plasma Version: 5.26.2
KDE Frameworks Version: 5.99.0
Qt Version: 5.15.7

ADDITIONAL INFORMATION

Behavior not observable on plasma X11
Comment 1 card_craft 2022-11-09 17:48:46 UTC 
This also seems to happen when using dropboxes or radio selections
Comment 2 Patrick Silva 2022-11-10 02:08:29 UTC 
Can confirm keyboard input lag with Discord on Arch Linux running Wayland session of Plasma 5.26.3.
Comment 3 Carlos De Maine 2025-09-20 09:36:23 UTC 
Thank you for your bug report! 
However this bug report was created/provided previous to 01/01/2023 and also has not received any updates since  before 01/01/2025. 
Unfortunately KDE neon no longer provides updates for anything older than noble 24.04 based edition's.
Please upgrade to KDE neon noble and if you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report.
Thanks for understanding!