GNOME under Wayland does not start after updating to Ubuntu 23.10

[Christian Köver-Draxl]

Hello Ubuntu community,

I recently upgraded my system from Ubuntu 23.04 to 23.10 and since then (1 Week) I've had problems starting GNOME under Wayland. Here are the details of my system and the steps already taken:

System information:

Device: MS Surface Pro 5 (Intel Iris Plus Graphics 640)
Ubuntu version: 10/23
Kernel: Linux 6.5.6-surface

Description of the problem:

After updating to Ubuntu 23.10, the GNOME window manager no longer starts under Wayland. X.org, however, works fine. However, in my opinion the quality of the display is lower (screen tearing, flickering mouse, low fps)

Screen resolution and scaling:

I use an external monitor with 1920x1080px and 100% scaling. The built-in screen has a resolution of 2736x1824px and a scaling of 200%. Fractional scaling is enabled.

Steps already taken:

* All available updates have been installed.
* Fractional scaling has been disabled.
* I tried to "force" Wayland by adding "WaylandEnable=True" in the "gdm3 custom.conf".
* Automatic login (without entering a password) has been deactivated.
* I tried reinstalling "libglib2.0-0".
* Various Linux kernels tested: Linux 6.5.6-surface, Linux 6.3.2-surface, Linux 6.5.0-9-generic

[Daniel van Vugt (vanvugt)]

Thanks for the bug report. I can see a SIGSEGV happening in that log so...

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Run these commands:
    journalctl -b0 > journal.txt
    journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.

2. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

[Christian Köver-Draxl (ckoever)]

I managed to "solve" this problem by deleting the complete ~/.config/dconf/user file and reinstall every gnome extension i had installed. Now i can start gnome on wayland, but also had to do again every customisation i had. (Not sure if removing every extension was necessary)

also see in: https://forum.garudalinux.org/t/gnome-45-wayland-session/31493/5

Requested error logs:
1. :
--> wayland working since several boots:
          journalctl -b0 > journal.txt
--> ~10 boots before -> wayland not working:
          journalctl -b-10 > prevjournal.txt
3. (most probably) https://errors.ubuntu.com/oops/45609b38-7049-11ee-b85d-fa163e171f02

(regrettably i dont have the old "faulty" dconf/user file anymore)