However, if I log in and immediately log out, Wayland is available on the login screen and you log in to a Wayland session.

This is identical on both my laptops, they are very different in hardware and performance. This started happening after updates about 3 weeks ago.

I have looked at logs and I can see the subsystems trying Wayland and falling back to X but I can’t see an obvious reason (probably my lack of experience at this).

Anyone else experienced similar?

  • @jimmy90OP
    1•1 year ago

    thought i would post some logs, maybe someone can spot something obvious

    • @[email protected]
      1•1 year ago

      It’s very difficult for me to work through these logs as they are missing new lines.

      But there is plenty of stuff giving errors:

      Aug 20 14:07:08 blackcloud gnome-session-binary[635]: Unrecoverable failure in required component org.gnome.Shell.desktop

      Aug 20 14:07:08 blackcloud org.gnome.Shell.desktop[646]: Failed to setup: No GPUs found

      Aug 20 14:07:08 blackcloud gdm[398]: Gdm: GdmDisplay: Session never registered, failing Aug 20 14:07:08 blackcloud gdm[398]: Gdm: Child process -628 was already dead.

      Aug 20 14:08:08 blackcloud /usr/lib/gdm-wayland-session[2472]: dbus-daemon[2472]: [session uid=120 pid=2472] Activated service ‘org.freedesktop.systemd1’ failed: Process org.freedesktop.systemd1 exited with status 1

      Aug 20 14:08:25 blackcloud gnome-shell[2483]: Connection to xwayland lost Aug 20 14:08:25 blackcloud gnome-shell[2483]: Xwayland terminated, exiting since it was mandatory Aug 20 14:08:25 blackcloud org.gnome.Shell.desktop[2483]: GNOME Shell terminated with an error: Xwayland exited unexpectedly

      You might want to try (in no specific order) to check why xwayland is failing, reinstall gnome, clean up old configuration, do a system upgrade, try pacdiff.