User cannot login and no networking after system update

pcc322 · 2024-01-21 20:27:15

A few days ago I ran a system update with pacman -Syu as usual, today when I started my computer there were come red messages that flashed by just before coming to the terminal login. It is very hard to read the messages but they have something about failure and D-Bus.

When I log in with my user name some text flashes by as usual like it is going to go to desktop environment (LXDE) but it comes back to the terminal login.

I can log in with root, su to my user, startx then startlxde, which takes me into LXDE, though not the usual setup, when I close the terminal windows is closes LXDE.

I have no networking with wifi nor ethernet as user or root so I am not able to attempt to do anything with pacman.

All of my files and directories seem fine.

I do not know where to look for startup logs to get specific messages.

Any help on getting this fixed is much appreciated.

seth · 2024-01-21 20:46:14

Please post your complete system journal for the boot:

sudo journalctl -b > /tmp/journal.txt

You'll have to usb-walk /tmp/journal.txt to a system w/ network, if you've access to some live distro that provides you w/ network access, you can also draw the journal from there, https://wiki.archlinux.org/title/System … al_to_view and pipe it to 0x0.st

However in the latter case please take a look at the journal to estimate whether it covers the concerned incident.

pcc322 · 2024-01-23 01:45:22

startup log in here

There are a number of failures listed, I am aware of the intel wireless chip failure which is unrelated to this problem but

Jan 22 19:22:01 x201 systemd[1]: Failed to start User Login Management.
Jan 22 19:22:01 x201 systemd[1]: Failed to listen on D-Bus System Message Bus Socket.

seem relevant.

Last edited by pcc322 (2024-01-23 01:48:37)

Head_on_a_Stick · 2024-01-23 08:28:19

Is this a Parabola system or are you just using their kernel? Note that the official Arch kernels do not contain any blobs at all.

EDIT: you're running a systemd version from November but a kernel from December. Were you using partial upgrades? You should have updated your system before posting here.

Last edited by Head_on_a_Stick (2024-01-23 08:32:21)

seth · 2024-01-23 08:35:02

Jan 22 19:22:01 x201 systemd[1]: dbus.socket: Socket service dbus.service not loaded, refusing.
Jan 22 19:22:01 x201 systemd-logind[343]: Failed to connect to system bus: No such file or directory
Jan 22 19:22:01 x201 systemd-logind[343]: Failed to fully start up daemon: No such file or directory
Jan 22 19:22:01 x201 systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 19:22:01 x201 systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
Jan 22 19:22:01 x201 kernel: usbcore: registered new interface driver ath9k_htc
Jan 22 19:22:01 x201 systemd[1]: Failed to start User Login Management.

Botched switch to dbus-broker?

pcc322 · 2024-01-24 03:13:38

Head_on_a_Stick wrote:

Is this a Parabola system or are you just using their kernel? Note that the official Arch kernels do not contain any blobs at all.
EDIT: you're running a systemd version from November but a kernel from December. Were you using partial upgrades? You should have updated your system before posting here.

It is an Arch install with Parabola kernel. If Arch kernels have no blobs, is Arch linux kernel basically linux-libre?

I had updated the system with pacman -Syu then shutdown the computer, and did not do partial update, at least not intentionally. The problem appeared the next time I booted, and as of current, I haven't found a way to connect to internet with wifi or ethernet so I am not able to update at present.

seth wrote:

Jan 22 19:22:01 x201 systemd[1]: dbus.socket: Socket service dbus.service not loaded, refusing.
Jan 22 19:22:01 x201 systemd-logind[343]: Failed to connect to system bus: No such file or directory
Jan 22 19:22:01 x201 systemd-logind[343]: Failed to fully start up daemon: No such file or directory
Jan 22 19:22:01 x201 systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 19:22:01 x201 systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
Jan 22 19:22:01 x201 kernel: usbcore: registered new interface driver ath9k_htc
Jan 22 19:22:01 x201 systemd[1]: Failed to start User Login Management.

Botched switch to dbus-broker?

Maybe. Any suggestions on how to go about fixing, preferably without reinstalling Arch? I am thinking booting from install USB, mounting the existing partitions, chrooting into the installed system and trying to update from there.

Last edited by pcc322 (2024-01-24 03:47:27)

seth · 2024-01-24 09:06:15

I am thinking booting from install USB, mounting the existing partitions, chrooting into the installed system and trying to update from there.

In the chroot, check

pacman -Qikk dbus dbus-broker dbus-units systemd

Also try the regular kernel, just to be sure.

Head_on_a_Stick · 2024-01-24 20:57:27

pcc322 wrote:

If Arch kernels have no blobs, is Arch linux kernel basically linux-libre?

Not quite. The "linux-libre" kernel is modified so that it cannot load blobs at all. Note that this might render your system unstable due to missing CPU microcode.

Arch Linux

#1 2024-01-21 20:27:15

User cannot login and no networking after system update

#2 2024-01-21 20:46:14

Re: User cannot login and no networking after system update

#3 2024-01-23 01:45:22

Re: User cannot login and no networking after system update

#4 2024-01-23 08:28:19

Re: User cannot login and no networking after system update

#5 2024-01-23 08:35:02

Re: User cannot login and no networking after system update

#6 2024-01-24 03:13:38

Re: User cannot login and no networking after system update

#7 2024-01-24 09:06:15

Re: User cannot login and no networking after system update

#8 2024-01-24 20:57:27

Re: User cannot login and no networking after system update

Board footer