Suspend command keyboard shortcut [Solved]
Re: Suspend command keyboard shortcut
Just tried using a Linux Mint live USB I had lying around. Choosing 'Suspend' from the shutdown menu works as it should and when waking the system the (wireless) mouse and keyboard work as expected. I tried it about half a dozen times with no issues. I don't know how Mint suspends the system, I should have tried 'sudo pm-suspend' but didn't, will try later.
Re: Suspend command keyboard shortcut [Solved]
Of course, you can try everything there, meanwhile wireless mouse is probably keeping it awake (retaining from suspend). On MX (the installed one) I would boot once with systemd and try systemctl suspend .
The difference (with Mint) may be due to kernels: you may also try Liquorix kernels from MXPI.
Re: Suspend command keyboard shortcut
Thanks again. I've only just started using the wireless mouse today so that's not the problem. I'll try booting with systemd as you suggest, see what that does.Charlie Brown wrote: Tue Sep 19, 2023 1:28 pm Of course, you can try everything there, meanwhile wireless mouse is probably keeping it awake (retaining from suspend). On MX (the installed one) I would boot once with systemd and try systemctl suspend .
Re: Suspend command keyboard shortcut
Booted with systemd and tried suspend maybe 15 times, using either 'systemctl suspend' in a terminal or the power button. Both work properly ie the computer suspends and the mouse and keyboard work when it wakes. I also noticed that boot time is significantly quicker.
Is there a downside to using systemd from an 'end user' perspective? I've read a tiny bit about the systemd controversy and I don't have an ideological standpoint, I just want my computer to work properly which it has for the last three years using MX Linux. I might update to MX23 and try it with the default boot system, if that doesn't work switch it to systemd.
Is there a downside to using systemd from an 'end user' perspective? I've read a tiny bit about the systemd controversy and I don't have an ideological standpoint, I just want my computer to work properly which it has for the last three years using MX Linux. I might update to MX23 and try it with the default boot system, if that doesn't work switch it to systemd.
Re: Suspend command keyboard shortcut
You can even make it default (as you might already know) : MX Boot Options => "Boot to" ..select any kernel you like with systemd option.
Just, there's no systemd on live session, so the only con may be using your snapshots ..
Just, there's no systemd on live session, so the only con may be using your snapshots ..
Re: Suspend command keyboard shortcut
Thanks again, I think I can mark this solved now (fingers crossed!).Charlie Brown wrote: Wed Sep 20, 2023 4:57 am You can even make it default (as you might already know) : MX Boot Options => "Boot to" ..select any kernel you like with systemd option.
Just, there's no systemd on live session, so the only con may be using your snapshots ..
Re: Suspend command keyboard shortcut
@Charlie Brown Just for info, I installed MX 23 and the same issue pertains unless I use systemd.
Re: Suspend command keyboard shortcut
Thank you for the feedback.
Can you just try 2 suspends with systemd ?
One with either the menu/button or with:
and the other with sudo pm-suspend.
(These may be useful for devs).
Say, these also work perfectly on systemd, then it's completely due to init.
(Meanwhile, did you try on live session? Just out of curiosity)
Can you just try 2 suspends with systemd ?
One with either the menu/button or with:
Code: Select all
xfce4-session-logout --suspend
(These may be useful for devs).
Say, these also work perfectly on systemd, then it's completely due to init.
(Meanwhile, did you try on live session? Just out of curiosity)
Re: Suspend command keyboard shortcut
I can confirm both of those work properly. I have systemd set as default for boot now and back to using my hotkey :D. I didn't try suspend on the MX23 live USB I'm afraid.
Re: Suspend command keyboard shortcut
Ok, thank you for trying and the feedback :)