You are not logged in.
Following the Arch wiki to setup kmscon and I cannot get Gnome to do automatic login anymore.
If I log in and run loginctl I see this:
loginctl sessikon-status
Failed to get path for 'auto': Caller does not belong to any known session and doesn't own any suitable session.The wiki mentions adding kmsconvt@tty1.service to my display manager but when I looked the changes were made upstream:
gdm.service
[Unit]
Description=GNOME Display Manager
# replaces the getty/kmsconvt
Conflicts=getty@tty1.service kmsconvt@tty1.service
After=getty@tty1.service kmsconvt@tty1.service
# replaces plymouth-quit since it quits plymouth on its own
Conflicts=plymouth-quit.service
After=plymouth-quit.service
# Needs all the dependencies of the services it's replacing
# pulled from getty@.service and plymouth-quit.service
# (except for plymouth-quit-wait.service since it waits until
# plymouth is quit, which we do)
After=rc-local.service plymouth-start.service systemd-user-sessions.service
# GDM takes responsibility for stopping plymouth, so if it fails
# for any reason, make sure plymouth still stops
OnFailure=plymouth-quit.service
[Service]
ExecStart=/usr/bin/gdm
KillMode=mixed
Restart=always
IgnoreSIGPIPE=no
BusName=org.gnome.DisplayManager
EnvironmentFile=-/etc/locale.conf
ExecReload=/bin/kill -SIGHUP $MAINPID
KeyringMode=shared
[Install]
Alias=display-manager.serviceGnome display manager is active but failing:
systemctl status gdm.service
● gdm.service - GNOME Display Manager
Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled; preset: disabled)
Active: active (running) since Sat 2026-11-21 06:22:17 EST; 1min 18s ago
Invocation: 9ddd3fafe9d141eeaadbf543de242837
Main PID: 1251 (gdm)
Tasks: 5 (limit: 37107)
Memory: 3.5M (peak: 6.9M)
CPU: 59ms
CGroup: /system.slice/gdm.service
└─1251 /usr/bin/gdm
Nov 21 06:22:18 lurch gdm[1251]: Gdm: Child process -1492 was already dead.
Nov 21 06:22:18 lurch gdm[1251]: Gdm: GdmDisplay: Session never registered, failing
Nov 21 06:22:18 lurch gdm[1251]: Gdm: Child process -1492 was already dead.
Nov 21 06:22:18 lurch gdm[1251]: Gdm: GdmDisplay: Session never registered, failing
Nov 21 06:22:18 lurch gdm[1251]: Gdm: Child process -1551 was already dead.
Nov 21 06:22:18 lurch gdm[1251]: Gdm: GdmDisplay: Session never registered, failing
Nov 21 06:22:18 lurch gdm[1251]: Gdm: Child process -1551 was already dead.
Nov 21 06:22:18 lurch gdm[1251]: Gdm: GdmDisplay: Session never registered, failing
Nov 21 06:22:18 lurch gdm[1251]: Gdm: GdmLocalDisplayFactory: maximum number of display failures reached. Giving up.
Nov 21 06:22:18 lurch gdm[1251]: Gdm: Child process -1604 was already dead.Tried using automatic login via kmscon with no success.
Tried disabling automatic login completely with no success.
Not sure what to try next.
Last edited by lenhuppe (Today 11:26:33)
Offline
GDM already says it in the unit you pasted: Conflicts=getty@tty1.service kmsconvt@tty1.service. tty1 belongs to the display manager. kmscon on that same VT is a second landlord, and "Session never registered" is GDM giving up after the child dies.
Disable kmsconvt@tty1, reboot once so the VT is clean, and if you still want kmscon put it on a later VT (kmsconvt@tty2). Autologin stays in /etc/gdm/custom.conf. The loginctl "auto" line is just that shell sitting outside a logind session, which is what you get when the graphical one never registered.
The wiki note about adding kmsconvt to the display manager is the old arrangement. The unit you quoted already replaced it.
Offline
GDM already says it in the unit you pasted: Conflicts=getty@tty1.service kmsconvt@tty1.service. tty1 belongs to the display manager. kmscon on that same VT is a second landlord, and "Session never registered" is GDM giving up after the child dies.
Disable kmsconvt@tty1, reboot once so the VT is clean, and if you still want kmscon put it on a later VT (kmsconvt@tty2). Autologin stays in /etc/gdm/custom.conf. The loginctl "auto" line is just that shell sitting outside a logind session, which is what you get when the graphical one never registered.
The wiki note about adding kmsconvt to the display manager is the old arrangement. The unit you quoted already replaced it.
1) Reinstalled
2) Enabled kmsconvt@ttyX.service along with kmsconvt@tty1.service and the system rebooted ok.
3) Switched to multi-user, rebooted, and was able to log in with a kmscon prompt.
4) Switched back to graphical and the system crashed while rebooting. Had to reset and reinstall.
Last edited by lenhuppe (Today 18:42:35)
Offline