"sudo poweroff" doesn’t work

nitrofurano · 2016-01-10 00:04:55

I tried to enter "sudo poweroff", but it doesn’t work - the window manager (whatever fluxbox, icewm, jwm, windowmaker, lxde, pekwm, etc.) logs out, but the computer doesn’t switch off - i guess that "sudo halt" or "sudo shutdown -h now" wouldn’t work as well - poweroff from lightdm menu also doesn’t work

i don’t know if that is related to a missing installed package related to power management, or something like that

the computer also seems to freeze when we enter "sudo reboot"

pressing sysrq+alt+b also doesn’t do anything, the computer is still turned on, and the it doesn’t get restarted

this is a quite weird situation i never saw happening after 17 years using gnu/linux

please let me know if logs like from lspci or cat /proc/* is needed

thanks

Horizon_Brave · 2016-01-10 00:45:51

Could this be an effect of systemd's handling of the older init runlevels? you may have to go for

 systemctl poweroff

Head_on_a_Stick · 2016-01-10 00:45:59

Does this work:

systemctl poweroff -i

EDIT: Ninja'd

Is there anything in the systemd journal?
https://www.digitalocean.com/community/ … stemd-logs

Last edited by Head_on_a_Stick (2016-01-10 00:46:35)

ohnonot · 2016-01-10 08:42:47

nitrofurano wrote:

i guess that "sudo halt" or "sudo shutdown -h now" wouldn’t work as well

guess? wouldn't? should be replaced with know, doesn't.

in any case, if previously posted suggestion doesn't fix it, we might be looking at an ACPI issue.

nitrofurano · 2016-01-10 10:54:30

yes, both

systemctl poweroff -i

and

systemctl poweroff

doesn’t work

anyway, please let me/us (us with similar issues) know which information should we provide for debugging it

Head_on_a_Stick · 2016-01-10 11:10:49

nitrofurano wrote:

please let me/us (us with similar issues) know which information should we provide for debugging it

Did you not read the link I provided about systemd's journal?

Open a terminal window and run this command:

journalctl -xf

Then attempt to shutdown and post any terminal output that appears.

nitrofurano · 2016-01-10 15:30:33

Head_on_a_Stick wrote:

nitrofurano wrote:
please let me/us (us with similar issues) know which information should we provide for debugging it
Did you not read the link I provided about systemd's journal?

which link, and where? (sorry asking...)

Open a terminal window and run this command:
journalctl -xf
Then attempt to shutdown and post any terminal output that appears.

guest@bunsenlabs-p4:~$ journalctl -xf
No journal files were found

thanks!

Head_on_a_Stick · 2016-01-10 15:58:17

nitrofurano wrote:

which link, and where? (sorry asking...)

I wrote:

https://www.digitalocean.com/community/ … stemd-logs

https://forums.bunsenlabs.org/viewtopic … 796#p14796

Sorry, I forgot that you will have to add your user to the "systemd-journal" group to view the journal:

sudo gpasswd -a USERNAME systemd-journal

Replace "USERNAME" with your actual username, do not use quotation marks.

Then log out & back in again and run `journalctl -xf` then attempt to shutdown and post the full output please.

You seem to have a lot of issues with your install that nobody else is suffering with.

I think we need to hear about the details of your installation process.

Perhaps you did something incorrectly.

nitrofurano · 2016-01-11 10:13:51

thanks, i'll do this asap

about the installation process, i did it as automatically as usual (as i did on all other distros, like Crunchbang, Ubuntu, Mint or whatever) - i just used the "graphic install" from the live-cd - is the installation process log stored somewhere, that i could share it?

Last edited by nitrofurano (2016-01-11 10:18:06)

nitrofurano · 2016-01-11 10:33:29

guest@bunsenlabs-p4:~$ journalctl -xf
-- Logs begin at Mon 2016-01-11 10:09:39 WET. --
Jan 11 10:28:40 bunsenlabs-p4 systemd[684]: Starting Sockets.
-- Subject: Unit UNIT has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit UNIT has begun starting up.
Jan 11 10:28:40 bunsenlabs-p4 systemd[684]: Reached target Sockets.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Jan 11 10:28:40 bunsenlabs-p4 systemd[684]: Starting Basic System.
-- Subject: Unit UNIT has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit UNIT has begun starting up.
Jan 11 10:28:40 bunsenlabs-p4 systemd[684]: Reached target Basic System.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Jan 11 10:28:40 bunsenlabs-p4 systemd[684]: Starting Default.
-- Subject: Unit UNIT has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit UNIT has begun starting up.
Jan 11 10:28:40 bunsenlabs-p4 systemd[684]: Reached target Default.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Jan 11 10:28:40 bunsenlabs-p4 systemd[684]: Startup finished in 43ms.
-- Subject: System start-up is now complete
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- All system services necessary queued for starting at boot have been
-- successfully started. Note that this does not mean that the machine is
-- now idle as services might still be busy with completing start-up.
-- 
-- Kernel start-up required KERNEL_USEC microseconds.
-- 
-- Initial RAM disk start-up required INITRD_USEC microseconds.
-- 
-- Userspace start-up required 43087 microseconds.
Jan 11 10:28:48 bunsenlabs-p4 org.a11y.Bus[721]: Activating service name='org.a11y.atspi.Registry'
Jan 11 10:28:48 bunsenlabs-p4 org.a11y.Bus[721]: Successfully activated service 'org.a11y.atspi.Registry'
Jan 11 10:28:48 bunsenlabs-p4 org.a11y.atspi.Registry[765]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry

Head_on_a_Stick · 2016-01-11 10:52:59

^ OK, that output looks like it just shows the startup and the localisation (the "a11y" bit).

Was any extra output added in the terminal after you attempted to reboot from the graphical desktop?

Just to be clear:

I want you to open a terminal window.

Then I want you to run this command in the terminal:

journalctl -xf

Then I want you to leave the terminal window open and attempt to reboot your system from the menu.

This should make extra lines appear in the terminal window you have left open -- that is the output that will contain some clues about what is happening here.

I think @ohnonot may be right and this sounds like an ACPI issue.

Head_on_a_Stick · 2016-01-11 11:21:04

Just found this:
http://freedesktop.org/wiki/Software/sy … wnproblems

Does your system shut down & reboot cleanly if you run these commands as root:

sync && reboot -f

sync && poweroff -f

spacex · 2016-01-31 01:28:22

Problem could go away by disabling "xhci", problem could also go away with a different kernel.

tknomanzr · 2016-01-31 02:20:25

I have seen a sporadic issue or two with the version of systemd in regards to power management that was current in Jessie prior to the newest release. A recent upgrade seemed to resolve those issues on my laptop.

#1 2016-01-10 00:04:55

"sudo poweroff" doesn’t work

#2 2016-01-10 00:45:51

Re: "sudo poweroff" doesn’t work

#3 2016-01-10 00:45:59

Re: "sudo poweroff" doesn’t work

#4 2016-01-10 08:42:47

Re: "sudo poweroff" doesn’t work

#5 2016-01-10 10:54:30

Re: "sudo poweroff" doesn’t work

#6 2016-01-10 11:10:49

Re: "sudo poweroff" doesn’t work

#7 2016-01-10 15:30:33

Re: "sudo poweroff" doesn’t work

#8 2016-01-10 15:58:17

Re: "sudo poweroff" doesn’t work

#9 2016-01-11 10:13:51

Re: "sudo poweroff" doesn’t work

#10 2016-01-11 10:33:29

Re: "sudo poweroff" doesn’t work

#11 2016-01-11 10:52:59

Re: "sudo poweroff" doesn’t work

#12 2016-01-11 11:21:04

Re: "sudo poweroff" doesn’t work

#13 2016-01-31 01:28:22

Re: "sudo poweroff" doesn’t work

#14 2016-01-31 02:20:25

Re: "sudo poweroff" doesn’t work

Board footer