As it turns out, just entering "powe" when searching for Power Management opens the system setting window as expected,

But when you enter "power"...

This causes the PC to sleep immediately.
Tell me why would I use "power" to go to sleep, when "sleep" exists? I'm thinking it's because the current setting when pushing the power button physically is to sleep.
(Unrelated, but there's still a fairly long-standing issue where sometimes my laptop almost fully goes to sleep, but for some reason, the system never sleeps even with no drive activity.
Likewise, sometimes the system fails to restore itself from sleep, and you're left with an unresponsive black screen, needing a forced poweroff and restart.
I still haven't figured out the cause for why this happens. The best I can discern has something to do with the inactivity timer. I couldn't yet trigger it by pushing the power to sleep manually.)
Edit: I got the below issue to occur by pushing the power button to sleep the laptop. It never fully went to sleep.
Can't find anything related to sleep in /var/log at the time it happened. Something must not be firing when it's supposed to...

But when you enter "power"...

This causes the PC to sleep immediately.
Tell me why would I use "power" to go to sleep, when "sleep" exists? I'm thinking it's because the current setting when pushing the power button physically is to sleep.
(Unrelated, but there's still a fairly long-standing issue where sometimes my laptop almost fully goes to sleep, but for some reason, the system never sleeps even with no drive activity.
Likewise, sometimes the system fails to restore itself from sleep, and you're left with an unresponsive black screen, needing a forced poweroff and restart.
I still haven't figured out the cause for why this happens. The best I can discern has something to do with the inactivity timer. I couldn't yet trigger it by pushing the power to sleep manually.)
Edit: I got the below issue to occur by pushing the power button to sleep the laptop. It never fully went to sleep.
Can't find anything related to sleep in /var/log at the time it happened. Something must not be firing when it's supposed to...