Shutdown command does not wait for the time specified

GodsOtherHand · 2015-09-08 20:52:51

Hello.
I have been using the following command for a while in order to shutdown my PC after an amount of time:

sudo shutdown -h 120.

However, for a few days now, this command just shuts down the PC without waiting the 120mins as it did before.

From the man page, I see that is should work

shutdown [OPTIONS...] [TIME] [WALL...]

However, it does not work as expected, as it does not wait for the 120 minutes as it should..

Also, I tried "sudo shutdown -h +120" but it still shuts down right after I enter the password.

Before this i just did an update, but I found no info about a change being made to this...

Last edited by GodsOtherHand (2015-09-08 20:53:07)

bmate22 · 2015-09-08 21:45:04

Have u found any solution? I have the same probleme. I took a photo (I had to be really fast wiht printscreen) and i red the terminal output.

Failed to set wall massage, ignoring? Massage did not recieve a reply (timeout by message bus)
Failed to call SheduleShutdown in logind, proceeding with immediate shutdown: Message did not recieve a reply (timeout by message bus)

I tried to edit the etc/systemd/logind.conf but it didn't help.

Last edited by bmate22 (2015-09-08 21:46:46)

karol · 2015-09-08 21:49:14

https://bbs.archlinux.org/viewtopic.php?pid=1559368 -> https://github.com/systemd/systemd/issues/1120

qwerty12 · 2015-09-08 21:50:21

https://github.com/systemd/systemd/issues/1120

EDIT: There's no delete button so I'll just say that karol was faster.

Last edited by qwerty12 (2015-09-08 21:51:03)

firekage · 2015-09-09 08:29:01

Could somebody explain to me how to apply mentioned above patch in link? I was never good at this and mentioned problem occurs with my Arch also. On the older time declaration in shutdown command works, on upgraded Arch it does not - just reboots system right on the spoot.

Edit: i'm not an lazy. I tried to search for git manuals, faq. I readed it, and i just don't understand it at all. If somebody could explain it with simpler language - big thanks.

Last edited by firekage (2015-09-09 09:09:14)

V1del · 2015-09-09 09:15:23

Just wait for systemd 226 to come out of testing which should include this fix

firekage · 2015-09-09 09:39:02

Yes, but i would like to learn something, that's why i asked. On link above one person said that applying fix solved problem - so, i would like to know how to do it.

ukhippo · 2015-09-09 10:17:09

See https://wiki.archlinux.org/index.php/Patching_in_ABS (and https://wiki.archlinux.org/index.php/ABS )

firekage · 2015-09-09 10:30:46

I read it a lot earlier, much earlier than this problem occured - it is also too complicated to me. Thanks anyway.

martinoff · 2015-09-12 19:45:51

firekage wrote:

I read it a lot earlier, much earlier than this problem occured - it is also too complicated to me. Thanks anyway.

you can try to install it from testing repo

pacman -U http://archlinux.polymorf.fr/testing/os/x86_64/systemd-sysvcompat-226-1-x86_64.pkg.tar.xz http://archlinux.polymorf.fr/testing/os/x86_64/systemd-226-1-x86_64.pkg.tar.xz

Last edited by martinoff (2015-09-12 19:46:35)

karol · 2015-09-12 21:09:31

Partial upgrades are not supported.

joelhy · 2015-09-15 01:24:12

If you just cannot wait the systemd 226 update, you can downgrade to systemd 224, by using command: # downgrade systemd, and choose systemd 224.
By the way, downgrade command is from aur/downgrade. Please make sure it is installed first.

Last edited by joelhy (2015-09-15 01:24:36)

pezmarino · 2015-09-15 13:49:25

The solution it's gaven in https://github.com/systemd/systemd/issues/1120

diff --git a/src/login/logind-dbus.c b/src/login/logind-dbus.c
index 7cc68d4..beae75e 100644
--- a/src/login/logind-dbus.c
+++ b/src/login/logind-dbus.c
@@ -1796,9 +1796,11 @@ static int update_schedule_file(Manager *m) {
if (r < 0)
return log_error_errno(r, "Failed to create shutdown subdirectory: %m");
- t = cescape(m->wall_message);
- if (!t)
- return log_oom();
+ if (!isempty(m->wall_message)) {
+ t = cescape(m->wall_message);
+ if (!t)
+ return log_oom();
+ }
r = fopen_temporary("/run/systemd/shutdown/scheduled", &f, &temp_path);
if (r < 0)

But I don't know how to do it.Could anyone help me? Thanks.

mrunion · 2015-09-15 16:37:04

@pexmarino: Either wait for 226, downgrade to 224 or use ABS, download the package, apply the patch and rebuild and reinstall the package. (See https://wiki.archlinux.org/index.php/Arch_Build_System)

Personally, I would wait for 226, but if it is that sever a problem for you, just downgrading to 224 would be easiest.

pezmarino · 2015-09-17 10:33:56

Thanks

Arch Linux

#1 2015-09-08 20:52:51

Shutdown command does not wait for the time specified

#2 2015-09-08 21:45:04

Re: Shutdown command does not wait for the time specified

#3 2015-09-08 21:49:14

Re: Shutdown command does not wait for the time specified

#4 2015-09-08 21:50:21

Re: Shutdown command does not wait for the time specified

#5 2015-09-09 08:29:01

Re: Shutdown command does not wait for the time specified

#6 2015-09-09 09:15:23

Re: Shutdown command does not wait for the time specified

#7 2015-09-09 09:39:02

Re: Shutdown command does not wait for the time specified

#8 2015-09-09 10:17:09

Re: Shutdown command does not wait for the time specified

#9 2015-09-09 10:30:46

Re: Shutdown command does not wait for the time specified

#10 2015-09-12 19:45:51

Re: Shutdown command does not wait for the time specified

#11 2015-09-12 21:09:31

Re: Shutdown command does not wait for the time specified

#12 2015-09-15 01:24:12

Re: Shutdown command does not wait for the time specified

#13 2015-09-15 13:49:25

Re: Shutdown command does not wait for the time specified

#14 2015-09-15 16:37:04

Re: Shutdown command does not wait for the time specified

#15 2015-09-17 10:33:56

Re: Shutdown command does not wait for the time specified

Board footer