Arch Linux

InFerYes

Member

Registered: 2012-11-13

Posts: 41

System broken after update (systemd disk dependency + GNOME fails)

I've ran pacman -Syu and had issues booting my PC.

First there was an issue with a disk that systemd failed

Here is what I believe to be the relevant snippet of the log:

okt 07 10:45:18 ranger dbus-broker[1434]: Dispatched 344 messages @ 1(±2)μs / message.
okt 07 10:45:18 ranger systemd[1410]: Stopping D-Bus User Message Bus...
okt 07 10:45:19 ranger systemd[1410]: Stopped D-Bus User Message Bus.
okt 07 10:45:19 ranger systemd[1410]: Removed slice User Core Session Slice.
okt 07 10:45:19 ranger systemd[1410]: Closed D-Bus User Message Bus Socket.
okt 07 10:45:19 ranger systemd[1410]: Removed slice User Application Slice.
okt 07 10:45:19 ranger systemd[1410]: Reached target Shutdown.
okt 07 10:45:19 ranger systemd[1410]: Finished Exit the Session.
okt 07 10:45:19 ranger systemd[1410]: Reached target Exit the Session.
okt 07 10:45:19 ranger systemd-logind[511]: Removed session 22.
okt 07 10:45:19 ranger (sd-pam)[1412]: pam_unix(systemd-user:session): session closed for user gdm-greeter
okt 07 10:45:19 ranger systemd[1]: user@60588.service: Deactivated successfully.
okt 07 10:45:19 ranger systemd[1]: Stopped User Manager for UID 60588.
okt 07 10:45:19 ranger systemd[1]: Stopping User Runtime Directory /run/user/60588...
okt 07 10:45:19 ranger systemd[1]: run-user-60588.mount: Deactivated successfully.
okt 07 10:45:19 ranger systemd[1]: user-runtime-dir@60588.service: Deactivated successfully.
okt 07 10:45:19 ranger systemd[1]: Stopped User Runtime Directory /run/user/60588.
okt 07 10:45:19 ranger systemd[1]: Removed slice User Slice of UID 60588.
okt 07 10:45:19 ranger systemd[1]: user-60588.slice: Consumed 1.032s CPU time, 30.8M memory peak.
okt 07 10:46:11 ranger systemd[1]: dev-disk-by\x2duuid-df2b5a15\x2d8767\x2d4aad\x2da8df\x2d90510e3501b1.device: Job dev-disk-by\x2duuid-df2b5a15\x2d8767\x2d4aad\x2da8df\x2d90510e3501b1.device/start timed out.
okt 07 10:46:11 ranger systemd[1]: Timed out waiting for device /dev/disk/by-uuid/df2b5a15-8767-4aad-a8df-90510e3501b1.
okt 07 10:46:11 ranger systemd[1]: Dependency failed for /mnt/df2b5a15-8767-4aad-a8df-90510e3501b1.
okt 07 10:46:11 ranger systemd[1]: mnt-df2b5a15\x2d8767\x2d4aad\x2da8df\x2d90510e3501b1.mount: Job mnt-df2b5a15\x2d8767\x2d4aad\x2da8df\x2d90510e3501b1.mount/start failed with result 'dependency'.
okt 07 10:46:11 ranger systemd[1]: Startup finished in 17.105s (firmware) + 5.291s (loader) + 1.804s (kernel) + 1min 30.648s (userspace) = 1min 54.849s.
okt 07 10:46:11 ranger systemd[1]: dev-disk-by\x2duuid-df2b5a15\x2d8767\x2d4aad\x2da8df\x2d90510e3501b1.device: Job dev-disk-by\x2duuid-df2b5a15\x2d8767\x2d4aad\x2da8df\x2d90510e3501b1.device/start failed with result 'timeout'.

After entering the system emergency console (press e button on boot selection (uefi) then add systemd.unit=desired.target at the end of the long string) I have edited fstab by commenting all my non-root disks. This made the system boot again.

Now I'm left with a blinking cursor in the top left of my screen.

It appears to be that GNOME is crasing:

okt 07 10:45:08 ranger systemd[1]: Started Process Core Dump (PID 1444/UID 0).
okt 07 10:45:08 ranger systemd-coredump[1445]: [?] Process 1436 (gnome-session-i) of user 60588 dumped core.

                                               
After some digging it appears to be related to X11, some genius removed Xorg mentions on the wiki instead of providing a path forward for migration.

Now my system won't start properly, I'm troubleshooting this by running startx and relying on fluxbox... What steps should I take?

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 68,770

Re: System broken after update (systemd disk dependency + GNOME fails)

The log shows a timeout attempting to mount df2b5a15-8767-4aad-a8df-90510e3501b1 into /mnt/df2b5a15-8767-4aad-a8df-90510e3501b1 - check your fstab wrt this, but it's not what's crashing the gnome session.
Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

add systemd.unit=desired.target

that's not a valid target (on a default system) - you're probably taking some placeholder a bit too literally there.

I'm … running startx and relying on fluxbox... What steps should I take?

Continue to do so because it spares you the headaches gnome causes you?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

InFerYes

Member

Registered: 2012-11-13

Posts: 41

Re: System broken after update (systemd disk dependency + GNOME fails)

I thought the target looked funny, but it worked. I consider the disk issue resolved for now, I will deal with that once I have my desktop working again. I don't consider these issues related, they both occured after my system update.

Here is the log you requested: http://0x0.st/KucR.txt

Last edited by InFerYes (2025-10-07 19:15:25)

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 68,770

Re: System broken after update (systemd disk dependency + GNOME fails)

okt 07 21:10:35 ranger gnome-session-i[646]: Starting GNOME session target: gnome-session-x11@gnome-login.target
okt 07 21:10:35 ranger gnome-session-i[646]: Failed to start unit gnome-session-x11@gnome-login.target: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-session-x11@gnome-login.target not found.
okt 07 21:10:35 ranger kernel: traps: gnome-session-i[646] trap int3 ip:7ffa0afd0b8c sp:7ffddcbcc490 error:0 in libglib-2.0.so.0.8600.0[64b8c,7ffa0af8a000+a7000]
okt 07 21:10:35 ranger systemd-coredump[654]: Process 646 (gnome-session-i) of user 60578 terminated abnormally with signal 5/TRAP, processing...
okt 07 21:10:35 ranger systemd[1]: Created slice Slice /system/systemd-coredump.
okt 07 21:10:35 ranger systemd[1]: Started Process Core Dump (PID 654/UID 0).
okt 07 21:10:35 ranger systemd-coredump[655]: Process 646 (gnome-session-i) of user 60578 dumped core.
                                              
                                              Stack trace of thread 646:
                                              #0  0x00007ffa0afd0b8c g_log_structured_array (libglib-2.0.so.0 + 0x64b8c)
                                              #1  0x00007ffa0afd12e0 g_log_default_handler (libglib-2.0.so.0 + 0x652e0)
                                              #2  0x00007ffa0afd157a g_logv (libglib-2.0.so.0 + 0x6557a)
                                              #3  0x00007ffa0afd1904 g_log (libglib-2.0.so.0 + 0x65904)
                                              #4  0x000055a0e04e3686 n/a (/usr/lib/gnome-session-init-worker + 0x2686)
                                              #5  0x00007ffa0ac27675 n/a (libc.so.6 + 0x27675)
                                              #6  0x00007ffa0ac27729 __libc_start_main (libc.so.6 + 0x27729)
                                              #7  0x000055a0e04e3c95 n/a (/usr/lib/gnome-session-init-worker + 0x2c95)

Gnome 49 does no longer support X11, disable https://wiki.archlinux.org/title/GDM#Use_Xorg_backend to run it on wayland.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

InFerYes

Member

Registered: 2012-11-13

Posts: 41

Re: System broken after update (systemd disk dependency + GNOME fails)

Yes! I just found that fix via other means and wanted to post it. I knew X11 was nog longer supported, I just didn't know how or where to fix it. I had to change /etc/gdm/custom.config and then restarted the GDM unit, which did the trick.

Thanks for troubleshooting.