You are not logged in.
I am getting a white screen saying "oh no, something has gone wrong." A problem has occurred and the system can't recover. Please contact a system administrator.
when doing journalctl -xe -u gdm I get this:
Jun 25 18:26:37 archlinux systemd[1]: Starting GNOME Display Manager...
Subject: A start job for unit gdm.service has begun execution
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/l … temd-devel
A start job for unit gdm.service has begun execution.
The job identifier is 142.
Jun 25 18:26:37 archlinux systemd[1]: Started GNOME Display Manager.
Subject: A start job for unit gdm.service has finished successfully
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/l … temd-devel
A start job for unit gdm.service has finished successfully.
The job identifier is 142.
Jun 25 18:26:37 archlinux gdm-launch-environment][672]: pam_systemd (gdm-launch-environment:session): New sd-bus connection (system-bus-pam-systemd-672) opened.
Jun 25 18:26:38 archlinux gdm-launch-environment][672]: pam_systemd (gdm-launch-environment:session): New sd-bus connection (system-bus-pam-systemd-672) opened.
Jun 25 18:26:38 archlinux gdm[645]: Gdm: GdmDisplay: Session never registered, failing
Jun 25 18:26:38 archlinux gdm[645]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Jun 25 18:26:38 archlinux gdm[645]: Gdm: Child process -692 was already dead.
Jun 25 18:26:38 archlinux gdm[645]: Gdm: GdmDisplay: Session never registered, failing
Jun 25 18:26:38 archlinux gdm[645]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Jun 25 18:26:38 archlinux gdm[645]: Gdm: Child process -692 was already dead.
Jun 25 18:26:38 archlinux gdm-launch-environment][727]: pam_systemd (gdm-launch-environment:session): New sd-bus connection (system-bus-pam-systemd-727) opened.
Edit: I forgot to say I'm running arch from a lenovo x1 carbon gen 8, and everything is up to date.
Last edited by mirkomassa (2024-06-25 16:40:55)
Offline
I've gotten this before, the fix was just a simple `yay -Syu`, or if you want to use regular pacman `sudo pacman -Syu` from a TTY.
--
Wesley Bryie - Student
wes@wesbryie.com
https://wesbryie.com
Offline