Bug 2350976 - kwin_wayland_wrapper - Key repeat discarded - Kwin crashes session on audible notification
Summary: kwin_wayland_wrapper - Key repeat discarded - Kwin crashes session on audible...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: pipewire
Version: 41
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-03-09 19:07 UTC by Robin Laing
Modified: 2025-12-16 19:04 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-12-16 19:04:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 2354295 0 unspecified CLOSED kwin_wayland_wrapper[17692]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! 2025-12-17 04:34:25 UTC

Description Robin Laing 2025-03-09 19:07:28 UTC
Deleting characters in file list causing an audible alarm, causing system to repeat the audible alert.  Session is almost unresponsive.  No mouse clicks work but pointer moves.  Can get into console session with keystrokes.

Process show pipewire at close to 100%.  Kill pipewire and session is still locked up.

Journal fills with 
"kwin_wayland_wrapper[253233]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!"

Had this issue with flatpacks and appimages as well.  If some function causes an audible notification and is not a native Plasma program.  FreeCAD, PrusaSlicer are two recent applications that this has occurred with.

Reproducible: Always

Steps to Reproduce:
1.Fresh session.  Open geeqie
2.Go into file location box and use backspace to delete the present path till notification that there are no more characters.
3.Session is borked.
Actual Results:  
Computer starts a loop of audible notifications sounds, mouse movement are slow.  Mouse buttons don't work.  Keyboard won't allow you to enter any characters in the kwin session.  Can move to console which works normally.  If trying to go back to session or original user selection login screen, both are blank and keyboard is now locked out.  Only hard shutdown works.  With the repeated sound, pipewire is close to 100% of a CPU.  Audio continues to work.  In once case, Clementine continued to play music, even in the console session which is shouldn't do.

Expected Results:  
Notification that the end of the entry box has been reached.  Session continues.

I have had this happen in appimages, FreeCAD and Arduino IDE.  Also in flatpack, PrusaSlicer.

In all cases, it is related to notification of some type.  Audio pings are continuous and constant.  They do not stop.

Journal logs are full of this message and it will repeat until kwin session is stopped or computer is shutdown.  Cannot start a new session until computer is rebooted.

kwin_wayland_wrapper[4617]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!

kwin_wayland_wrapper[253233]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!

It is related to the process that causes the crash.  I have repeated the crash with geeqie as that is the one that has the least effect on my system

Comment 1 Robin Laing 2025-03-11 22:42:36 UTC
More information.

I have had one accidental crash when using KiCAD and a forced crash to gather some data.

Crashed in two different accounts on the same system machine.  Has not happened on a different machine.

On a crash, wireplumber goes to almost 100% until the application that caused the crash is killed.  Killed process by ssh and by entering a different local terminal.  Same effect.

If music is playing on the account, it continues in the background of the notification and after the notification alert stops.

journal logs keep filling with 
kwin_wayland_wrapper[4617]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!

until I change to a local terminal.  (ctrl+alt+f5)

I see some of these within the journal messages. Might be related.
Reverse order 
plasmashell[3644]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1b.0.analog-stereo.monitor"
plasmashell[3644]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1b.0.analog-stereo.monitor"
plasmashell[3644]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1b.0.analog-stereo.monitor"
plasmashell[3644]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1b.0.analog-stereo"
plasmashell[3644]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1b.0.analog-stereo.monitor"
plasmashell[3644]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1b.0.analog-stereo"
plasmashell[3644]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1b.0.analog-stereo.monitor"
plasmashell[3644]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1b.0.analog-stereo"
plasmashell[3644]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1b.0.analog-stereo.monitor"
plasmashell[3644]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1b.0.analog-stereo.monitor"
kwin_wayland[3451]: kwin_core: Applying output config failed!

One thing that I find strange on this computer is the audio from Clementine will continue to play, even when I change to a tty.  I have never seen that on a Fedora machine before.

Not sure if this is related. This is among the processing events log entry.  Reverse entry -r flag.

Mar 11 15:43:19 XXX kwin_wayland_wrapper[3558]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
Mar 11 15:43:19 XXX kwin_wayland_wrapper[3558]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
Mar 11 15:43:19 XXX kwin_wayland_wrapper[3558]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
Mar 11 15:43:19 XXX kwin_wayland_wrapper[3558]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
Mar 11 15:43:19 XXX audit: BPF prog-id=77 op=UNLOAD
Mar 11 15:43:19 XXX kwin_wayland_wrapper[3558]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
Mar 11 15:43:19 XXX audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/sys>
Mar 11 15:43:19 XXX systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Mar 11 15:43:19 XXX kwin_wayland_wrapper[3558]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!


Mar 11 15:42:35 XXX kwin_wayland[3451]: kwin_wayland_drm: The main thread was hanging temporarily!


Mar 11 15:42:19 XXX kwin_wayland_wrapper[3558]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
Mar 11 15:42:19 XXX kwin_wayland_wrapper[3558]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
Mar 11 15:42:19 XXX systemd[3352]: dbus-:1.2-org.kde.KSplash: Failed with result 'exit-code'.
Mar 11 15:42:19 XXX systemd[3352]: dbus-:1.2-org.kde.KSplash: Main process exited, code=exited, status=1/FAILURE
Mar 11 15:42:19 XXX plasma_waitforname[4090]: org.kde.plasma.waitforname: WaitForName: Service was not registered within timeout
Mar 11 15:42:19 XXX kwin_wayland_wrapper[3558]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!

Comment 2 Robin Laing 2025-03-31 20:24:35 UTC
Today I had a crash and found out that if I login remotely and kill pipewire processes, I get control of the system again.  I am changing the component to pipewire due to this evidence. 

I can keep repeating the issue.  Today it occurred in KiCAD while trying to change a directory.  

From journal after pipewire processes were closed.

pipewire[3675]: mod.x11-bell: canberra context open error: IO error

pipewire[3675]: mod.x11-bell: canberra context open error: IO error

 kded6[3773]: org.kde.pulseaudio: context kaput

plasmashell[3820]: org.kde.pulseaudio: context kaput

Seconds before the lockup I had some of these messages in the journal

kwin_wayland[3620]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11

Not everyone has the ability to remotely login and close off services.

May be related to this bug as well.
https://bugzilla.redhat.com/show_bug.cgi?id=2354295

Comment 3 Adam Williamson (Red Hat non-Fedora) 2025-12-02 02:34:49 UTC
This message is a reminder that Fedora Linux 41 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 41 on 2025-12-15.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '41'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 41 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Samyak Jain (RedHat) 2025-12-16 19:04:35 UTC
Fedora Linux 41 entered end-of-life (EOL) status on 2025-12-15.

Fedora Linux 41 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.