Mercury neo -- weird boot up

just installed mercury as virtual machine.

when booting up the system remains for about 2 minutes on ‘reached target Graphical Interface’
no error report - then the start screen appears and everything works well

any idea what happens or what to do?

you can check your journal and see if there is anything in there maybe check
systemd-analyze blame and see what information it can tell you.

no indication of an issue

but I found out a likely reason —> wayland
using Xorg doesn’t show the behavior

1 Like

Noticed it today as well. I can only login using X, wayland is not listed as choice at all. Both login and logout are unusually long.

This is a Regression: GNOME falls back to X11 after Wayland times out (fresh install in KVM).

sudo journalctl -b

Will show the issue:

...
Apr 25 09:37:08 EndeavourOS gnome-shell[622]: Running GNOME Shell (using mutter 48.2) as a Wayland display server
Apr 25 09:37:08 EndeavourOS avahi-daemon[474]: Server startup complete. Host name is EndeavourOS.local. Local service cookie is 988154112.
Apr 25 09:37:08 EndeavourOS systemd[1]: Starting RealtimeKit Scheduling Policy Service...
Apr 25 09:37:08 EndeavourOS systemd[1]: Started RealtimeKit Scheduling Policy Service.
Apr 25 09:37:08 EndeavourOS rtkit-daemon[649]: Successfully called chroot.
Apr 25 09:37:08 EndeavourOS rtkit-daemon[649]: Successfully dropped privileges.
Apr 25 09:37:08 EndeavourOS rtkit-daemon[649]: Successfully limited resources.
Apr 25 09:37:08 EndeavourOS rtkit-daemon[649]: Canary thread running.
Apr 25 09:37:08 EndeavourOS rtkit-daemon[649]: Running.
Apr 25 09:37:08 EndeavourOS rtkit-daemon[649]: Watchdog thread running.
Apr 25 09:37:08 EndeavourOS rtkit-daemon[649]: Supervising 0 threads of 0 processes of 0 users.
Apr 25 09:37:08 EndeavourOS rtkit-daemon[649]: Successfully made thread 648 of process 622 owned by '1000' high priority at nice level -15. 
Apr 25 09:37:08 EndeavourOS rtkit-daemon[649]: Supervising 1 threads of 1 processes of 1 users.
Apr 25 09:37:08 EndeavourOS gnome-shell[622]: Thread 'KMS thread' will be using high priority scheduling
Apr 25 09:37:08 EndeavourOS gnome-shell[622]: libEGL warning: egl: failed to create dri2 screen
Apr 25 09:37:08 EndeavourOS gnome-shell[622]: MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER)
Apr 25 09:37:17 EndeavourOS systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Apr 25 09:37:38 EndeavourOS systemd-timesyncd[378]: Contacted time server 54.39.17.239:123 (2.arch.pool.ntp.org).
Apr 25 09:37:38 EndeavourOS systemd-timesyncd[378]: Initial clock synchronization to Fri 2025-04-25 09:37:38.262785 EDT. 
Apr 25 09:37:38 EndeavourOS systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Apr 25 09:37:41 EndeavourOS systemd[1]: Starting Rotate log files...
Apr 25 09:37:41 EndeavourOS systemd[1]: logrotate.service: Deactivated successfully.
Apr 25 09:37:41 EndeavourOS systemd[1]: Finished Rotate log files.
Apr 25 09:38:39 EndeavourOS systemd[542]: org.gnome.Shell@wayland.service: start operation timed out. Terminating.
...

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.