Arch Linux

julio.cesar.s93

Member

Registered: 2024-06-30

Posts: 2

Issues using Wayland on Gnome

I tried to enable Wayland on my Arch Linux with GNOME following this tutorial: https://www.osside.net/2023/07/02/how-t … a-rtx-gpu/.

Now I can log in with Wayland, but the resolution is terrible (after login and in GDM), and I can't open most applications. If I select GNOME on Xorg in GDM, the session starts normally with a good resolution and opens applications.

The packages are up to date.

Can someone help me?
Thanks in advance.

julio.cesar.s93

Member

Registered: 2024-06-30

Posts: 2

Re: Issues using Wayland on Gnome

That's what i got in journalctl -b -u gdm:

jun 30 16:16:11 archlinux systemd[1]: Starting GNOME Display Manager...
jun 30 16:16:11 archlinux systemd[1]: Started GNOME Display Manager.
jun 30 16:16:11 archlinux gdm-launch-environment][1381]: pam_systemd(gdm-launch-environment:session): New sd-bus connection (system-bus-pam-systemd-1381) opened.
jun 30 16:16:19 archlinux gdm-password][1834]: pam_systemd_home(gdm-password:auth): New sd-bus connection (system-bus-pam-systemd-home-1834) opened.
jun 30 16:16:25 archlinux gdm-password][1834]: gkr-pam: unable to locate daemon control file
jun 30 16:16:25 archlinux gdm-password][1834]: gkr-pam: stashed password to try later in open session
jun 30 16:16:25 archlinux gdm-password][1834]: pam_unix(gdm-password:session): session opened for user julio(uid=1000) by julio(uid=0)
jun 30 16:16:25 archlinux gdm-password][1834]: pam_systemd(gdm-password:session): New sd-bus connection (system-bus-pam-systemd-1834) opened.
jun 30 16:16:25 archlinux gdm-password][1834]: gkr-pam: unlocked login keyring
jun 30 16:16:25 archlinux gdm[1355]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
jun 30 16:16:29 archlinux gdm[1355]: Gdm: Child process -1400 was already dead.
jun 30 16:16:29 archlinux gdm[1355]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
jun 30 16:17:17 archlinux gdm[1355]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
jun 30 16:17:17 archlinux gdm[1355]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
jun 30 16:17:17 archlinux gdm-launch-environment][3006]: pam_systemd(gdm-launch-environment:session): New sd-bus connection (system-bus-pam-systemd-3006) opened.
jun 30 16:17:20 archlinux gdm-password][3408]: pam_systemd_home(gdm-password:auth): New sd-bus connection (system-bus-pam-systemd-home-3408) opened.
jun 30 16:17:27 archlinux gdm-password][3408]: gkr-pam: unable to locate daemon control file
jun 30 16:17:27 archlinux gdm-password][3408]: gkr-pam: stashed password to try later in open session
jun 30 16:17:27 archlinux gdm-password][3408]: pam_unix(gdm-password:session): session opened for user julio(uid=1000) by julio(uid=0)
jun 30 16:17:27 archlinux gdm-password][3408]: pam_systemd(gdm-password:session): New sd-bus connection (system-bus-pam-systemd-3408) opened.
jun 30 16:17:27 archlinux gdm-password][3408]: gkr-pam: unlocked login keyring
jun 30 16:17:27 archlinux gdm[1355]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
jun 30 16:17:31 archlinux gdm[1355]: Gdm: Child process -3032 was already dead.
jun 30 16:17:31 archlinux gdm[1355]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
jun 30 16:18:54 archlinux gdm[1355]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
jun 30 16:18:54 archlinux gdm[1355]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
jun 30 16:18:54 archlinux gdm-launch-environment][4681]: pam_systemd(gdm-launch-environment:session): New sd-bus connection (system-bus-pam-systemd-4681) opened.
jun 30 16:18:58 archlinux gdm-password][5086]: pam_systemd_home(gdm-password:auth): New sd-bus connection (system-bus-pam-systemd-home-5086) opened.
jun 30 16:19:03 archlinux gdm-password][5086]: gkr-pam: unable to locate daemon control file
jun 30 16:19:03 archlinux gdm-password][5086]: gkr-pam: stashed password to try later in open session
jun 30 16:19:03 archlinux gdm-password][5086]: pam_unix(gdm-password:session): session opened for user julio(uid=1000) by julio(uid=0)
jun 30 16:19:03 archlinux gdm-password][5086]: pam_systemd(gdm-password:session): New sd-bus connection (system-bus-pam-systemd-5086) opened.
jun 30 16:19:03 archlinux gdm-password][5086]: gkr-pam: unlocked login keyring
jun 30 16:19:03 archlinux gdm[1355]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
jun 30 16:19:06 archlinux gdm[1355]: Gdm: Child process -4702 was already dead.
jun 30 16:19:06 archlinux gdm[1355]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
jun 30 16:19:17 archlinux gdm[1355]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
jun 30 16:19:17 archlinux gdm[1355]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
jun 30 16:19:17 archlinux gdm-launch-environment][6159]: pam_systemd(gdm-launch-environment:session): New sd-bus connection (system-bus-pam-systemd-6159) opened.
jun 30 16:19:20 archlinux gdm-password][6559]: pam_systemd_home(gdm-password:auth): New sd-bus connection (system-bus-pam-systemd-home-6559) opened.
jun 30 16:19:24 archlinux gdm-password][6559]: gkr-pam: unable to locate daemon control file
jun 30 16:19:24 archlinux gdm-password][6559]: gkr-pam: stashed password to try later in open session
jun 30 16:19:24 archlinux gdm-password][6559]: pam_unix(gdm-password:session): session opened for user julio(uid=1000) by julio(uid=0)
jun 30 16:19:24 archlinux gdm-password][6559]: pam_systemd(gdm-password:session): New sd-bus connection (system-bus-pam-systemd-6559) opened.
jun 30 16:19:24 archlinux gdm-password][6559]: gkr-pam: unlocked login keyring
jun 30 16:19:24 archlinux gdm[1355]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
jun 30 16:19:28 archlinux gdm[1355]: Gdm: Child process -6188 was already dead.
jun 30 16:19:28 archlinux gdm[1355]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed

seth

Member

Registered: 2012-09-03

Posts: 60,798

Re: Issues using Wayland on Gnome

https://wiki.archlinux.org/title/GDM#Wa … DIA_driver
Please use [code][/code] tags. Edit your post in this regard.
Also don't post randomly filtered excerpts, your problem isn't w/ GDM but the session and from the symptoms, you'll likely end up w/ the simpledrm device.
In doubt post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc