So you you suppressed the problem instead of fixing it...
FYI, if I have controll over the system at the first place, I will fix and post the solutions. The systemd automates the things. I don't mind as long as suitable fixing/knowledge tools/documents are provided.
Systemd is challanging the Arch Way, which is good. But we have to remember that there are two sides in the coin..... system/improvements by devs and utilisation by users.
]]>The problem was in the systemd. When trying to fix I lost the sound and a smooth X display. I reinstalled the installation and all ok.
So you you suppressed the problem instead of fixing it...
]]>Hi,
may not be related but I had similar failed systemd-logind.service , some dbus errros etc after
the last (eg filesystem 2012.10-2 -> 2012.11-1) update.I have ssd installation with /var symlinked to directory on other hdd partition.
I noticed the /var/lock and /var/run links wrong.
So I unlinked and re-created links to point to /run and /run/lock, all is fine now.
Maybe the problem is because of my unusual setup and not related to your at all,
anyway I think it is worth checking /var.
With systemd this is a very problematic setup, as systemd mounts partitions asynchronnously. So, there may be a time when /var points to an unmounted partition... Why is there a need for having /var as a symbolic link at all? Why can't you simply mount that hdd on /var?
]]>Unfortunately, I had no time to properly investigate the issue. I rebooted to rescue.target, disabled and re-enabled gdm.service and booted to multi-user.target. This time gdm started normally.
I didn't yet have time to come back to that system yet, so I don't really have a clue about the root of the problem.
Edit: It appears I was overly optimistic. The system consistently fails to boot to working state, while booting it to rescue.target, starting multi-user.target from command line, logging in and restarting gdm.service consistently helps.
]]>may not be related but I had similar failed systemd-logind.service , some dbus errros etc after
the last (eg filesystem 2012.10-2 -> 2012.11-1) update.
I have ssd installation with /var symlinked to directory on other hdd partition.
I noticed the /var/lock and /var/run links wrong.
So I unlinked and re-created links to point to /run and /run/lock, all is fine now.
Maybe the problem is because of my unusual setup and not related to your at all,
anyway I think it is worth checking /var.
The problem was in the systemd. When trying to fix I lost the sound and a smooth X display. I reinstalled the installation and all ok.
That's good to hear. I'm glad you found the source of the problem. It just goes to show that there can be different causes of similar symptoms.
]]>Mr Green
]]>I got the same problem after the latest upgrade..... the systemd hangs up after loading the services. I didn't check what was upgraded.
@rasat: Are you booting via uefi, or bios?
I boot arch via uefi and, after updating my kernel to 3.6.7, like the OP was getting a multitude of systemd "Dependency failed" errors.
It turned out I had failed to copy over my updated kernel to my special fat32 EFI boot partition. It's not very elegant, but my uefi setup requires me to manually copy any updated kernel and initramfs img file from /boot to my EFI boot partition. I suspect other uefi people do something cleaner, but this works for me.
I didn't catch my mindblogglingly idiotic error until I read this helpful post:
]]>I am seriously considering going over to Fedora .. at least their systemd/dbus works ...
Bye.
Don't let the door hit you ...
I know it's foolish to be dragged down to this level, but the sort of posts you've been putting in this thread really p(*&# me off. If you had any real intent to leave you'd be gone, you wouldn't be here posting. You post that drivel because you think that someone here will give a damn. Worse yet you think someone here *should* give a damn - like you chosing to no longer use arch linux would do some great harm to the community and everyone here should bend over backwards to convince you to stay.
Hell, if this is your normal attitude, arch would be better off without you. So, bye.
]]>Well I have given all the information I can think off
Really? You didn't think that posting actual errors would be useful? You didn't try booting with debug to get a better idea of what's going wrong?
I can do without the pain ... I have a life ...
Boo hoo.
]]>