Disclaimer: I am not sure if KWin is to blame here. However, it seems involved in the issue. In Emacs, certain key combinations (e.g., Ctrl+G) ring the bell (if not configured otherwise). On my system, this produces an audible sound. When I press and hold, e.g., Ctrl+G the whole system freezes while the bell sound is played repeatedly (a new sound is started before the previous one is finished). The system stays in that state (including the bell sounds) after releasing the keys. The system needs to be hardly turned off. When this occurs, the following message is written a lot to the journal (around 25 times per second according to the timestamps): > kwin_wayland_wrapper[1993]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! So the system at least keeps logging while it appears frozen and is unresponsive to user input. Unfortunately, I was able to reproduce this behavior only with Emacs. Disabling the bell in Emacs works around this issue. I only found one other application that similarly rings the bell, namely xterm, however, with this one the next bell sound in played only after the previous one finished and the problem does not occur. It also occassionally produces the journal message, however, by far not as rapidly as with Emacs. There might be an issue with Emacs. However, since the whole system freezes, I guess other components (KWin?) are involved as well. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.2 Kernel Version: 6.13.7-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 15,4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: LENOVO Product Name: 20L50000GE System Version: ThinkPad T480
*** This bug has been marked as a duplicate of bug 500916 ***
This will be fixed in 6.3.4
(In reply to Nicolas Fella from comment #1) > > *** This bug has been marked as a duplicate of bug 500916 *** Oh, sorry for the noise. While searching for existing issues, I did not notice that the search is limited to open issues by default.