You are not logged in.
Hi,
just wondering that obviously almost nobody seems to be expecting this systemd-bug: https://bugs.archlinux.org/task/37007, https://bugzilla.novell.com/show_bug.cgi?id=841544
But the actual question I have: Could this be in any way related to the new systemd hook, triggered by applying respectively not applying it?
Offline
cju,
Mine is having the same problem. btw, did you find a message in 'journalctl -b' like this?
Sep 22 10:30:56 archbox systemd[1370]: Failed to open private bus connection: Failed to connect to socket /run/user/1000/dbus/user_bus_socket: No such file or directory
Last edited by enihcam (2013-09-22 03:13:52)
Offline
Hi,
just wondering that obviously almost nobody seems to be expecting this systemd-bug: https://bugs.archlinux.org/task/37007, https://bugzilla.novell.com/show_bug.cgi?id=841544
But the actual question I have: Could this be in any way related to the new systemd hook, triggered by applying respectively not applying it?
I've been using the new systemd hook and I don't have this problem at all (no hangs with systemd 207 with or without the new systemd hook). I don't think its related to that.
Offline
cju,
Mine is having the same problem. btw, did you find a message in 'journalctl -b' like this?Sep 22 10:30:56 archbox systemd[1370]: Failed to open private bus connection: Failed to connect to socket /run/user/1000/dbus/user_bus_socket: No such file or directory
Yes, I do.
Last edited by cju (2013-09-22 08:44:17)
Offline
cju wrote:Hi,
just wondering that obviously almost nobody seems to be expecting this systemd-bug: https://bugs.archlinux.org/task/37007, https://bugzilla.novell.com/show_bug.cgi?id=841544
But the actual question I have: Could this be in any way related to the new systemd hook, triggered by applying respectively not applying it?
I've been using the new systemd hook and I don't have this problem at all (no hangs with systemd 207 with or without the new systemd hook). I don't think its related to that.
Thanks for the info; I'm not sure whether this bug is related to this, but since there's also this thread: Are you using Arch in a VBox or as a real system?
Offline
bwat47 wrote:cju wrote:Hi,
just wondering that obviously almost nobody seems to be expecting this systemd-bug: https://bugs.archlinux.org/task/37007, https://bugzilla.novell.com/show_bug.cgi?id=841544
But the actual question I have: Could this be in any way related to the new systemd hook, triggered by applying respectively not applying it?
I've been using the new systemd hook and I don't have this problem at all (no hangs with systemd 207 with or without the new systemd hook). I don't think its related to that.
Thanks for the info; I'm not sure whether this bug is related to this, but since there's also this thread: Are you using Arch in a VBox or as a real system?
No virtualbox here.
Looking at this link from the bug report: http://lists.freedesktop.org/archives/s … 13334.html
It looks like the bug is only triggered by a type=notify service. I guess none of the services I have activated are type=notify.
Last edited by bwat47 (2013-09-22 12:45:36)
Offline
Yeah i got this too today, a "sudo reboot" just froze/waited for 1-2 minutes and then it suddenly kick into gear and started stopping services and reboot as it should.
I watched htop and saw "systemd-tty-ask-password-agent" being executed by my reboot, which is probably another new systemd-thingie'majingies.
. Main: Intel Core i5 6600k @ 4.4 Ghz, 16 GB DDR4 XMP, Gefore GTX 970 (Gainward Phantom) - Arch Linux 64-Bit
. Server: Intel Core i5 2500k @ 3.9 Ghz, 8 GB DDR2-XMP RAM @ 1600 Mhz, Geforce GTX 570 (Gainward Phantom) - Arch Linux 64-Bit
. Body: Estrogen @ 90%, Testestorone @ 10% (Not scientific just out-of-my-guesstimate-brain)
Offline
i am affected by this issue as well. downgrade did the trick for me too. jose
Offline
I have the same issue. Not sure the cause, but downgrading works for me.
Offline