Since the upgrade to 20.04 I'm unable to login Wayland sessions. I'm using vanilla GNOME so in my greeter I have four options (GNOME, GNOME on Xorg, Ubuntu and Ubuntu on Wayland). I can log in the two Xorg sessions, but not the Wayland ones.
I ran journalctl -b
and found these error messages:
gdm-password][118320]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: No such file or directory
gdm-password][118320]: gkr-pam: unable to locate daemon control file
gdm-password][118320]: gkr-pam: stashed password to try later in open session
systemd[1449]: Dependency failed for GNOME XSettings.
systemd[1942]: Dependency failed for GNOME Shell on Wayland.
systemd[1942]: Dependency failed for GNOME Wayland Session.
systemd[1942]: Dependency failed for GNOME Wayland Session (session: gnome)
I read that this might be a problem with NVIDIA GPUs, but my system has an Intel one.
EDIT
grep -i WaylandEnable /etc/gdm3/custom.conf
gives:
#WaylandEnable=false
EDIT 2
I tried creating another user and managed to log into a Wayland session. So the issue resides in my user folder.
How do I re-enable Wayland sessions?
Best Answer
Run:
Change this:
to this:
Reboot ans retest Wayland.
Update #1:
After closer review, turned out it was already commented out.
Created another user account, and Wayland works there.
This indicates a problem in the original user's account.
The most common problems occur in the
~/.cache
,~/.local
, and~/.config
folders.ONE at a time, rename the folder to
.cache.HOLD
, etc.Log out and see if you can log in using Wayland. If not, rename the second folder, retest, etc.
These three folders will recreate themselves and populate themselves with default settings. If renaming these folders fixes the problem, MOVE (not copy) the contents of the
.HOLD
folders back into their respective non-.HOLD
folders, but DO NOT replace existing files. Any files left over in.HOLD
folders are suspects in causing the problem.