You are not logged in.
Pages: 1
Topic closed
Hey all,
I have a problem with my arch install that just started recently.
I will usually shutdown my laptop with "shutdown -h 0".
However, recently it will sometimes not shutdown and give me this output:
Failed to talk to shutdownd, proceeding with immediate shutdown: Connection refused
Failed to open /dev/initctl: No such device or address
Failed to talk to init daemon.
Also, I have noticed that sometimes when I close the lid of the laptop it will not suspend and when I try to switch to switch to a new login shell with "alt + F2" I get a cursor, but no prompt for my username.
I'm stumped. Any ideas?
Offline
Is your Arch system up to date? If not, upgrade it first.
The correct command for shutdown via systemd is
# systemctl poweroff
which must be run as root (or prefix it with sudo).
About the suspending with the lid closed, using your favorite editor as root, edit /etc/systemd/logind.conf, search for the line HandleLidSwitch, uncomment it and set it to HandleLidSwitch=suspend, save the file, restart the system with
# systemctl reboot
as root or prefix it with sudo and see if the problem persists.
You can use CTRL+ALT+[F1-F8] to change consoles. Maybe your display manager (the graphical interface that allows you to log in) is conflicting with the virtual terminals.
Last edited by bjornoslav (2013-09-21 09:06:24)
asus ux303la, core i5@1.6ghz, 8 gb ram, 500gb hdd, hd4400 gpu, crux x64 with openbox
Offline
Please read the wiki: https://wiki.archlinux.org/index.php/Al … o_Shutdown
Install polkit and you can reboot / shutdown w/o sudo i.e.
$ systemctl poweroff
Offline
Thank you for the replies.
My system is up to date and I do have polkit installed.
I tried using these same commands early in a session and they all worked. The lid closing still suspended even though I have not removed the comment out from /etc/systemd/logind.conf.
I also went on a hunch that it might be caused by Steam since this problem started around the time that I installed Steam.
I started up Steam and then killed it. Now the laptop is back where it was and will not shutdown, reboot or suspend (but the consoles problem is gone).
Running systemctl poweroff with sudo after steam has been run and killed yields this response:
Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Connection refused
At this point, I'd put about an 80% probability that it is Steam related, but I'm going to try and reverse a couple other recent changes I've made to see what the effect is.
On a side note, is their any particular merit to managing power with systemctl instead of using reboot and shutdown -h?
Offline
$ ls -l /usr/bin/shutdown /usr/bin/reboot
lrwxrwxrwx 1 root root 9 Sep 20 00:15 /usr/bin/reboot -> systemctl
lrwxrwxrwx 1 root root 9 Sep 20 00:15 /usr/bin/shutdown -> systemctl
You're using systemctl either way.
Last edited by karol (2013-09-21 16:45:54)
Offline
Which model of laptop do you have?
asus ux303la, core i5@1.6ghz, 8 gb ram, 500gb hdd, hd4400 gpu, crux x64 with openbox
Offline
Reversing other settings has yielded nothing. I am convinced that Steam is the problem. Somehow it seems that Steam is wrecking D-bus.
My computer is a thinkpad Z60t, but I don't think that will help much.
This is part of the terminal output when I launch Steam in the terminal:
[0921/135328:ERROR:object_proxy.cc(239)] Failed to call method: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files
[0921/135328:WARNING:proxy_service.cc(958)] PAC support disabled because there is no system implementation
I'm not sure what to make of it though. Should I post the entirety of the terminal output?
Offline
Ok,
Now I've had a session where I did not start Steam, but I still was locked out of shutingdown, rebooting, or suspending.
I am really at a loss. Does anyone have any guess about what might be wrong?
Offline
I have seen exactly the same behaviour here on two of my systems, one being a netbook and the other a generic desktop setup. My laptop started misbehaving two days ago right when systemd was updated to 205-2 (I believe that was the number!) and the desktop has been giving me the "cannot shutdown" issue too. My laptop, when I try to reboot or shutdown through Xfce, tells me that it cannot connect to init and that there is no sysctl. I'll try to record the errors and post them if anyone wishes to see them.
Oh and I am not running Steam at all so I think you can put that idea to bed.
Offline
Same problem here: Thinkpad T400, up-to-date system (systemd 207-5, systemd-sysvcompat 207-5, sysvinit-tools 2.88-11, dbus 1.6.14-1, linux 3.11.1-1; since one of the other boxes is a thinkpad, too, here are my thinkpad-specific programs: community/tp_smapi 0.41-35, AUR/tpfanco-svn 89-6, AUR/thinkhdaps 0.2.1-3, AUR/hdaps-gl 0.0.5-3).
I have just noticed that I have a host of zombie processes in my process table, probably also a problem of the init process, no? (The list is continously growing, due to cronjobs apparently leaving zombies behind.)
Also, steam is not installed here at all.
Edit: I've just seen another thread that is probably related, and it's about a kernel bug triggered by suspending - which I did, too: https://bbs.archlinux.org/viewtopic.php?id=170008. (Kernel bugreport: https://bugzilla.kernel.org/show_bug.cgi?id=61781.)
Last edited by awagner (2013-09-24 08:25:21)
Offline
Well I guess it's a bit comforting knowing that it is just the kernel and not something I did.
It seems that rolling back to kernel 3.10 has been recommended as a solution. Would that be the best bet for now or would it be better just to stick with 3.11 and not suspend until the bug is fixed?
Offline
https://bbs.archlinux.org/viewtopic.php?pid=1328836
seems this segfault of systemd is caused by kernel 3.11, which is a kernel issue resulting from suspend/resume, downgrading to 3.10 kernel fixes it so far. So skip 3.11 to resolve this issue. Or live without suspend lol.
Offline
Note that the kernel bug status is currently NEEDS INFO. Somebody needs to give them the info for this to get fixed...
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
I can get information on the bug, but I'm very new to bug reporting and don't know what specifics I should be getting.
All I've been able to narrow down so far is that this bug effects only 32 bit intel installs. After going into a working suspend and waking up, the system's dbus will be a bit off (I'm not sure how to describe it). Using ps -e after a suspend reveals a lot of redundantly spawned instances of kworker.
1888 ? 00:00:00 systemd-sleep <defunct>
1890 ? 00:00:00 kworker/0:3
1891 ? 00:00:00 kworker/0:4
1892 ? 00:00:00 kworker/u2:1
Once it reaches kworker/u2:1 it goes on to u2:2 then 3 and so on. In the session that I am observing right now it goes up to 82.
All this being said, this is all observations and I doubt it helps at all in debugging. Can anyone tell me anything I can do to help?
Last edited by MongooseOfPower (2013-09-25 16:49:24)
Offline
# Reboot
sudo systemctl --force --force reboot
# Shutdown
sudo systemctl --force --force poweroff
Offline
Please don't necrobump. Especially to post potentially harmful advice.
https://wiki.archlinux.org/index.php/Co … bumping.22
Closing.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Online
Pages: 1
Topic closed