Where to report this bug? Fedora 40 and Ubuntu 24.04 don't suspend if you provide mouse input after you click on suspend

Ask Fedora
, , ,
1

On Fedora 40, when you click on sleep on KDE plasma to suspend, or when you click on suspend on Gnome, and afterwards you immediately start moving the mouse and clicking on the mouse, the system does not suspend and instead freezes so it has to be either forcefully shut down by pressing and holding the power button or you have to press Ctrl+alt+f5 or some other function key to log in and then reboot the system. This bug also happens on Ubuntu 24.04. if I don’t misremember at least on KDE you have a chance at saving the system by pressing CTRL+Alt+F2 and then logging in.

I don’t know how Linux goes into suspend, so where can this bug be reported? It’s not exclusive to Fedora.

Edit if it helps I am using a wireless usb Microsoft mouse on a Lenovo 15ach6h with Nvidia graphics, doesn’t seem to matter if it’s running nouveau or proprietary Nvidia drivers

2

Added f40, gnome, kde, suspend-resume

3

I wonder if the fact that you move and click the mouse is seen as a reason to ignore the request to suspend?

Why do you click the mouse after selecting to suspend?

4

I bumped my mouse after I clicked on suspend and that froze my system. So later I decided to click my mouse after clicking on suspend and that reproduces the bug reliably

5

I tried and I can’t reproduce this bug, neither with a USB nor with a bluetooth mouse, I tried it several times, but my T470s goes to sleep and wakes up as expected.

6

comparing these two journalctl logs, which cover the suspend and resume processes, taken with kde plasma 6.2 as the desktop environment:

from my machine, there are several things that stand out to me on the failed suspend log that aren’t present in the normal suspend log. I cut the logs just before they revealed the name of my wifi network

there’s this error:

fedora fprintd[4578]: Failed to install a sleep delay inhibitor: GDBus.Error:org.freedesktop.login1.OperationInProgress: The operation inhibition has been requested for is already running

This is where things start to go wrong.

fedora kernel: Wakeup pending. Abort CPU freeze
fedora kernel: Non-boot CPUs are not disabled

it seems that, fedora does not disable the processor to complete the sleep process. There is no indication in the logs, that this is caused by the USB mouse, even though it only happens when i click on both mouse buttons repeatedly, quickly and randomly, and simultaneously move the mouse quickly and randomly after clicking on sleep in kde plasma. Maybe the kernel is not completely ignoring mouse input? Because of the line that says, wakeup pending?

when resuming, this line:

fedora kernel: ACPI: PM: Restoring platform NVS memory

is missing from the failed suspend log probably because the processor was never turned off. and these lines are missing too:

fedora kernel: usb 3-4: reset high-speed USB device number 3 using xhci_hcd
fedora kernel: usb 1-3: reset high-speed USB device number 3 using xhci_hcd

probably because of the same reason. Device number 3 is the transceiver for my wireless mouse which is the microsoft wireless mobile mouse 1850.

in the failed suspend log the line that says

fedora kernel: PM: resume devices

appears twice. it seems the system tries to suspend twice.

I am running kernel version 6.10.12-200.fc40.x86_64 maybe I should post more of the logs after my system connects to wifi but I couldn’t see any other errors or anything of the sort so it seems the kernel works fine after resuming from the failed suspend but for some reason KDE doesn’t appear soon after resuming from the failed suspend

7

I was clicking and moving the mouse for about 10 seconds after clicking suspend or sleep to get the bug to trigger.

Now in kernel version 6.11, if you click on sleep in KDE plasma and then immediately start moving the mouse randomly and clicking on both of its buttons randomly, and do it without ever stopping for a while, eventually the system recovers on its own and the log in screen shows up after less than a minute and you can log back in. However if you ever stop the system still freezes. So if you happen to bump into the mouse after clicking on sleep, the system will still freeze and it won’t be recoverable by pressing Ctrl-alt-f3 so you will have to force a shutdown by pressing and holding the power button of the laptop for 5 seconds.

8

it seems this only happens with certain models of mice. testing with a maxell mowl-100 wireless mouse plugged into the computer using the usb dongle included with the mouse, the issue did not occur. tested on fedora 41 with kde plasma 6.2.2