Only GNOME on Xorg works after recent update

Ask Fedora
, , , ,
1

After a recent update to Fedora, the Wayland session would not work. When I tried to start a Gnome Wayland session by clicking the gear icon on the lock screen than “Gnome” from the dropdown, and logging in, the screen would go blank for a moment than it would bring me back to the lock screen. Only the “Gnome on Xorg” option will work. It is not desirable for me to use X11 because I have my system configured well for Wayland and using X11 breaks things. Also X11 does not support touchpad gestures which I like to use. I am using the integrated Intel Iris Xe Graphics.

I tried to run Gnome on Wayland by pressing Ctrl + Alt + F5 on the lock screen then running:

~$ gnome-shell --display-server --wayland

My output was:

libmutter-Message: 4:01:50.864: Running GNOME Shell (using mutter 46.4) as a Wayland display server
libmutter-Message: 4:01:50.911: Made thread 'KMS thread' realtime scheduled
libmutter-Message: 4:01:50.911: Device '/dev/dri/card1'
libmutter-Message: 4:01:50.925: Added device 'dev/dri/card1' (i915) using atomic mode setting.
libmutter-Message: 4:01:50.926: Created gbm renderer for '/dev/dri/card1'
libmutter-Message: 4:01:50.926: Boot VGA GPU /dev/dri/card1 selected as primary
** Message: 14:01:50.927: Obtained a high priority EGL context
** Message: 14:01:50.928: Obtained a high priority EGL context

(gnome-shell: 5616): libmutter-ERROR **: 14:01:51.073: Failed to start X Wayland: Wrong ownership for directory "/tmp/.X11-unix"
2

Added f40 and removed f34

3

Added workstation and removed server

4

Welcome to Fedora @generic-user

Please test to downgrade the mutter package to see if you can work normal again?

sudo dnf downgrade mutter
1 Like
5

I downgraded it and there was no difference.

6

Did you restart the computer?

7

yes, of course.

8

I updated Fedora via Gnome Software and rebooted, it updated Mutter and Mutter-common back.

9

I think this is normal. If you downgrade a software you have to tell the system not to upgrade again. Otherwise it will.

As you stated that the downgrade not worked for you, I guess it is ok this way, right?

I think it makes sense that you just use software update or dnf. And not both, alias just for gnome only changes use software.

I do regularly check my system with dnf, sometimes after an upgrade “Software” shows still some updates. This is because Software includes flatpak while dnf does not.

To be able to help you, we do need more information about your system, like an inxi -Fzx

10

I did

and here are the relevant results I got:

System:
  Kernel 6.10.6-200.fc40.x86_64 12arch x86_64 12bits 64 12compiler gcc 12v 2.41-37.fc40
  Desktop GNOME 12v 46.4 12Distro Fedora Linux 40 (Workstation Edition)
CPU:
  Info quad core 12model 11th Gen Intel Core i5-11320H 12bits 64 12type MT MCP 12arch Tiger Lake 12rev 2
    cache 12L1 320 KiB 12L2 5 MiB 12L3 8 MiB
  Speed (MHz) 12avg 3702 12high 4500 12min/max 400/4500 12cores 121 4259 122 490 123 4300 124 3536 5 4500 126 4300
    7 4300 128 3934 12bogomips 39936
  Flags avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1 Intel TigerLake-LP GT2 [Iris Xe Graphics] 12vendor Dell 12driver i915 12v kernel 12arch Gen-12.1
    bus-ID 0000:00:02.0
  Display x11 12server X.Org 12v 1.20.14 12with Xwayland 12v 24.1.2 12driver 12X 12loaded intel 12dri iris
    gpu i915 12resolution 1920x1080~60Hz
  API OpenGL 12v 4.6 12vendor intel mesa 12v 24.1.6 12glx-v 1.4 12direct-render yes 12renderer Mesa Intel Xe
    Graphics (TGL GT2)
  API EGL 12Message EGL data requires eglinfo. Check --recommends.
11

Please for next time, post output as pre formated text. You can use the </> button in the editor for that.

12

sorry i forgot about that

13

What shell are you using when doing inxi? All this nr 12 on each line is irritating and makes the whole thing unreadable.

See how mine looks like:

System:
  Kernel: 6.10.5-200.fc40.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.41-37.fc40
  Desktop: GNOME v: 46.4 tk: GTK v: 3.24.43 wm: gnome-shell dm: 1: GDM
    2: LightDM note: stopped Distro: Fedora Linux 40 (Workstation Edition)
Machine:
  Type: Laptop System: CompuLab product: Intense-PC v: 1.x
    serial: <superuser required>
  Mobo: CompuLab model: Intense-PC v: 1.x serial: <superuser required>
    UEFI: Phoenix v: IPC_2.2.400.5 X64 date: 03/15/2018
Battery:
  Device-1: hidpp_battery_0 model: Logitech M585/M590 Multi-Device Mouse
    serial: <filter> charge: 55% (should be ignored) status: discharging
  Device-2: hidpp_battery_1 model: Logitech Wireless Keyboard K230
    serial: <filter> charge: 100% (should be ignored) status: discharging
CPU:
  Info: dual core model: Intel Core i7-3517UE bits: 64 type: MT MCP
    arch: Ivy Bridge rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 4 MiB
  Speed (MHz): avg: 798 min/max: 800/2800 cores: 1: 798 2: 798 3: 798 4: 798
    bogomips: 17559
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel 3rd Gen Core processor Graphics driver: i915 v: kernel
    arch: Gen-7 ports: active: HDMI-A-1 empty: DP-1, DP-2, HDMI-A-2, VGA-1
    bus-ID: 00:02.0 chip-ID: 8086:0166
  Device-2: Sunplus Innovation FHD Camera Microphone
    driver: snd-usb-audio,uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1
    bus-ID: 2-1.6:4 chip-ID: 1bcf:28c4
  Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 24.1.2
    compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa
    dri: crocus gpu: i915 display-ID: 0
  Monitor-1: HDMI-A-1 model: LG (GoldStar) ULTRAWIDE res: 2560x1080 dpi: 97
    diag: 730mm (28.8")
  API: OpenGL v: 4.2 vendor: intel mesa v: 24.1.6 glx-v: 1.4 es-v: 3.0
    direct-render: yes renderer: Mesa Intel HD Graphics 4000 (IVB GT2)
    device-ID: 8086:0166 display-ID: :0.0
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
14

just using bash emulated in kgx (gnome console)

15

oh, the tool wasnt installed yet and yum or dnf installed it and subsequently ran it making the 12s appear

here is my output after I ran the tool again:

System:
  Kernel: 6.10.6-200.fc40.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.41-37.fc40
  Desktop: GNOME v: 46.4 Distro: Fedora Linux 40 (Workstation Edition)
Machine:
  Type: Laptop System: Dell product: Inspiron 15 5510 v: N/A
    serial: <superuser required>
Battery:
  ID-1: BAT0 charge: 47.3 Wh (100.0%) condition: 47.3/54.0 Wh (87.6%)
    volts: 16.8 min: 15.0 model: BYD DELL WV3K81C status: full
  Device-1: hidpp_battery_1 model: Logitech Signature M650 L Mouse
    charge: 80% status: discharging
CPU:
  Info: quad core model: 11th Gen Intel Core i5-11320H bits: 64 type: MT MCP
    arch: Tiger Lake rev: 2 cache: L1: 320 KiB L2: 5 MiB L3: 8 MiB
  Speed (MHz): avg: 3134 high: 4300 min/max: 400/4500 cores: 1: 3966 2: 400
    3: 3173 4: 4300 5: 4300 6: 610 7: 4068 8: 4262 bogomips: 39936
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] vendor: Dell
    driver: i915 v: kernel arch: Gen-12.1 bus-ID: 0000:00:02.0
  Device-2: Realtek Integrated_Webcam_HD driver: uvcvideo type: USB
    bus-ID: 3-6:4
  Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 24.1.2 driver: X:
    loaded: intel dri: iris gpu: i915 resolution: 1920x1080~60Hz
  API: OpenGL v: 4.6 vendor: intel mesa v: 24.1.6 glx-v: 1.4
    direct-render: yes renderer: Mesa Intel Xe Graphics (TGL GT2)
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: Intel Tiger Lake-LP Smart Sound Audio vendor: Dell
    driver: sof-audio-pci-intel-tgl bus-ID: 0000:00:1f.3
  Device-2: Logitech Yeti Orb driver: hid-generic,snd-usb-audio,usbhid
    type: USB bus-ID: 3-4:2
  API: ALSA v: k6.10.6-200.fc40.x86_64 status: kernel-api
  Server-1: JACK v: 1.9.22 status: off
  Server-2: PipeWire v: 1.0.7 status: active
Network:
  Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi v: kernel bus-ID: 0000:00:14.3
  IF: wlp0s20f3 state: up mac: <filter>
Bluetooth:
  Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB
    bus-ID: 3-10:5
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2
    lmp-v: 11
RAID:
  Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd
    v: 0.6 bus-ID: 0000:00:0e.0
Drives:
  Local Storage: total: 238.47 GiB used: 119.45 GiB (50.1%)
  ID-1: /dev/nvme0n1 vendor: A-Data model: IM2P33F3A NVMe 256GB
    size: 238.47 GiB temp: 25.9 C
Partition:
  ID-1: / size: 139.7 GiB used: 119.43 GiB (85.5%) fs: btrfs
    dev: /dev/nvme0n1p5
  ID-2: /boot/efi size: 299.8 MiB used: 19.2 MiB (6.4%) fs: vfat
    dev: /dev/nvme0n1p6
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 65.0 C mobo: 52.0 C
  Fan Speeds (rpm): cpu: 2980
Info:
  Memory: total: 16 GiB note: est. available: 15.36 GiB used: 4.06 GiB (26.4%)
  Processes: 331 Uptime: 1h 15m Init: systemd target: graphical (5)
  Packages: 69 Compilers: clang: 18.1.6 gcc: 14.2.1 Shell: Bash v: 5.2.26
    inxi: 3.3.34
1 Like
16

How does this look like in your case ?

cat /etc/gdm/custom.conf

 # GDM configuration storage

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

p.s.
I am following this article here … describing a similar symptom as you have:

17

i have already tried doing that, it didn’t fix the issue

18

How does the jounalctl look like:

journalctl --no-tail --no-hostname -S "today" -p err

# or more detailed

journalctl --no-tail --no-hostname -S "today" |grep -i gdm

# and
systemctl status gdm
19

I found:

Aug 23 08:16:48 gnome-shell[1429]: Failed to start X Wayland: Directory "/tmp/.X11-unix" is not writable
Aug 23 08:16:49 systemd-coredump[1488]: [🡕] Process 1429 (gnome-shell) of user 42 dumped core.

And then a very long stack trace

20 
~$ systemctl status gdm
● gdm.service - GNOME Display Manager
     Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Fri 2024-08-23 08:20:35 EDT; 1h 52min ago
   Main PID: 1211 (gdm)
      Tasks: 4 (limit: 18817)
     Memory: 6.1M (peak: 26.9M)
        CPU: 144ms
     CGroup: /system.slice/gdm.service
             └─1211 /usr/sbin/gdm

Aug 23 08:20:36 fedora gdm[1211]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Aug 23 08:20:36 fedora gdm[1211]: Gdm: Child process -1299 was already dead.
Aug 23 08:20:36 fedora gdm[1211]: Gdm: GdmDisplay: Session never registered, failing
Aug 23 08:20:36 fedora gdm[1211]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Aug 23 08:20:36 fedora gdm[1211]: Gdm: Child process -1299 was already dead.
Aug 23 08:20:42 fedora gdm-password][1964]: gkr-pam: unable to locate daemon control file
Aug 23 08:20:42 fedora gdm-password][1964]: gkr-pam: stashed password to try later in open session
Aug 23 08:20:43 fedora gdm[1211]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Aug 23 08:20:45 fedora gdm[1211]: Gdm: Child process -1413 was already dead.
Aug 23 08:20:45 fedora gdm[1211]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed