Wayland crashing, falling back to X11 in fedora 41 on Dell XPS15

Ask Fedora
, , ,
1

Hi there,

I have upgraded to fedora 41 but since then gnome-shell seems to be crashing wayland and falling back to X11, which is a problem both security-wise and usability-wise.

Here is the log I get from systemd:

https://etherpad.mit.edu/p/f41-wayland-crash-dell-XPS-2024-12-07

Any help would be greatly appreciated! Thanks in advance

2

Does the xps use nvidia gpu?
Which nvidia driver are you using?

The output of inxi -Fzxx will provide people here with useful info needed to help you.

3

Thanks for the reply, here is the result of inxi -Fzxx:

System:
  Kernel: 6.11.10-300.fc41.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.43.1-2.fc41
  Desktop: GNOME v: 47.1 tk: GTK v: 3.24.43 wm: gnome-shell dm: GDM
    Distro: Fedora Linux 41 (Workstation Edition)

Graphics:
  Device-1: Intel Alder Lake-P GT2 [Iris Xe Graphics] vendor: Dell
    driver: i915 v: kernel arch: Gen-12.2 ports: active: eDP-1 empty: DP-1,
    DP-2, DP-3, DP-4, HDMI-A-1 bus-ID: 0000:00:02.0 chip-ID: 8086:46a6
  Device-2: Microdia Integrated_Webcam_HD driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-6:3 chip-ID: 0c45:6732
  Display: x11 server: X.Org v: 21.1.14 with: Xwayland v: 24.1.4
    compositor: gnome-shell driver: X: loaded: modesetting alternate: fbdev,vesa
    dri: iris gpu: i915 display-ID: :1 screens: 1
  Screen-1: 0 s-res: 1920x1200 s-dpi: 96
  Monitor-1: eDP-1 model: LG Display 0x06b3 res: 1920x1200 dpi: 145
    diag: 396mm (15.6")
  API: OpenGL v: 4.6 vendor: intel mesa v: 24.2.8 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: Mesa Intel Graphics (ADL GT2)
    device-ID: 8086:46a6
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
4

That is not the output I expect from inxi -Fzxx for example the memory and BIOS details are missing.

I would not expect you to see crashs in Wayland, given the limited inxi information provided. The Intel GPU drives are usually very good.

Just a thought. You might have RAM issues. Can you install memtest and boot into the memory test and run them. Do they pass?

5

I only pasted the parts I thought were relevant, sorry about that.

I’m running memtest right now, it’s been an hour and no error has been found yet.

Edit : still no error after 3 hours and 6 passes.

6

Still no memory error after 22 passes (I slept over it).

7

Do you have the details of the crash in wayland mode?
I think should be recorded in coredumpctl.

8

I think I pasted it in the link in the first post.

Here are the results of coredumpctl :slight_smile:

Fri 2024-12-06 07:38:01 CET  4841   42   42 SIGSEGV inaccessible /usr/bin/gnome-shell       -
Fri 2024-12-06 18:43:01 CET 11148   42   42 SIGSEGV inaccessible /usr/bin/gnome-shell       -
Fri 2024-12-06 18:43:15 CET 12609 1002 1002 SIGSEGV inaccessible /usr/bin/gnome-software    -
Fri 2024-12-06 19:52:22 CET 21422   42   42 SIGSEGV inaccessible /usr/bin/gnome-shell       -
Sat 2024-12-07 08:45:15 CET 31086   42   42 SIGSEGV inaccessible /usr/bin/gnome-shell       -
Sat 2024-12-07 12:16:50 CET 58596   42   42 SIGSEGV inaccessible /usr/bin/gnome-shell       -
Sat 2024-12-07 12:17:40 CET  1519   42   42 SIGSEGV inaccessible /usr/bin/gnome-shell       -
Sat 2024-12-07 13:10:44 CET  6454   42   42 SIGSEGV inaccessible /usr/bin/gnome-shell       -
Sat 2024-12-07 15:37:08 CET 12125   42   42 SIGSEGV inaccessible /usr/bin/gnome-shell       -
Sat 2024-12-07 17:33:06 CET 15189   42   42 SIGSEGV inaccessible /usr/bin/gnome-shell       -
Sat 2024-12-07 18:22:26 CET 42450   42   42 SIGSEGV inaccessible /usr/bin/gnome-shell       -
Sun 2024-12-08 09:08:26 CET  1523   42   42 SIGSEGV inaccessible /usr/bin/gnome-shell       -
Sun 2024-12-08 10:18:16 CET  6016   42   42 SIGSEGV inaccessible /usr/bin/gnome-shell       -
Sun 2024-12-08 10:20:36 CET  8905   42   42 SIGSEGV inaccessible /usr/bin/gnome-shell       -
Sun 2024-12-08 10:49:01 CET 14120   42   42 SIGSEGV inaccessible /usr/bin/gnome-shell       -
Sun 2024-12-08 10:56:52 CET 15899   42   42 SIGSEGV inaccessible /usr/bin/gnome-shell       -
Sun 2024-12-08 14:37:16 CET 68077   42   42 SIGSEGV inaccessible /usr/bin/gnome-shell       -
Sun 2024-12-08 14:38:21 CET  1513   42   42 SIGSEGV inaccessible /usr/bin/gnome-shell       -
Sun 2024-12-08 18:50:00 CET  4466   42   42 SIGSEGV inaccessible /usr/bin/gnome-shell       -
Sun 2024-12-08 22:28:36 CET 17026   42   42 SIGSEGV inaccessible /usr/bin/gnome-shell       -
Sun 2024-12-08 22:30:02 CET  1524   42   42 SIGSEGV inaccessible /usr/bin/gnome-shell       -
9

You might want to try disabling graphic mode in favor of multi-user and run startx and see if there is a bit more info …

  1. sudo systemctl set-default multi-user
  2. reboot
  3. login
  4. startx
    see what you get …
    (kind of looks like gnome-shell is either missing or corrupt)
10

You need the help of gnome developers to debug the crash.
You have enough data to raise a bug ticket against gnome-shell.
Suggest you fill a bug in the fedora bugzilla.

11

I did that and now I can’t log into my system. I get a “Module is unknown” error message after typing my password, and then I’m back at the login prompt again.

12

Ok,

That’s your root cause … I suspect that the system hibernated/suspended/crahsed during the upgrade …
Can you get in via the previous kernel at grub boot?

13

I tried all the options in grub but none would work, not even the recovery mode.

14

I don’t remember any hiccup during the update though.

15

Try booting a Fedora Live USB … see if you can get to the internal drive and look at the journal on the crashed … journal -D {internal_disk}/var/log/journal … you are looking for a kernel module that is missing/did not load …
You “might” be able to resolve by reinstalling the missing module … otherwise it’s likely a rebuild/reinstall

16

I guess I’m in for a new install. The live system does work correctly, so it is not a hardware problem at least.
Thank you all for your help.