Bug 496302 - Extreme laggy text input on the desktop environment with AMD 780M GPU
Summary: Extreme laggy text input on the desktop environment with AMD 780M GPU
Status: RESOLVED UPSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 6.2.3
Platform: Arch Linux Linux
: NOR major
Target Milestone: ---
Assignee: KWin default assignee
URL: https://gitlab.freedesktop.org/drm/am...
Keywords:
Depends on:
Blocks:
 
Reported: 2024-11-15 14:35 UTC by pablogarcialopez234
Modified: 2024-11-21 16:54 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed 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 pablogarcialopez234 2024-11-15 14:35:26 UTC 
After updating with pacman the system, it has extreme laggy text input only in the system graphical enviroment. (settings, konsole (unuseful), search bars, login screen,kate etc.) Firefox and Clion work OK and also tty so not a keyboard issue.


Operating System: EndeavourOS 
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Kernel Version: 6.11.7-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 PRO 8840U w/ Radeon 780M Graphics
Memory: 14.3 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Comment 1 David Edmundson 2024-11-21 15:10:12 UTC 
>Firefox

If Firefox works ok it's unlikely to be a kwin issue either. All input goes through kwin.

Can you run

WAYLAND_DEBUG=1 kwrite |& grep keyboard

and see if there is a lag between pressing a key and getting debug out?

Also can you check if you have any environment variables starting with QT_
Comment 2 Nate Graham 2024-11-21 15:31:07 UTC 
I can reproduce this intermittently, and it started appearing a few days ago for me as well, after updates. I'm almost positive it's not a KDE issue though:
- It affects my stable session as well as my built-from-source session
- It happens when using older kernels as well as the latest one

My guess right now is an AMD GPU driver or mesa regression. Notably I'm also using a Radeon 780M Graphics GPU, and a Ryzen 7 7840U CPU (same as your 8840U but without the NPU).
Comment 3 pablogarcialopez234 2024-11-21 15:40:01 UTC 
	Hi there, I tried older kernel versions, but nothing changed. So, I downgraded the entire system to the version from November 1, 2024, by changing the repository links in pacman.conf to point to that date. This resolved the issue, which means it must be caused by a recent package update. I also performed a clean installation to rule out any corrupt packages, but as soon as I ran pacman -Syu, the bug reappeared. Currently, I’m not sure if the latest updates have resolved the issue.
Comment 5 Nate Graham 2024-11-21 15:50:27 UTC 
Others:
- https://gitlab.freedesktop.org/drm/amd/-/issues/3742
- https://gitlab.freedesktop.org/drm/amd/-/issues/3658

Lots of upstream chatter about this. Hopefully it'll be fixed soon.
Comment 6 Nate Graham 2024-11-21 15:59:12 UTC 
Going down to 48Hz refresh rate works around it for now. Crappy workaround, but it is a working workaround.