I have the same issue after last system update and it remains even after clean arch reinstall. Itās driving me crazy for my whole evening and night.
I noticed the same āProcessā¦ gnome-shellā¦ dumped coreā. Last messages in the journal regarding wayland are:
Š¾ŠŗŃ 03 07:37:08 klepoarch systemd[1445]: Started GNOME Session Manager (session: gnome).
Š¾ŠŗŃ 03 07:37:08 klepoarch systemd[1445]: Reached target GNOME Session Manager is ready.
Š¾ŠŗŃ 03 07:37:08 klepoarch systemd[1445]: Starting GNOME Shell on Wayland...
Š¾ŠŗŃ 03 07:37:08 klepoarch systemd[1445]: Starting GNOME Shell on X11...
Š¾ŠŗŃ 03 07:37:08 klepoarch systemd[1445]: org.gnome.Shell@wayland.service: Skipped due to 'exec-condition'.
Š¾ŠŗŃ 03 07:37:08 klepoarch systemd[1445]: Condition check resulted in GNOME Shell on Wayland being skipped.
Š¾ŠŗŃ 03 07:37:08 klepoarch gnome-shell[1588]: Running GNOME Shell (using mutter 44.5) as a X11 window and compositing manager
Š¾ŠŗŃ 03 07:37:08 klepoarch gnome-shell[1588]: Enabling experimental feature 'kms-modifiers'
Also, not sure if itās related, but i noticed that gdm struggles to load āintelā module
Š¾ŠŗŃ 03 07:37:01 klepoarch /usr/lib/gdm-x-session[1044]: (==) Matched intel as autoconfigured driver 0
Š¾ŠŗŃ 03 07:37:01 klepoarch /usr/lib/gdm-x-session[1044]: (==) Matched modesetting as autoconfigured driver 1
Š¾ŠŗŃ 03 07:37:01 klepoarch /usr/lib/gdm-x-session[1044]: (==) Matched fbdev as autoconfigured driver 2
Š¾ŠŗŃ 03 07:37:01 klepoarch /usr/lib/gdm-x-session[1044]: (==) Matched vesa as autoconfigured driver 3
Š¾ŠŗŃ 03 07:37:01 klepoarch /usr/lib/gdm-x-session[1044]: (==) Assigned the driver to the xf86ConfigLayout
Š¾ŠŗŃ 03 07:37:01 klepoarch /usr/lib/gdm-x-session[1044]: (II) LoadModule: "intel"
Š¾ŠŗŃ 03 07:37:01 klepoarch /usr/lib/gdm-x-session[1044]: (WW) Warning, couldn't open module intel
Š¾ŠŗŃ 03 07:37:01 klepoarch /usr/lib/gdm-x-session[1044]: (EE) Failed to load module "intel" (module does not exist, 0)
After all of this madness of fiddling with logs, modules and arch wiki, I tried to launch Wayland manually, without GDM. And it finished almost immediately with dbus connection error:
dbus-daemon[593]: [session uid=0 pid=593] Activating service name='ca.desrt.dconf' requested by ':1.4' (uid=0 pid=594 comm="/usr/lib/gnome-session-binary")
dbus-daemon[593]: [session uid=0 pid=593] Successfully activated service 'ca.desrt.dconf'
A connection to the bus can't be made
[root@klepoarch ~]# gnome-shell-calendar-server[734]: Lost (or failed to acquire) the name org.gnome.Shell.CalendarServer - exiting
(evolution-calendar-factory:785): libedbus-private-WARNING **: 07:24:55.570: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: The connection is closed (g-io-error-quark, 18)
(evolution-addressbook-factory:814): libedbus-private-WARNING **: 07:24:55.575: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: The connection is closed (g-io-error-quark, 18)
Iām getting the same error since the last system update. Iām using NVIDIA drivers, and even when trying with nouveau, I still encounter the same issue. Here is my graphics card:
00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics G7 (rev 07)
Subsystem: Acer Incorporated [ALI] Iris Plus Graphics G7
Kernel driver in use: i915
--
02:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX330] (rev a1)
Subsystem: Acer Incorporated [ALI] GP108M [GeForce MX330]
Kernel driver in use: nvidia
PS: It works fine in X11, but the performance is not smooth.
this looks like optimusā¦ default also if you have Nvidia Drivers installed is that it runs igpu only (intel), a slong as you do not switch nvidia onā¦
org.gnome.Shell.desktop[1101]: Window manager warning: Failed to parse saved session file: Failed to open file ā/var/lib/gdm/.config/mutter/sessions/10e769de2d95dda74f16963078225038900000010650000.msā: No such file or directory
/usr/lib/gdm-x-session[1044]: (EE) Failed to load module "intel" (module does not exist, 0)
Oct 01 04:20:43 siena /usr/lib/gdm-x-session[2112]: (EE) xf86OpenSerial: Cannot open device /dev/input/mouse3
Oct 01 04:20:43 siena /usr/lib/gdm-x-session[2112]: Permission denied.
-
-
Oct 01 04:20:43 siena /usr/lib/gdm-x-session[2112]: (II) mouse3 - failed to create input device '/dev/input/mouse3'.
Oct 01 04:20:43 siena /usr/lib/gdm-x-session[2112]: (EE) libinput: SYNA3297:00 06CB:CD50 Touchpad: Failed to create a device for /dev/input/mouse3
Oct 01 04:20:43 siena /usr/lib/gdm-x-session[2112]: (EE) PreInit returned 2 for "SYNA3297:00 06CB:CD50 Touchpad"
looks strangeā¦ the coredump part itself doe snot say much more infoā¦
Oct 01 04:20:41 siena kernel: gnome-shell[1078]: segfault at 0 ip 0000000000000000 sp 00007ffd597684f8 error 14 likely on CPU 5 (core 1, socket 0)
Oct 01 04:20:41 siena kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
Oct 01 04:20:41 siena systemd[1]: Created slice Slice /system/systemd-coredump.
Only to make sureā¦ xf86-video-intel is not installed i bet?
I just tried downgrading to Mesa 23.1.8 and Mesa 23.1.7 and it doesnāt fix the problem
And when I try to run gnome-shell --wayland it returns: Failed to start X Wayland: wrong ownership for directory "/tmp/.X11-unix"
this indicates there is already a session running from what i seeā¦
And not sure if you are currently running on nouveau or nvidia drivers?
In your log i see both acting, so in case you try to use nouveau it could be Nvidia is not fully removed.
Installing Nvidia would blacklist nouveau in addition.
Check pacman -Qs nvidia and make sure you remove any xorg.conf.d configs related ā¦for nouveau to be usedā¦
You can also run nvidia-inst -n that should do revert to nouveau.
If running on Nvidia use nvidia-inst what will install everything needed and indeed remove unneeded packages if installed. It will also add the DRM modesetting parameter to bootloader. Thats needed for Nvidia and wayland to work, and also for optiomus hybrid to be able to switch Nvidia on.
Iām using the proprietary NVIDIA driver, and it seems like the driver is okay. If I switch to Nouveau, the issue with Wayland still persistsā¦ I tried nvidia-inst, and it doesnāt return anything at all. Iām really lostā¦
The GRUB line is as follows:
linux /boot/vmlinuz-linux root=UUID=2d6f1c7c-e8f1-4473-976a-fb7c3bfd35b0 rw resume=UUID=9831aa74-5864-42df-a427-91c4d0674507 loglevel=3 nowatchdog nvme_load=YES nvidia-drm.modeset=1