Wayland Not Working By Default On An Offline Install

This is what happens when I log into Wayland.

I don’t understand why you have startx in your .bash_profile .

You should have sddm or so installed. Don’t you?

If yes, could you comment out (or better delete) these lines and then retest?

The if statement in ~/.bash_profile should be set to

if [ "$XDG_SESSION_TYPE" = "x11" ] && [ -z "$DISPLAY" ] && [ -n "$XDG_VTNR" ] && [ "$XDG_VTNR" -eq 1 ]; then
  exec startx
fi

Edit: see the better fix below, which is removing the whole if...fi statement.

basic x environment casued by starting with startx .
Is this an offline or online install?

I still dont get how you “log into wayland”. startx is obviously wrong. Although your screenshot looks exactly like a plain “startx” session.

So how did you log into wayland? And by the way: The wording is wrong. You do not log into wayland. You log into kde, gnome, xfce and ask the desktop environment to use wayland instead of X11.

So how do you log into your desktop environment? And how did you tell it to use wayland.

A better fix is to remove the whole if statement from ~/.bash_profile.

Now I’m able to login into wayland after 2024/01/09 update, through gdm using GNOME 45.3. Thanks

System Details Report


Report details

  • Date generated: 2024-01-09 12:24:37

Hardware Information:

  • Hardware Model: Dell Inc. Inspiron 5567
  • Memory: 8.0 GiB
  • Processor: Intel® Core™ i7-7500U × 4
  • Graphics: Intel® HD Graphics 620 (KBL GT2)
  • Disk Capacity: 1.0 TB

Software Information:

  • Firmware Version: 1.5.0
  • OS Name: EndeavourOS
  • OS Build: 2023.05.28
  • OS Type: 64-bit
  • GNOME Version: 45.3
  • Windowing System: Wayland
  • Kernel Version: Linux 6.6.10-arch1-1

This one is the offline install , because I borked my grub config so I had to reinstall using the offline setup to get my system asap , after which I updated it.

From the login screen you have two options at the lower left corner , x11 and Wayland to choose from as your session, this is how I “log into a Wayland session” and yes the wording was pretty wrong.

Sddm is installed and so are other packages .

If this was the cause of the issue, I can’t understand why the title of the topic says: Wayland Not Working After Update ?

No updates will never ever put that in ~/.bash_profile.

:thinking:

why dont you provide more meaningful information as suggested earlier in this thread. And get rid of this “exec startx” if you want to test wayland.

Good information would be the journal. It will show some entries from SDDM how it tries to start a wayland session and how it fails.

This issue was not caused by an update but a flaw in the offline install which copies a wrong .bash_profile.
The team is aware of this and fixing it as soon as possible.

The fix to this on existing installs is to remove the execution of startx.

Issue is solved now and yes the title was indeed wrong . What I presumed as an issue introduced by an update was a flaw in endeavour’s offline install instead.

Thank you both for the explanation! Now that clear things up.
I see the title of the topic has been changed as well by @Hitman_Agent47 to better match the issue.
Glad you’ve pinpoint the issue of the offline install and that it will be resolved soon!

I guess this is the reason i couldn’t log in with Wayland on Nvidia as i installed the offline version since my WiFi was given issues downloading.

Edit: I managed to install with the online installer and now it’s working.