Description of problem: (not really sure what the component is, probably not mate-common). Using Fedora 31 with Mate, when selecting the option System > Shutdown > Suspend, the system initially suspends, but a second later it automatically wakes up again. This is what I see in dmesg: [ 1641.419441] PM: suspend entry (s2idle) [ 1641.432120] Filesystems sync: 0.012 seconds [ 1641.433379] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 1641.436154] OOM killer disabled. [ 1641.436156] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 1641.437613] printk: Suspending console(s) (use no_console_suspend to debug) [ 1641.438577] wlp2s0: deauthenticating from 48:8d:36:f5:24:20 by local choice (Reason: 3=DEAUTH_LEAVING) [ 1641.649169] psmouse serio1: Failed to disable mouse on isa0060/serio1 [ 1642.933559] PM: suspend devices took 1.496 seconds [ 1642.957372] ACPI: EC: interrupt blocked [ 1643.043043] ACPI: EC: interrupt unblocked [ 1643.262925] ath10k_pci 0000:02:00.0: unsupported HTC service id: 1536 [ 1644.191091] PM: resume devices took 1.109 seconds [ 1644.191093] OOM killer enabled. [ 1644.191094] Restarting tasks ... done. [ 1644.195851] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915]) [ 1644.235907] PM: suspend exit [ 1644.416231] mmc0: cannot verify signal voltage switch I guess the problem is in the line: [ 1641.649169] psmouse serio1: Failed to disable mouse on isa0060/serio1 But I don't really know. It happens whether I've got an external mouse connected or or not. If I try to suspend a second time immediately after, then it works. I'm using a Dell XPS. Version-Release number of selected component (if applicable): How reproducible: Happens every time Steps to Reproduce: 1. On the Mate menu, System > Shutdown Suspend Actual results: The system suspends just for a second, and then it keeps active. Expected results: The system is suspended until a key or something is pressed.
(In reply to Marc Garcia from comment #0) ... > (not really sure what the component is, probably not mate-common). ... I suggest changing the component to "kernel". Also, could you post the output from these commands: $ uname -r # kernel version $ journalctl -b --no-hostname -g 'DMI:' # laptop description This could be the same bug: Bug 1812010 - Kernel 5.5.7-200 does not suspend on Dell XPS-13
Thanks, but reporter can do that always for yourself, not need to call for help.
$ uname -r 5.5.8-200.fc31.x86_64 $ journalctl -b --no-hostname -g 'DMI:' -- Logs begin at Mon 2019-06-17 17:30:08 BST, end at Thu 2020-03-12 19:01:20 GMT. -- Mar 12 13:47:40 kernel: DMI: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.5.1 08/09/2018 I've also got a Dell XPS-13, so I guess this bug is related to 1812010, but the behavior is not exactly the same (in my case doesn't suspend correctly the first time).
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. 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 Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.