when I try to suspend I get this advice that inhibit suspend, I have to insert root password and then I can suspend, how to get rid of this?
Check what application inhibits suspend.
systemd-inhibits --list
Watch for mode block.
Small typo that I also often make the command is
systemd-inhibit --list
manythanks 
here is
pla@pla4-TW:~> systemd-inhibit --list
WHO UID USER PID COMM WHAT WHY >
ModemManager 0 root 1136 ModemManager sleep ModemManager needs to reset devices >
NetworkManager 0 root 944 NetworkManager sleep NetworkManager needs to turn off networks>
UPower 0 root 1607 upowerd sleep Execute critical action >
PowerDevil 1000 pla 5428 org_kde_powerde handle-power-key:handle-suspend-key:handle-hibernate-key:handle-lid-switch KDE handles power events >
Screen Locker 1000 pla 4739 ksmserver sleep Ensuring that the screen gets locked befo>
electron 1000 pla 20515 electron sleep Application cleanup before suspend >
6 inhibitors listed.
lines 1-9/9 (END)
No, it is not. You cut off the most important information. Use
systemd-inhibit --list | cat
here is
pla@pla4-TW:~> systemd-inhibit --list | cat
WHO UID USER PID COMM WHAT WHY MODE
ModemManager 0 root 1136 ModemManager sleep ModemManager needs to reset devices delay
NetworkManager 0 root 944 NetworkManager sleep NetworkManager needs to turn off networks delay
UPower 0 root 1607 upowerd sleep Execute critical action block
PowerDevil 1000 pla 5428 org_kde_powerde handle-power-key:handle-suspend-key:handle-hibernate-key:handle-lid-switch KDE handles power events block
Screen Locker 1000 pla 4739 ksmserver sleep Ensuring that the screen gets locked before going to sleep delay
electron 1000 pla 20515 electron sleep Application cleanup before suspend delay
6 inhibitors listed.
pla@pla4-TW:~>
As you see, upowerd blocks sleep. Here upowerd is using “delay” inhibit which does not block it.
AFAIU upowerd inhibits suspend when it detects critical battery level.
manythanks, some day ago I had critical battery level alert, I’m in resume mode so I didn’t rebooted from then on,
it means that upowerd doesn’t reset after the first critical battery level alert?
is it correct or is it a bug?
I suppose if I reboot it will not block suspend anymore,
how can I solve without rebooting?
There is not enough information to guess. Full output of
journalctl -b --no-pager --full
may provide some hints. Upload to https://susepaste.org/
Restarting upowerd should reset it.
systemctl restart upower.service
manythanks, here is the link to journalctl -b --no-pager --full, it was too big for susepaste
using
systemctl restart upower.service
it works, suspend doesn’t require no more password
Unfortunately, log does not give any more information. There was resume from suspend at 20:19:27 and net request at 21:36:13 requested authentication. There are a couple of log entries from upowerd about change event but no information about what changed.