Fedora KDE — Laptop does not properly enter/return from Sleep (Suspend)

Ask Fedora
,
1

Mouse and UI become unresponsive after waking from Sleep/Suspend – Fedora KDE Wayland

Hi Fedora community,

I am a Kubuntu user swich to fedora 1 month.

I’m experiencing a strange problem with Sleep/Suspend mode on Fedora KDE Plasma.

After the laptop wakes up from sleep, the display comes back normally, but mouse interaction and parts of the graphical interface become unresponsive.

Problem description

The problem happens after I put the laptop into Sleep/Suspend mode and then wake it up.

After waking:

  • The screen/display works normally.

  • The mouse cursor is visible.

  • I can move the mouse cursor.

  • Left-click does not work.

  • Right-click does not work.

  • Mouse scrolling does not work.

  • Applications appear to be partially frozen.

  • When I move the mouse over application icons or other UI elements, there is no hover response.

  • Clicking application icons does nothing.

  • The keyboard continues to work normally.

  • I can type using the keyboard.

  • The system does not appear to be completely frozen because keyboard input still works.

So it feels like the mouse input and graphical UI interaction become frozen at some point during suspend/resume.

The cursor itself can still move, but mouse buttons and scrolling do not work.

For example, after waking up, if I move the mouse over an application icon on the taskbar, normally the icon should react to the mouse hover. Instead, there is no visual response at all.

This makes it seem like this may be more than just a physical mouse problem.

I also tried changing the suspend mode

Initially, the system was using:

s2idle

I also tried changing the system to use S3 / deep sleep instead of s2idle.

Unfortunately, the problem still occurs after switching to S3.

So the issue does not appear to be specific to s2idle.

Both suspend methods result in the same behavior after resume.

What I have tried

When the problem occurs, I tried restarting/reloading Plasma.

I tried:

systemctl --user restart plasma-plasmashell.service

and:

plasmashell --replace &

Unfortunately, this did not fix the problem.

The mouse still moves, but:

  • left-click does not work;

  • right-click does not work;

  • scrolling does not work;

  • application icons do not react to hover;

  • clicking applications does nothing.

Logs after waking from Sleep

I also checked the system logs around the suspend/resume event.

The system reports the suspend/resume process, including:

PM: suspend entry (s2idle)
PM: resume devices took 0.149 seconds
PM: suspend exit

There are also messages from the Intel graphics driver (i915) during the resume process.

The suspend/resume operation itself appears to complete successfully, and the display comes back normally.

However, the graphical interface is not fully functional afterwards.

I’m not sure whether the i915 messages are relevant or simply normal messages during resume.

System information

Operating System: Fedora Linux 44
KDE Plasma Version: 6.7.4
KDE Frameworks Version: 6.29.0
Qt Version: 6.11.2
Kernel Version: 7.1.12-200.fc44.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz
Memory: 20 GiB of RAM (19.2 GiB usable)
Graphics Processor: Intel® Iris® Plus Graphics
Manufacturer: LENOVO
Product Name: 81VW
System Version: Lenovo IdeaPad S340-15IIL

What could be causing this?

At first I thought this might be a mouse or input-device problem.

However, because the following things happen at the same time:

  • mouse movement still works;

  • mouse clicks don’t work;

  • mouse scrolling doesn’t work;

  • application hover effects don’t work;

  • application icons cannot be clicked;

  • applications appear to be unresponsive;

  • keyboard input continues to work;

I’m wondering whether the problem could be somewhere in the Wayland/KWin/Plasma input or event-processing pipeline, rather than the physical mouse itself.

Possible components involved might include:

  • KDE Plasma

  • kwin_wayland

  • Wayland

  • libinput

  • systemd-logind

  • Linux kernel

  • Intel i915

  • suspend/resume handling

  • interaction between KWin/Wayland and input devices after resume

I also tried switching from s2idle to S3/deep sleep, but the problem remained the same.

All sleeping model working on kubuntu 24.04 (x11)
i have install fedora 44 the last month, and faced this problem.

How can I troubleshoot this?

Any advice on how to properly diagnose this issue would be greatly appreciated.

Thank you!