[SOLVED] gnome is always start with x11, how to use wayland ?

nibazshab · 2022-10-04 03:37:11

i notice the gnome is start with x11 instead of wayland，but I remember it used to be start with wayland , it may be start with x11 a period of time but just today i notice it

this is the gdm config file, it looks don't disabled the wayland

> cat /etc/gdm/custom.conf
# GDM configuration storage

[daemon]
# Uncomment the line below to force the login screen to use Xorg
#WaylandEnable=false

[security]

[xdmcp]

[chooser]

[debug]
# Uncomment the line below to turn on debugging
#Enable=true

> loginctl
SESSION  UID USER   SEAT  TTY
      3 1000 phhbjs seat0 tty2

1 sessions listed.
> loginctl show-session 3 -p Type
Type=x11

here is my GDM log

10月 03 23:02:09 hasee systemd[1]: Starting GNOME Display Manager...
10月 03 23:02:09 hasee systemd[1]: Started GNOME Display Manager.
10月 03 23:02:54 hasee gdm-password][1376]: pam_systemd_home(gdm-password:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
10月 03 23:02:56 hasee gdm-password][1376]: gkr-pam: unable to locate daemon control file
10月 03 23:02:56 hasee gdm-password][1376]: gkr-pam: stashed password to try later in open session
10月 03 23:02:56 hasee gdm-password][1376]: pam_unix(gdm-password:session): session opened for user phhbjs(uid=1000) by (uid=0)
10月 03 23:02:56 hasee gdm-password][1376]: pam_env(gdm-password:session): deprecated reading of user environment enabled
10月 03 23:02:56 hasee gdm-password][1376]: gkr-pam: unlocked login keyring
10月 03 23:03:03 hasee gdm[688]: Gdm: Child process -812 was already dead.
10月 04 00:35:03 hasee systemd[1]: Stopping GNOME Display Manager...
10月 04 00:35:03 hasee gdm[688]: Gdm: Failed to contact accountsservice: Error calling StartServiceByName for org.freedesktop.Accounts: Refusing activation, D-Bus is shutting down
10月 04 00:35:03 hasee systemd[1]: gdm.service: Main process exited, code=exited, status=1/FAILURE
10月 04 00:35:03 hasee systemd[1]: gdm.service: Failed with result 'exit-code'.
10月 04 00:35:03 hasee systemd[1]: Stopped GNOME Display Manager.
10月 04 00:35:03 hasee systemd[1]: gdm.service: Triggering OnFailure= dependencies.
10月 04 00:35:03 hasee systemd[1]: gdm.service: Failed to enqueue OnFailure= job, ignoring: Unit plymouth-quit.service not found.

how should i do can make it back to wayland?

Last edited by nibazshab (2022-10-04 09:37:37)

seth · 2022-10-04 06:20:50

There's no way tellign what's going on from a random GDM log excerpt.
Please post a complete system journal,

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

nibazshab · 2022-10-04 06:26:21

ok, here is complete log: http://0x0.st/oJuz.txt

seth · 2022-10-04 06:45:19

GDM runs on wayland, from there you explicitly start gnome on X11, a gnome wayland session isn't attempted.
Just select gnome/wayland (not xorg) as session type.

nb. https://wiki.archlinux.org/title/PRIME# … figuration

nibazshab · 2022-10-04 07:44:16

thank you, i find it at the log, i don't know what to lead to this .

Condition check resulted in GNOME Shell on Wayland being skipped.

and how can i choose wayland? at https://wiki.archlinux.org/title/PRIME# … figuration, i get this

> glxinfo | grep 'OpenGL renderer'
OpenGL renderer string: Mesa Intel(R) UHD Graphics 630 (CFL GT2)
> DRI_PRIME=pci-0000_01_00_0 __VK_LAYER_NV_optimus=NVIDIA_only __GLX_VENDOR_LIBRARY_NAME=nvidia glxinfo | grep 'OpenGL renderer string'
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  156 (NV-GLX)
  Minor opcode of failed request:  6 ()
  Value in failed request:  0x0
  Serial number of failed request:  96
  Current serial number in output stream:  96

V1del · 2022-10-04 07:52:02

The condition check here will be GDM's udev rule for checking you have modeset and the suspension hooks enabled on the nvidia driver which are described under https://wiki.archlinux.org/title/NVIDIA … de_setting and https://wiki.archlinux.org/title/NVIDIA … er_suspend respectively.

If you don't want to deal with that and at the chances of having subpar experience with the nvidia driver setup then you can also disable the udev rule doing this check: https://wiki.archlinux.org/title/GDM#Wa … DIA_driver

Arch Linux

#1 2022-10-04 03:37:11

[SOLVED] gnome is always start with x11, how to use wayland ?

#2 2022-10-04 06:20:50

Re: [SOLVED] gnome is always start with x11, how to use wayland ?

#3 2022-10-04 06:26:21

Re: [SOLVED] gnome is always start with x11, how to use wayland ?

#4 2022-10-04 06:45:19

Re: [SOLVED] gnome is always start with x11, how to use wayland ?

#5 2022-10-04 07:44:16

Re: [SOLVED] gnome is always start with x11, how to use wayland ?

#6 2022-10-04 07:52:02

Re: [SOLVED] gnome is always start with x11, how to use wayland ?

Board footer