Hello,
in May i upgraded to Ubuntu Mate 18.04 coming from Ubuntu Mate 17.04, so in the same day i perform two system upgrade (17.04->17.10 and 17.10->18.04).
Since the upgrade to 18.04 my server automatically suspend exactly 20 minutes after a reboot, no matter if i’m using it or not (e.g. it suspend even if i’m controlling it with xrdp):
Aug 23 15:22:34 Server_Kimsufi systemd[1]: Mounted Huge Pages File System.
Aug 23 15:22:34 Server_Kimsufi systemd[1]: Mounted Kernel Debug File System.
Aug 23 15:22:34 Server_Kimsufi systemd[1]: Started Uncomplicated firewall.
Aug 23 15:22:34 Server_Kimsufi kernel: [ 0.000000] Linux version 4.15.0-32-generic (buildd@lgw01-amd64-039) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #35-Ubuntu SMP Fri Aug 10 17:58:07 UTC 2018 (Ubuntu 4.15.0-32.35-generic 4.15.18)
Aug 23 15:22:34 Server_Kimsufi kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=0e1a682a-ce60-44e1-9686-0bb567077d7f ro net.ifnames=0
.
.
.
.
.
.
Aug 23 15:42:45 Server_Kimsufi NetworkManager[927]: <info> [1535031765.8742] manager: sleep: sleep requested (sleeping: no enabled: yes)
Aug 23 15:42:45 Server_Kimsufi NetworkManager[927]: <info> [1535031765.8941] manager: sleep: wake requested (sleeping: yes enabled: yes)
This force me to do a restart on the server web control panel to be able to use the server again, from scratch, for another 20 minutes.
To be able to use the server for more than 20 minutes i was forced to mask the suspend service, to disable suspend in the hard way:
sudo systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target
Unfortunately this create problem with systemd-logind.service causing it to crash and restart when suspend occurred:
Aug 23 15:42:45 Server_Kimsufi NetworkManager[927]: <info> [1535031765.8742] manager: sleep: sleep requested (sleeping: no enabled: yes)
Aug 23 15:42:45 Server_Kimsufi NetworkManager[927]: <info> [1535031765.8941] manager: sleep: wake requested (sleeping: yes enabled: yes)
Aug 23 15:42:45 Server_Kimsufi systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE
Aug 23 15:42:45 Server_Kimsufi systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
Aug 23 15:42:45 Server_Kimsufi systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart.
Aug 23 15:42:45 Server_Kimsufi upowerd[2046]: Could not acquire inhibitor lock: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
Aug 23 15:42:45 Server_Kimsufi systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 1.
Aug 23 15:42:46 Server_Kimsufi systemd[1]: Stopped Login Service.
Aug 23 15:42:46 Server_Kimsufi ModemManager[922]: <warn> [sleep-monitor] inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
Aug 23 15:42:46 Server_Kimsufi systemd[1]: Starting Login Service...
Aug 23 15:42:46 Server_Kimsufi systemd[1]: Started Login Service.
Looking on internet i found something related to this problem:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893574
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893964#22
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/22
https://bugzilla.redhat.com/show_bug.cgi?id=1558485
I tried to disable the power saving setting in the Ubuntu Mate Power GUI, and also to follow the suggestion of the above posts, disabling with dconf all the power setting and timeout under:
org/gnome/settings-daemon/plugins/power
Unfortunately this doesn’t help, and my system still suspend 20 minutes after a restart.
The strange thing is: with the systemctl mask on sleep service (as shown above), after a restart the system try to suspend after 20 minute. It fails to suspend since the service is disable but after that it doesn’t try to go to sleep in the next 20 minutes. So the system want to sleep only one time (20 minutes after the restart) and not periodically (every 20 minutes).
Does someone know if i’m missing some new power setting or if it is a bug?