Arch Linux

loflorem

Member

Registered: 2022-11-28

Posts: 9

[SOLVED] GNOME does not start with Wayland.

After the last update in Arch Linux, Gnome doesn't start with Wayland, it starts normally with xorg though.

I already checked the Nvidia driver (I am using the official nvidia package), and just run:

pacman -Syu

From the `journalctl`:

Sep 25 23:11:33 astolfo gnome-shell[946]: Running GNOME Shell (using mutter 42.5) as a Wayland display server
Sep 25 23:11:33 astolfo gnome-shell[946]: Device '/dev/dri/card0' prefers shadow buffer
Sep 25 23:11:33 astolfo gnome-shell[946]: Added device '/dev/dri/card0' (i915) using atomic mode setting.
Sep 25 23:11:33 astolfo gnome-shell[946]: Created gbm renderer for '/dev/dri/card0'
Sep 25 23:11:33 astolfo gnome-shell[946]: Boot VGA GPU /dev/dri/card0 selected as primary
Sep 25 23:11:33 astolfo gnome-shell[946]: Using public X11 display :0, (using :1 for managed services)
Sep 25 23:11:33 astolfo gnome-shell[946]: Using Wayland display name 'wayland-0'
Sep 25 23:11:33 astolfo gnome-shell[946]: JS ERROR: GLib.Error g-invoke-error-quark: Could not locate g_file_new_tmp_async: 'g_file_new_tmp_async': /usr/lib/libgio-2.0.so.0: undefined symbol: g_file_new_tmp_async
                                          _init@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:511:5
                                          @resource:///org/gnome/shell/ui/environment.js:46:66
                                          @resource:///org/gnome/shell/ui/init.js:5:1
Sep 25 23:11:33 astolfo gnome-shell[946]: Execution of main.js threw exception: Module resource:///org/gnome/shell/ui/init.js threw an exception
Sep 25 23:11:33 astolfo gnome-session[907]: gnome-session-binary[907]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Sep 25 23:11:33 astolfo gnome-session-binary[907]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Sep 25 23:11:33 astolfo org.gnome.Shell.desktop[984]: (EE) could not connect to wayland server
Sep 25 23:11:33 astolfo gnome-session-binary[907]: Unrecoverable failure in required component org.gnome.Shell.desktop

GNOME Shell: 43.1
Operating System: Arch Linux                     
Kernel: Linux 6.0.10-arch2-1
Architecture: x86-64
Hardware Vendor: Dell Inc.
Hardware Model: Inspiron 7460
Firmware Version: 1.15.0

However, if I run ...

gnome-shell --wayland

... from a non-interactive session, it runs apparently fine, but it does not load some custom configurations, e.g.: custom short key to open the terminal.

How can I make it start correctly with Wayland, as it was automatically being done before the update?

Thanks in advance for the help .

Last edited by loflorem (2023-07-12 21:00:15)

cfr

Member

From: Cymru

Registered: 2011-11-27

Posts: 7,178

Re: [SOLVED] GNOME does not start with Wayland.

Please edit your post to use [ code ] [ /code ] tags (without the spaces). You also might want to 'report' your post and ask a mod to move it to the applications/DEs forum as this isn't really to do with installation.

---

CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

loflorem

Member

Registered: 2022-11-28

Posts: 9

Re: [SOLVED] GNOME does not start with Wayland.

Thanks! Just did it.

Last edited by loflorem (2022-12-03 01:07:44)

HalosGhost

Forum Fellow

From: Twin Cities, MN

Registered: 2012-06-22

Posts: 2,097

Website

Re: [SOLVED] GNOME does not start with Wayland.

Moved by-request.

All the best,

-HG

---

Code of Conduct

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,696

Re: [SOLVED] GNOME does not start with Wayland.

How can I make it start correctly with Wayland, as it was automatically being done before the update?

"Automatically" by what? DM? Init script?

---

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

loflorem

Member

Registered: 2022-11-28

Posts: 9

Re: [SOLVED] GNOME does not start with Wayland.

By the gdm. Before the update, gnome-shell was automatically being run with Wayland when logged in.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,696

Re: [SOLVED] GNOME does not start with Wayland.

Make sure you don't have the gnome on Xorg session pre-selected.
Then post "lspci -k" because

I already checked the Nvidia driver

doesn't match

Added device '/dev/dri/card0' (i915) using atomic mode setting.

and finally look at https://wiki.archlinux.org/title/NVIDIA#Early_loading resp. https://wiki.archlinux.org/title/Kernel … _KMS_start

In doubt, please post a complete system journal after starting into an X11 session.

---

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

loflorem

Member

Registered: 2022-11-28

Posts: 9

Re: [SOLVED] GNOME does not start with Wayland.

I checked the "/etc/gdm/custom.conf" file and I have the following configuration. Would that be enough to confirm Xorg is not pre-selected?

# 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

Here is the output of "lspci -k"

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 02)
	Subsystem: Dell Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers
	Kernel driver in use: skl_uncore
lspci: Unable to load libkmod resources: error -2
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
	DeviceName:  Onboard IGD
	Subsystem: Dell HD Graphics 620
	Kernel driver in use: i915
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 02)
	Subsystem: Dell Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem
	Kernel driver in use: proc_thermal
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
	Subsystem: Dell Sunrise Point-LP USB 3.0 xHCI Controller
	Kernel driver in use: xhci_hcd
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
	Subsystem: Dell Sunrise Point-LP Thermal subsystem
	Kernel driver in use: intel_pch_thermal
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21)
	Subsystem: Dell Sunrise Point-LP Serial IO I2C Controller
	Kernel driver in use: intel-lpss
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21)
	Subsystem: Dell Sunrise Point-LP Serial IO I2C Controller
	Kernel driver in use: intel-lpss
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
	Subsystem: Dell Sunrise Point-LP CSME HECI
	Kernel driver in use: mei_me
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21)
	Subsystem: Dell Sunrise Point-LP SATA Controller [AHCI mode]
	Kernel driver in use: ahci
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1)
	Subsystem: Dell Sunrise Point-LP PCI Express Root Port
	Kernel driver in use: pcieport
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)
	Subsystem: Dell Sunrise Point-LP PCI Express Root Port
	Kernel driver in use: pcieport
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1)
	Subsystem: Dell Sunrise Point-LP PCI Express Root Port
	Kernel driver in use: pcieport
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
	Subsystem: Dell Sunrise Point-LP LPC Controller
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
	Subsystem: Dell Sunrise Point-LP PMC
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
	Subsystem: Dell Sunrise Point-LP HD Audio
	Kernel driver in use: snd_hda_intel
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
	Subsystem: Dell Sunrise Point-LP SMBus
	Kernel driver in use: i801_smbus
01:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 940MX] (rev a2)
	Subsystem: Dell GM108M [GeForce 940MX]
	Kernel driver in use: nvidia
02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
	Subsystem: Dell QCA6174 802.11ac Wireless Network Adapter
	Kernel driver in use: ath10k_pci
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
	Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
	Kernel driver in use: r8169

I see now the following error:

lspci: Unable to load libkmod resources: error -2

Can that be related? If so, how can I investigate further?

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,696

Re: [SOLVED] GNOME does not start with Wayland.

Would that be enough to confirm Xorg is not pre-selected?

No, this wouldn't be about GDM but your session.
There's only the intel VGA device, but you've a 3D-Controller.

In the meantime, https://wiki.archlinux.org/title/GDM#Wa … DIA_driver has emerged.
If that doesn't help,

please post a complete system journal after starting into an X11 session.

---

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

loflorem

Member

Registered: 2022-11-28

Posts: 9

Re: [SOLVED] GNOME does not start with Wayland.

Please, see here the system journal of latest boot: https://gist.github.com/luisbaldissera/ … a75ffebc72

I tried the following before, but did not yet solve the problem:

Added nvidia related modules:

"/etc/mkinitcipo.conf"

 vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(piix ide_disk reiserfs)
MODULES=(cdc_acm nvidia nvidia_modeset nvidia_uvm nvidia_drm)

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=()

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS=(base)
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS=(base udev autodetect block filesystems)
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev block filesystems)
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS=(base udev block mdadm encrypt filesystems)
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS=(base udev block lvm2 filesystems)
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS=(base udev autodetect keyboard keymap consolefont modconf block encryptmulti lvm2 filesystems fsck)

# COMPRESSION
# Use this to compress the initramfs image. By default, zstd compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="zstd"
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()

And run `mkinitcpio -P`

I also noticed:

Jul 12 19:52:45 astolfo systemd[1507]: Started GNOME Session Manager (session: gnome).
Jul 12 19:52:45 astolfo systemd[1507]: Reached target GNOME Session Manager is ready.
Jul 12 19:52:45 astolfo systemd[1507]: Starting GNOME Shell on Wayland...
Jul 12 19:52:45 astolfo systemd[1507]: Starting GNOME Shell on X11...
Jul 12 19:52:45 astolfo systemd[1507]: org.gnome.Shell@wayland.service: Skipped due to 'exec-condition'.
Jul 12 19:52:45 astolfo systemd[1507]: Condition check resulted in GNOME Shell on Wayland being skipped.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,696

Re: [SOLVED] GNOME does not start with Wayland.

To force-enable Wayland, override these rules by creating the following symlink:

# ln -s /dev/null /etc/udev/rules.d/61-gdm.rules

Did you?

---

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

loflorem

Member

Registered: 2022-11-28

Posts: 9

Re: [SOLVED] GNOME does not start with Wayland.

I didn't before. That solved the issue! Thanks