[SOLVED] GDM cannot start Gnome Wayland

ChilledTonic · 2021-12-18 06:49:58

Hi there,

I've installed gnome and GDM using the standard advice found on this wiki page: https://wiki.archlinux.org/title/GNOME

Previously I've been using sway, which works without issue - and can be launched without issue from GDM. GDM can also start gnome in X mode.

However, GDM refuses to launch gnome in wayland. Gnome launches fine if I do it from tty via "gnome-shell --wayland", and runs properly. Instead, GDM hangs for less then a second before taking me back to the password prompt.

Here is the log from when I attempt to do this: https://pastebin.com/SE8UexXZ

I'm pretty stumped on this one - the log is too dense for me to seek out where its failing; and it seems from my searching that nobody has experienced this exact issue before.

My video card is an Intel Iris Xe card; i915 is enabled for early KMS. GDM is running in wayland mode itself, not xorg. As far as I can tell, this is a gnome issue, not a wayland issue - but I could be wrong.

Let me know if I can supply any more information.

Last edited by ChilledTonic (2021-12-20 18:44:15)

seth · 2021-12-18 15:33:00

Dec 17 23:34:03 daruma gdm-wayland-session[1192]: Gdm: Running wayland session
Dec 17 23:34:03 daruma gdm[633]: Gdm: GdmManager: trying to register new display
Dec 17 23:34:03 daruma gdm[633]: Gdm: GdmCommon: Found session 7 for PID 1192, using
Dec 17 23:34:03 daruma gdm[633]: Gdm: GdmSession: Setting display device: tty3
Dec 17 23:34:03 daruma gdm[633]: Gdm: using ut_user alex
Dec 17 23:34:03 daruma gdm[633]: Gdm: Writing login record
Dec 17 23:34:03 daruma gdm[633]: Gdm: using ut_type USER_PROCESS
Dec 17 23:34:03 daruma gdm[633]: Gdm: using ut_tv time 1639809243
Dec 17 23:34:03 daruma gdm[633]: Gdm: using ut_pid 1192
Dec 17 23:34:03 daruma gdm[633]: Gdm: using ut_host tty3
Dec 17 23:34:03 daruma gdm[633]: Gdm: using ut_line tty3
Dec 17 23:34:03 daruma gdm[633]: Gdm: Writing wtmp session record to /var/log/wtmp
Dec 17 23:34:03 daruma gdm[633]: Gdm: Adding or updating utmp record for login
Dec 17 23:34:03 daruma gdm[633]: Gdm: GdmLocalDisplayFactory: display status changed: 2
Dec 17 23:34:03 daruma gdm-wayland-session[1192]: Gdm: gdm-wayland-session: Session will register itself
Dec 17 23:34:03 daruma gdm-wayland-session[1192]: Gdm: session exited with status 0
Dec 17 23:34:03 daruma gdm-password][1182]: Gdm: GdmSessionWorker: child (pid:1192) done (status:0)
Dec 17 23:34:03 daruma gdm-password][1182]: Gdm: GdmSessionWorker: uninitializing PAM
Dec 17 23:34:03 daruma gdm-password][1182]: pam_unix(gdm-password:session): session closed for user alex
Dec 17 23:34:03 daruma audit[1182]: USER_END pid=1182 uid=0 auid=1000 ses=7 msg='op=PAM:session_close grantors=pam_loginuid,pam_keyinit,pam_systemd_home,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env,pam_gnome_keyring acct="alex" exe="/usr/lib/gdm-session-worker" hostname=daruma addr=? terminal=/dev/tty3 res=success'
Dec 17 23:34:03 daruma audit[1182]: CRED_DISP pid=1182 uid=0 auid=1000 ses=7 msg='op=PAM:setcred grantors=pam_shells,pam_faillock,pam_permit,pam_faillock,pam_gnome_keyring acct="alex" exe="/usr/lib/gdm-session-worker" hostname=daruma addr=? terminal=/dev/tty3 res=success'
Dec 17 23:34:03 daruma gdm-password][1182]: Gdm: GdmSessionWorker: state NONE
Dec 17 23:34:03 daruma gdm-password][1182]: Gdm: Trying script /etc/gdm/PostSession
Dec 17 23:34:03 daruma gdm-password][1182]: Gdm: script /etc/gdm/PostSession not found; skipping
Dec 17 23:34:03 daruma gdm-password][1182]: Gdm: Trying script /etc/gdm/PostSession/Default
Dec 17 23:34:03 daruma gdm-password][1182]: Gdm: Running process: /etc/gdm/PostSession/Default
Dec 17 23:34:03 daruma gdm-password][1182]: Gdm: Gdm: script environment: PATH=/usr/local/bin:/usr/local/sbin:/usr/bin
Dec 17 23:34:03 daruma gdm-password][1182]: Gdm: Gdm: script environment: LOGNAME=alex
Dec 17 23:34:03 daruma gdm-password][1182]: Gdm: Gdm: script environment: USER=alex
Dec 17 23:34:03 daruma gdm-password][1182]: Gdm: Gdm: script environment: USERNAME=alex
Dec 17 23:34:03 daruma gdm-password][1182]: Gdm: Gdm: script environment: PWD=/home/alex
Dec 17 23:34:03 daruma gdm-password][1182]: Gdm: Gdm: script environment: SHELL=/bin/bash
Dec 17 23:34:03 daruma gdm-password][1182]: Gdm: Gdm: script environment: RUNNING_UNDER_GDM=true
Dec 17 23:34:03 daruma gdm-password][1182]: Gdm: Gdm: script environment: GROUP=alex
Dec 17 23:34:03 daruma gdm-password][1182]: Gdm: Gdm: script environment: HOME=/home/alex
Dec 17 23:34:03 daruma gdm-password][1182]: Gdm: Process exit status: 0
Dec 17 23:34:03 daruma gdm[633]: Gdm: GdmSession: Emitting 'session-exited' signal with exit code '0'
Dec 17 23:34:03 daruma gdm[633]: Gdm: GdmManager: session exited with status 0
Dec 17 23:34:03 daruma gdm[633]: Gdm: Writing logout record
Dec 17 23:34:03 daruma gdm[633]: Gdm: using ut_type DEAD_PROCESS
Dec 17 23:34:03 daruma gdm[633]: Gdm: using ut_tv time 1639809243
Dec 17 23:34:03 daruma gdm[633]: Gdm: using ut_pid 1192
Dec 17 23:34:03 daruma gdm[633]: Gdm: using ut_host tty3
Dec 17 23:34:03 daruma gdm[633]: Gdm: using ut_line tty3
Dec 17 23:34:03 daruma gdm[633]: Gdm: Writing wtmp logout record to /var/log/wtmp
Dec 17 23:34:03 daruma gdm[633]: Gdm: Adding or updating utmp record for logout
Dec 17 23:34:03 daruma gdm[633]: Gdm: GdmDisplay: Session never registered, failing
Dec 17 23:34:03 daruma gdm-password][1182]: Gdm: GdmSessionWorker: jumping to VT 1

The session insta-terminates w/o error, but the log looks edited/filtered - can you please post the entire system journal?

ChilledTonic · 2021-12-18 15:43:52

Hi seth,

Sorry; that was a journalctl -f while I attempted to log in - below is a complete output of journalctl -b.

https://pastebin.com/x0aVtGh9

In the boot above, I attempted to login twice via GDM into gnome wayland, then used GDM to start a sway session.

I'm glad at least it's not simply me glossing over an error message. Thanks.

seth · 2021-12-18 17:02:53

There's no additional error, crash etc.
What sticks out is some stray (?) "]" and

Dec 18 08:40:14 daruma gnome-shell[723]: Failed to launch ibus-daemon: Failed to execute child process â€œibus-daemonâ€ (No such file or directory)

what looks like the locale is off.
Not saying that this is the cause, but several gnome components have been locale-sensitive in the past.

localectl; locale; locale -a

ChilledTonic · 2021-12-18 22:26:48

If the first part of your reply is a question and not a statement - no, unless they're being dumped somewhere unusual this error creates no error messages, logs, etc. GDM remains functional even after the failed login; I can use it to launch other DM's no issue.

Here's the outputs of localectl, etc;

localectl: 

System Locale: LANG=en_US.UTF-8
VC Keymap: us
X11 Layout: us

locale:

LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

locale -a:

C
en_US.utf8
POSIX

I tinkered with setting the locale to something else, along with the keymap. Error persists. Tinkering with iBus to see if the issue lays there, but still no meaningful progress

seth · 2021-12-19 07:37:37

Was a statement and "unfortunately" your locale is ok.

Did you try to run a gnome-wayland session w/ a fresh user (maybe there's just an extension that doesn't like wayland now)?

ChilledTonic · 2021-12-19 18:08:34

Hi,

Running a gnome-wayland session with a fresh user worked flawlessly.

What do you mean by extension? I'm not sure what could be in my user folder that could trigger this failure.

Head_on_a_Stick · 2021-12-19 20:39:26

ChilledTonic wrote:

What do you mean by extension?

https://wiki.archlinux.org/title/GNOME#Extensions

ChilledTonic · 2021-12-19 23:51:26

Thanks Head_on_a_Stick, seth;

Looking in /usr/share/gnome-shell/extensions & pacman I had none installed system wide that didn't come with the default gnome & gnome-extra packages; and hadn't installed any from the browser (though that looks neat!)

Anyways, my final suspicion is that this was tied to something I did with trying to scale up GTK and QT, since I've been using a hidpi monitor. Couldn't figure out what configuration file it actually was.

My final solution was nuking my original user and recreating everything. Gnome now works excellent, and looks good too. Thanks for all your help.

However, since I didn't find the actual source of the problem, I'm hesitant to mark this thread solved. What do you think?

Head_on_a_Stick · 2021-12-20 06:49:26

I think [SOLVED] would be appropriate because this thread at least gives some clues as to where to look should a user wish to investigate further before taking the nuclear option. If anybody does find a root cause they can always bump the thread with it.

Arch Linux

#1 2021-12-18 06:49:58

[SOLVED] GDM cannot start Gnome Wayland

#2 2021-12-18 15:33:00

Re: [SOLVED] GDM cannot start Gnome Wayland

#3 2021-12-18 15:43:52

Re: [SOLVED] GDM cannot start Gnome Wayland

#4 2021-12-18 17:02:53

Re: [SOLVED] GDM cannot start Gnome Wayland

#5 2021-12-18 22:26:48

Re: [SOLVED] GDM cannot start Gnome Wayland

#6 2021-12-19 07:37:37

Re: [SOLVED] GDM cannot start Gnome Wayland

#7 2021-12-19 18:08:34

Re: [SOLVED] GDM cannot start Gnome Wayland

#8 2021-12-19 20:39:26

Re: [SOLVED] GDM cannot start Gnome Wayland

#9 2021-12-19 23:51:26

Re: [SOLVED] GDM cannot start Gnome Wayland

#10 2021-12-20 06:49:26

Re: [SOLVED] GDM cannot start Gnome Wayland

Board footer