Arch boots start into tty

noberuf · 2025-12-17 16:22:39

My system worked fine yesterday before i went to sleep i updated using pacman -Syu and shutdown woke up in the morning and now my system boots straight into tty.

I can start my greeter manually by using ly-dm but i cannot login i get the error "failed to initialize user".

I tried startx command and i get several errors relating to twm, xclock & xterm not being installed but checking pacman -Qe i can see xorg-utils is installed.

There is also another error relating to $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR" not being defined but i dont know what that means.

Any help is appreciated. I dont know if this is an nvidia driver, desktop environment(LXQT) or xorg issue.
The full error log is below:

Error
X.Org X Server 1.21.1.21
X Protocol Version 11, Revision 0
Current Operating System: Linux Gold-0 6.18.1-arch1-2 #1 SMP PREEMPT_DYNAMIC Sat, 13 Dec 2025 18:23:21 +0000 x86_64
Kernel command line: initrd=\initramfs-linux.img cryptdevice=PARTUUID=2f194594-7a2a-410e-a7d8-0d3033c0334a:root root=/dev/mapper/root zswap.enabled=0 rw rootfstype=ext4 intel_iommu=on iommu=pt vfio-pci.ids=10de:1e07,10de:10f7
 
Current version of pixman: 0.46.4
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Dec 17 15:42:26 2025
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Could not resolve keysym XF86OK
> Warning:          Could not resolve keysym XF86GoTo
> Warning:          Could not resolve keysym XF86VendorLogo
> Warning:          Could not resolve keysym XF86MediaSelectProgramGuide
> Warning:          Could not resolve keysym XF86MediaSelectProgramGuide
> Warning:          Could not resolve keysym XF86MediaSelectHome
> Warning:          Could not resolve keysym XF86MediaLanguageMenu
> Warning:          Could not resolve keysym XF86MediaTitleMenu
> Warning:          Could not resolve keysym XF86AudioChannelMode
> Warning:          Could not resolve keysym XF86MediaSelectPC
> Warning:          Could not resolve keysym XF86MediaSelectTV
> Warning:          Could not resolve keysym XF86MediaSelectCable
> Warning:          Could not resolve keysym XF86MediaSelectVCR
> Warning:          Could not resolve keysym XF86MediaSelectVCRPlus
> Warning:          Could not resolve keysym XF86MediaSelectSatellite
> Warning:          Could not resolve keysym XF86MediaSelectCD
> Warning:          Could not resolve keysym XF86MediaSelectTape
> Warning:          Could not resolve keysym XF86MediaSelectRadio
> Warning:          Could not resolve keysym XF86MediaSelectTuner
> Warning:          Could not resolve keysym XF86MediaPlayer
> Warning:          Could not resolve keysym XF86MediaSelectTeletext
> Warning:          Could not resolve keysym XF86MediaSelectAuxiliary
> Warning:          Could not resolve keysym XF86MediaPlaySlow
> Warning:          Could not resolve keysym XF86NumberEntryMode
> Warning:          Could not resolve keysym XF86RefreshRateToggle
> Warning:          Could not resolve keysym XF86Accessibility
> Warning:          Could not resolve keysym XF86DoNotDisturb
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Could not resolve keysym XF86OK
> Warning:          Could not resolve keysym XF86GoTo
> Warning:          Could not resolve keysym XF86VendorLogo
> Warning:          Could not resolve keysym XF86MediaSelectProgramGuide
> Warning:          Could not resolve keysym XF86MediaSelectProgramGuide
> Warning:          Could not resolve keysym XF86MediaSelectHome
> Warning:          Could not resolve keysym XF86MediaLanguageMenu
> Warning:          Could not resolve keysym XF86MediaTitleMenu
> Warning:          Could not resolve keysym XF86AudioChannelMode
> Warning:          Could not resolve keysym XF86MediaSelectPC
> Warning:          Could not resolve keysym XF86MediaSelectTV
> Warning:          Could not resolve keysym XF86MediaSelectCable
> Warning:          Could not resolve keysym XF86MediaSelectVCR
> Warning:          Could not resolve keysym XF86MediaSelectVCRPlus
> Warning:          Could not resolve keysym XF86MediaSelectSatellite
> Warning:          Could not resolve keysym XF86MediaSelectCD
> Warning:          Could not resolve keysym XF86MediaSelectTape
> Warning:          Could not resolve keysym XF86MediaSelectRadio
> Warning:          Could not resolve keysym XF86MediaSelectTuner
> Warning:          Could not resolve keysym XF86MediaPlayer
> Warning:          Could not resolve keysym XF86MediaSelectTeletext
> Warning:          Could not resolve keysym XF86MediaSelectAuxiliary
> Warning:          Could not resolve keysym XF86MediaPlaySlow
> Warning:          Could not resolve keysym XF86NumberEntryMode
> Warning:          Could not resolve keysym XF86RefreshRateToggle
> Warning:          Could not resolve keysym XF86Accessibility
> Warning:          Could not resolve keysym XF86DoNotDisturb
Errors from xkbcomp are not fatal to the X server
Failed to connect to user scope bus via local transport: $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined (consider using --machine=<user>@.host --user to connect to bus of other user)
dbus-update-activation-environment: error: unable to connect to D-Bus: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead
/etc/X11/xinit/xinitrc: line 52: twm: command not found
/etc/X11/xinit/xinitrc: line 53: xclock: command not found
/etc/X11/xinit/xinitrc: line 54: xterm: command not found
/etc/X11/xinit/xinitrc: line 56: exec: xterm: not found
/etc/X11/xinit/xinitrc: line 55: xterm: command not found
xinit: connection to X server lost

waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.

V1del · 2025-12-17 16:28:25

The update will have included a note when ly was upgraded that there was a change in how it's service file is enabled: https://gitlab.archlinux.org/archlinux/ … type=heads

noberuf · 2025-12-17 16:55:51

V1del wrote:

The update will have included a note when ly was upgraded that there was a change in how it's service file is enabled: https://gitlab.archlinux.org/archlinux/ … type=heads

Thank you, this worked for me.

sudo systemctl enable --now ly@tty1.service'

Last edited by noberuf (2025-12-17 16:56:16)

Arch Linux

#1 2025-12-17 16:22:39

Arch boots start into tty

#2 2025-12-17 16:28:25

Re: Arch boots start into tty

#3 2025-12-17 16:55:51

Re: Arch boots start into tty

Board footer