2

systemd of my archlinux hangs since this morning without any error message and before TTY. So, I cannot use Ctrl+Alt+F1. The last thing I see is Reached Target Bluetooth. But everything looks fine except it does not boot into GDM.

Although I know that systemd itself causes this issue, as it is very well explained here.

What can I do to reach either TTY or login?

Edit: After hours of trying, I have not found any solution. I tried to autologin with gdm, to disable it, checked fstab to no avail, checked journalctl (which does not show an issues), fscked sda3, tried to get online to update the system (which has failed), I can access files like fstab via a Live-CD like Knoppix but nothing has helped. It's a pity.

Improve this question
1
  • 1
    Welcome to U&L. If you know what you are capable of doing, asking how to do that, makes your post a much better question. Asking about whether people are capable of assisting you (for which the only appropriate answers are "Yes, someone can help you out" or "No, nobody can help you out").
    – Anthon
    Commented Sep 20, 2015 at 9:25

2 Answers 2

Reset to default
2

Mine did the same. Did you happen to try to install updates using Gnome's update-at-shutdown feature?

Anyway, here's what fixed it for me:

  1. Boot to GRUB (or whatever bootloader you use), and edit the kernel command line so that it has systemd.unit=graphical.target. Then let it boot using the new parameters.

  2. GDM should start, and you should be able to log in as normal.

  3. When you reboot, it should be unwedged.

I don't know, but my hypothesis is that the update feature changes the default boot target, temporarily, and the update target is somehow borked.

Improve this answer
6
  • Hi, ams, thank you very much for this answer. You saved me! I guess, this was the problem. Yes, I used indeed Gnome's update-at-shutdown feature. I have one little issue, though, I cannot get into GRUB, since GRUB_HIDDEN-TIMEOUT=0. Do you know by any chance if I can just change /etc/default/grub within a Live CD without chroot?
    – Til Hund
    Commented Sep 21, 2015 at 13:21
  • 1
    You can change /boot/grub.cfg directly, or you can change /etc/default/grub and then regenerate grub.cfg. I always have a 1 second GRUB timeout so I can break in if I'm quick.
    – ams
    Commented Sep 21, 2015 at 13:27
  • 1
    It happened to me again, and the multi-user.target step was unnecessary, so I updated my answer.
    – ams
    Commented Sep 24, 2015 at 8:40
  • 1
    The install-updates-on-shutdown feature appears to be working again now. I just used it without anything breaking.
    – ams
    Commented Oct 7, 2015 at 9:46
  • 1
    Nope, it's just a convenient way to do the same thing (although I noticed gnome-software doesn't seem to bother with a few, obscure packages).
    – ams
    Commented Oct 7, 2015 at 11:21
0

I had a similar problem. It was caused by systemd after update bragging that [email protected] file was not a symlink. Making it a symlink to library fixed the issue.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .