I just switched from Fedora back to Ubuntu 22.04 and I can’t get suspend to work. It will log me out, turn off my WiFi and screen, but it will never “sleep”. So it can’t ever hibernate because it doesn’t properly suspend. If I move the mouse around or press a key on the keyboard, the screen will come back on and it’ll let me log in again.
What’s funny is that I’ve had Ubuntu 22.04 on here before (Linux Mint 21) and it didn’t have this issue, and it didn’t have this issue on Fedora 37 either…
Happy to help. What is the output of:
journalctl | grep suspend
and
journalctl | grep resume
Also what peripherals are attached?
Suspend:
Mar 25 16:56:11 bluelazer kernel: nvme 0000:01:00.0: platform quirk: setting simple suspend
Mar 25 16:58:47 bluelazer kernel: nvme 0000:01:00.0: platform quirk: setting simple suspend
Mar 26 10:52:41 bluelazer ModemManager[860]: <info> [sleep-monitor-systemd] system is about to suspend
Mar 26 10:53:29 bluelazer kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Mar 26 12:02:32 bluelazer ModemManager[866]: <info> [sleep-monitor-systemd] system is about to suspend
Mar 26 12:02:32 bluelazer systemd-sleep[116673]: Entering sleep state 'suspend'...
Mar 26 12:02:32 bluelazer kernel: PM: suspend entry (s2idle)
Mar 26 17:16:28 bluelazer kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Mar 26 17:16:28 bluelazer kernel: PM: suspend exit
Mar 26 17:16:28 bluelazer systemd[1]: systemd-suspend.service: Deactivated successfully.
Mar 26 17:16:49 bluelazer ModemManager[866]: <info> [sleep-monitor-systemd] system is about to suspend
Mar 26 17:16:49 bluelazer systemd-sleep[117332]: Entering sleep state 'suspend'...
Mar 26 17:16:49 bluelazer kernel: PM: suspend entry (s2idle)
Mar 27 05:49:54 bluelazer kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Mar 27 05:49:54 bluelazer kernel: PM: suspend exit
Mar 27 05:49:54 bluelazer systemd[1]: systemd-suspend.service: Deactivated successfully.
Mar 27 06:09:13 bluelazer ModemManager[866]: <info> [sleep-monitor-systemd] system is about to suspend
Mar 27 10:25:32 bluelazer ModemManager[893]: <info> [sleep-monitor-systemd] system is about to suspend
Mar 27 10:25:33 bluelazer systemd-sleep[144003]: Entering sleep state 'suspend'...
Mar 27 10:25:33 bluelazer kernel: PM: suspend entry (s2idle)
Mar 27 10:26:03 bluelazer kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Mar 27 10:26:03 bluelazer kernel: PM: suspend exit
Mar 27 10:26:03 bluelazer systemd[1]: systemd-suspend.service: Deactivated successfully.
Mar 27 10:28:37 bluelazer sudo[158265]: joe : TTY=pts/20 ; PWD=/home/joe ; USER=root ; COMMAND=/usr/bin/ln -nsT /usr/lib/systemd/system/systemd-suspend-then-hibernate.service /etc/systemd/system/systemd-suspend.service
Mar 27 10:29:15 bluelazer sudo[161586]: joe : TTY=pts/20 ; PWD=/home/joe ; USER=root ; COMMAND=/usr/bin/rm /etc/systemd/system/systemd-suspend.service
Mar 27 10:31:02 bluelazer sudo[168077]: joe : TTY=pts/20 ; PWD=/home/joe ; USER=root ; COMMAND=/usr/bin/systemctl suspend-then-hibernate
Mar 27 10:31:02 bluelazer ModemManager[893]: <info> [sleep-monitor-systemd] system is about to suspend
Mar 27 10:31:02 bluelazer systemd-sleep[168709]: Entering sleep state 'suspend'...
Mar 27 10:31:02 bluelazer kernel: PM: suspend entry (s2idle)
Mar 27 10:33:26 bluelazer kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Mar 27 10:33:26 bluelazer kernel: PM: suspend exit
Mar 27 10:33:26 bluelazer systemd[1]: systemd-suspend-then-hibernate.service: Deactivated successfully.
Mar 27 10:36:59 bluelazer sudo[182501]: joe : TTY=pts/20 ; PWD=/home/joe ; USER=root ; COMMAND=/usr/bin/systemctl suspend-then-hibernate
Mar 27 10:36:59 bluelazer ModemManager[893]: <info> [sleep-monitor-systemd] system is about to suspend
Mar 27 10:37:00 bluelazer systemd-sleep[183111]: Entering sleep state 'suspend'...
Mar 27 10:37:00 bluelazer kernel: PM: suspend entry (s2idle)
Mar 27 10:37:23 bluelazer kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Mar 27 10:37:23 bluelazer kernel: PM: suspend exit
Mar 27 10:37:23 bluelazer systemd[1]: systemd-suspend-then-hibernate.service: Deactivated successfully.
Mar 27 10:37:43 bluelazer sudo[184467]: joe : TTY=pts/20 ; PWD=/home/joe ; USER=root ; COMMAND=/usr/bin/systemctl suspend
Mar 27 10:37:43 bluelazer ModemManager[893]: <info> [sleep-monitor-systemd] system is about to suspend
Mar 27 10:37:44 bluelazer systemd-sleep[185042]: Entering sleep state 'suspend'...
Mar 27 10:37:44 bluelazer kernel: PM: suspend entry (s2idle)
Mar 27 10:37:54 bluelazer kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Mar 27 10:37:54 bluelazer kernel: PM: suspend exit
Mar 27 10:37:54 bluelazer systemd[1]: systemd-suspend.service: Deactivated successfully.
Mar 27 10:43:35 bluelazer ModemManager[893]: <info> [sleep-monitor-systemd] system is about to suspend
Mar 27 10:43:35 bluelazer systemd-sleep[204288]: Entering sleep state 'suspend'...
Mar 27 10:43:35 bluelazer kernel: PM: suspend entry (s2idle)
Mar 27 10:46:49 bluelazer kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Mar 27 10:46:49 bluelazer kernel: PM: suspend exit
Mar 27 10:46:49 bluelazer systemd[1]: systemd-suspend.service: Deactivated successfully.
Mar 27 10:46:53 bluelazer ModemManager[893]: <info> [sleep-monitor-systemd] system is about to suspend
Mar 27 10:46:53 bluelazer systemd-sleep[204823]: Entering sleep state 'suspend'...
Mar 27 10:46:53 bluelazer kernel: PM: suspend entry (s2idle)
Mar 27 10:46:57 bluelazer kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Mar 27 10:46:57 bluelazer kernel: PM: suspend exit
Mar 27 10:46:57 bluelazer systemd[1]: systemd-suspend.service: Deactivated successfully.
Mar 27 18:43:51 bluelazer ModemManager[893]: <info> [sleep-monitor-systemd] system is about to suspend
Mar 27 18:43:51 bluelazer systemd-sleep[1442414]: Entering sleep state 'suspend'...
Mar 27 18:43:51 bluelazer kernel: PM: suspend entry (s2idle)
Mar 27 19:02:58 bluelazer kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Mar 27 19:02:58 bluelazer kernel: PM: suspend exit
Mar 27 19:02:59 bluelazer systemd[1]: systemd-suspend.service: Deactivated successfully.
Mar 27 19:07:16 bluelazer sudo[1451707]: joe : TTY=pts/20 ; PWD=/home/joe ; USER=root ; COMMAND=/usr/bin/systemctl suspend
Mar 27 19:07:16 bluelazer ModemManager[893]: <info> [sleep-monitor-systemd] system is about to suspend
Mar 27 19:07:17 bluelazer systemd-sleep[1454215]: Entering sleep state 'suspend'...
Mar 27 19:07:17 bluelazer kernel: PM: suspend entry (s2idle)
Mar 27 19:07:26 bluelazer kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Mar 27 19:07:26 bluelazer kernel: PM: suspend exit
Mar 27 19:07:27 bluelazer systemd[1]: systemd-suspend.service: Deactivated successfully.
Mar 27 19:14:27 bluelazer ModemManager[897]: <info> [sleep-monitor-systemd] system is about to suspend
Mar 27 19:14:27 bluelazer systemd-sleep[2847]: Entering sleep state 'suspend'...
Mar 27 19:14:27 bluelazer kernel: PM: suspend entry (s2idle)
Mar 27 19:14:40 bluelazer kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Mar 27 19:14:40 bluelazer kernel: PM: suspend exit
Mar 27 19:14:41 bluelazer systemd[1]: systemd-suspend.service: Deactivated successfully.
Mar 27 19:16:07 bluelazer sudo[8084]: joe : TTY=pts/2 ; PWD=/home/joe ; USER=root ; COMMAND=/usr/bin/systemctl unmask suspend.target hibernate.target sleep.target sudo systemctl enable suspend.target hibernate.target sleep.target
Mar 27 19:16:22 bluelazer sudo[9115]: joe : TTY=pts/2 ; PWD=/home/joe ; USER=root ; COMMAND=/usr/bin/systemctl unmask suspend.target hibernate.target sleep.target sudo systemctl enable suspend.target hibernate.target sleep.target
Mar 27 19:16:31 bluelazer sudo[9843]: joe : TTY=pts/2 ; PWD=/home/joe ; USER=root ; COMMAND=/usr/bin/systemctl unmask suspend.target hibernate.target sleep.target
Mar 27 19:16:42 bluelazer sudo[10638]: joe : TTY=pts/2 ; PWD=/home/joe ; USER=root ; COMMAND=/usr/bin/systemctl enable suspend.target hibernate.target sleep.target
Mar 27 19:17:52 bluelazer ModemManager[897]: <info> [sleep-monitor-systemd] system is about to suspend
Mar 27 19:17:52 bluelazer systemd-sleep[14092]: Entering sleep state 'suspend'...
Mar 27 19:17:52 bluelazer kernel: PM: suspend entry (s2idle)
Mar 27 19:18:02 bluelazer kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Mar 27 19:18:02 bluelazer kernel: PM: suspend exit
Mar 27 19:18:03 bluelazer systemd[1]: systemd-suspend.service: Deactivated successfully.
Mar 27 19:20:52 bluelazer ModemManager[875]: <info> [sleep-monitor-systemd] system is about to suspend
Mar 27 19:20:52 bluelazer systemd-sleep[2820]: Entering sleep state 'suspend'...
Mar 27 19:20:52 bluelazer kernel: PM: suspend entry (s2idle)
Mar 27 19:21:06 bluelazer kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Mar 27 19:21:06 bluelazer kernel: PM: suspend exit
Mar 27 19:21:07 bluelazer systemd[1]: systemd-suspend.service: Deactivated successfully.
Mar 27 19:21:57 bluelazer ModemManager[875]: <info> [sleep-monitor-systemd] system is about to suspend
Mar 27 19:21:57 bluelazer systemd-sleep[7584]: Entering sleep state 'suspend'...
Mar 27 19:21:57 bluelazer kernel: PM: suspend entry (s2idle)
Mar 27 19:22:12 bluelazer kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Mar 27 19:22:12 bluelazer kernel: PM: suspend exit
Mar 27 19:22:13 bluelazer systemd[1]: systemd-suspend.service: Deactivated successfully.
Mar 27 19:28:52 bluelazer ModemManager[875]: <info> [sleep-monitor-systemd] system is about to suspend
Mar 27 19:28:53 bluelazer systemd-sleep[34718]: Entering sleep state 'suspend'...
Mar 27 19:28:53 bluelazer kernel: PM: suspend entry (s2idle)
Mar 27 19:29:04 bluelazer kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Mar 27 19:29:04 bluelazer kernel: PM: suspend exit
Mar 27 19:29:05 bluelazer systemd[1]: systemd-suspend.service: Deactivated successfully.
Mar 27 19:30:04 bluelazer ModemManager[875]: <info> [sleep-monitor-systemd] system is about to suspend
Mar 27 19:30:04 bluelazer systemd-sleep[37755]: Entering sleep state 'suspend'...
Mar 27 19:30:04 bluelazer kernel: PM: suspend entry (s2idle)
Mar 27 22:43:11 bluelazer kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Mar 27 22:43:11 bluelazer kernel: PM: suspend exit
Mar 27 22:43:12 bluelazer systemd[1]: systemd-suspend.service: Deactivated successfully.
Mar 27 23:03:14 bluelazer ModemManager[875]: <info> [sleep-monitor-systemd] system is about to suspend
Mar 27 23:03:15 bluelazer systemd-sleep[79790]: Entering sleep state 'suspend'...
Mar 27 23:03:15 bluelazer kernel: PM: suspend entry (s2idle)
Mar 27 23:03:29 bluelazer kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Mar 27 23:03:29 bluelazer kernel: PM: suspend exit
Mar 27 23:03:30 bluelazer systemd[1]: systemd-suspend.service: Deactivated successfully.
Resume:
Mar 26 10:51:25 bluelazer kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1028-oem root=UUID=5ce61f91-9595-48d8-b5a5-98318d23acf2 ro quiet splash nvme.noacpi=1 resume=UUID=cabb2111-cbf5-4827-b5a1-5df78f59e6d9
Mar 26 10:51:25 bluelazer kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1028-oem root=UUID=5ce61f91-9595-48d8-b5a5-98318d23acf2 ro quiet splash nvme.noacpi=1 resume=UUID=cabb2111-cbf5-4827-b5a1-5df78f59e6d9
Mar 26 11:17:54 bluelazer kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1028-oem root=UUID=5ce61f91-9595-48d8-b5a5-98318d23acf2 ro quiet splash nvme.noacpi=1 resume=UUID=cabb2111-cbf5-4827-b5a1-5df78f59e6d9
Mar 26 11:17:54 bluelazer kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1028-oem root=UUID=5ce61f91-9595-48d8-b5a5-98318d23acf2 ro quiet splash nvme.noacpi=1 resume=UUID=cabb2111-cbf5-4827-b5a1-5df78f59e6d9
Mar 27 09:09:45 bluelazer kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1028-oem root=UUID=5ce61f91-9595-48d8-b5a5-98318d23acf2 ro quiet splash nvme.noacpi=1 resume=UUID=cabb2111-cbf5-4827-b5a1-5df78f59e6d9
Mar 27 09:09:45 bluelazer kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1028-oem root=UUID=5ce61f91-9595-48d8-b5a5-98318d23acf2 ro quiet splash nvme.noacpi=1 resume=UUID=cabb2111-cbf5-4827-b5a1-5df78f59e6d9
Mar 27 10:46:57 bluelazer kernel: PM: dpm_run_callback(): usb_dev_resume+0x0/0x20 returns -5
Mar 27 10:46:57 bluelazer kernel: usb 3-3.5: PM: failed to resume async: error -5
Mar 27 19:13:47 bluelazer kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1029-oem root=UUID=5ce61f91-9595-48d8-b5a5-98318d23acf2 ro quiet splash nvme.noacpi=1 resume=UUID=cabb2111-cbf5-4827-b5a1-5df78f59e6d9
Mar 27 19:13:47 bluelazer kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1029-oem root=UUID=5ce61f91-9595-48d8-b5a5-98318d23acf2 ro quiet splash nvme.noacpi=1 resume=UUID=cabb2111-cbf5-4827-b5a1-5df78f59e6d9
Mar 27 19:20:13 bluelazer kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1029-oem root=UUID=5ce61f91-9595-48d8-b5a5-98318d23acf2 ro quiet splash nvme.noacpi=1 resume=UUID=cabb2111-cbf5-4827-b5a1-5df78f59e6d9
Mar 27 19:20:13 bluelazer kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1029-oem root=UUID=5ce61f91-9595-48d8-b5a5-98318d23acf2 ro quiet splash nvme.noacpi=1 resume=UUID=cabb2111-cbf5-4827-b5a1-5df78f59e6d9
Mar 28 08:27:39 bluelazer kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1029-oem root=UUID=5ce61f91-9595-48d8-b5a5-98318d23acf2 ro quiet splash nvme.noacpi=1 resume=UUID=cabb2111-cbf5-4827-b5a1-5df78f59e6d9
Mar 28 08:27:39 bluelazer kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1029-oem root=UUID=5ce61f91-9595-48d8-b5a5-98318d23acf2 ro quiet splash nvme.noacpi=1 resume=UUID=cabb2111-cbf5-4827-b5a1-5df78f59e6d9
Looks like it’s popping out of s2idle, something is indeed waking it up.
Which if any, peripherals are attached. This includes Bluetooth devices, external displays, please list anything you can think of.
Which applications are open/running when this is happening?
I have tried with nothing plugged in and nothing running. Of course there are some services running in the background at boot, but nothing out of the ordinary. Only thing I can think of that I enabled that isn’t installed by default is Redshift?
@Matt_Hartley Is there a way I can see what is waking it up? I disabled Redshift, but that doesn’t change anything
Actually Redshift can cause wakeup events (accesses hardware features) - I’d completely exit out of it (applet included if present). Test this and see if this changes anything.
If this proves successful, odds are solid that this will resolve it - but before doing this below, test by ending the process completely, then suspend.
if memory serves me (I don’t have it installed at the moment):
edit ~/.config/redshift.conf
and add in:
[redshift]
disable-hardware=true
Did a clean boot with Redshift not starting but same thing. Not sure what else I could have changed…
For whatever reason switching from s2idle to deep makes it work fine 
Happy to hear the switch to deep fixed the issue. I’ll mark this as solved, but if it was waking s2idle it may have meant that a process/application/device was waking it up out of a less than deep sleep. Either way, glad deep worked. 