gdm3: "Oh no! Something has gone wrong."

gdm3/custom.conf:

WaylandEnable=false

dmesg -H shows the following crash. The same crash occurs when restarting the gdm service:

[Mar10 22:03] gnome-shell[4837]: unhandled signal 11 code 0x1 at 0x0000000000001422 in libc.so.6[3f83060000+126000]
[ +0.000073] CPU: 2 PID: 4837 Comm: gnome-shell Not tainted 5.19.0-1013-generic #14-Ubuntu
[ +0.000011] Hardware name: SiFive HiFive Unmatched A00 (DT)
[ +0.000007] epc : 0000003f830da1fc ra : 0000003f830dbb20 sp : 0000003fe0515390
[ +0.000008] gp : 0000002ac99b3800 tp : 0000003f7f8c2780 t0 : 0000000000000000
[ +0.000008] t1 : 0000003f83bc99cc t2 : 0000000000000100 s0 : 0000000000001422
[ +0.000007] s1 : 0000002ac99b15a0 a0 : 0000000000001422 a1 : 000000000000003a
[ +0.000008] a2 : 0000002b03dd69a0 a3 : 0000000000000031 a4 : 000000000000003a
[ +0.000007] a5 : 0000000000000002 a6 : 0000000000000004 a7 : 0000003f83189938
[ +0.000007] s2 : 0000003f84149d30 s3 : 000000000000003a s4 : 000000000000003a
[ +0.000007] s5 : 0000002b03dd6980 s6 : 0000003f680082e0 s7 : 0000002b03a61de0
[ +0.000007] s8 : 0000003fe05155c8 s9 : 0000003ffb2d6de1 s10: 0000000000000000
[ +0.000007] s11: 0000000000000000 t3 : 0000003f830dbae0 t4 : 0000000000000000
[ +0.000008] t5 : 0000000000000000 t6 : 0000000000000000
[ +0.000006] status: 8000000200006020 badaddr: 0000000000001422 cause: 000000000000000d
[ +2.735129] gnome-shell[4848]: unhandled signal 11 code 0x1 at 0x0000000000001422 in libc.so.6[3faa460000+126000]
[ +0.000066] CPU: 3 PID: 4848 Comm: gnome-shell Not tainted 5.19.0-1013-generic #14-Ubuntu
[ +0.000012] Hardware name: SiFive HiFive Unmatched A00 (DT)
[ +0.000008] epc : 0000003faa4da1fc ra : 0000003faa4dbb20 sp : 0000003ffae05390
[ +0.000008] gp : 0000002ab17eb800 tp : 0000003fa6d07780 t0 : 0000000000000000
[ +0.000007] t1 : 0000003faafc99cc t2 : 0000000000000100 s0 : 0000000000001422
[ +0.000008] s1 : 0000002ab17e95a0 a0 : 0000000000001422 a1 : 000000000000003a
[ +0.000007] a2 : 0000000000003d80 a3 : 0000002aceab07e0 a4 : 000000000000003a
[ +0.000007] a5 : 0000000000000002 a6 : 0000000000000000 a7 : 0000000000000000
[ +0.000007] s2 : 0000003fab58dd30 s3 : 000000000000003a s4 : 000000000000003a
[ +0.000007] s5 : 0000002aceab07c0 s6 : 0000003f94008400 s7 : 0000002ace731de0
[ +0.000008] s8 : 0000003ffae055c8 s9 : 0000003ffb2d6de1 s10: 0000000000000000
[ +0.000007] s11: 0000000000000000 t3 : 0000003faa4dbae0 t4 : 0000000000000000
[ +0.000007] t5 : 0000000000000000 t6 : 0000000000000000
[ +0.000007] status: 0000000200004020 badaddr: 0000000000001422 cause: 000000000000000d

When trying to start via sddm the logon screen is shown but when entering Gnome the same crash occurs and the "Oh no! Something has gone wrong." message appears.

Heinrich also tried gnome-shell 44rc and had the same problem.

I noticed that we have disabled the mutter build tests from being run on Debian's riscv64.

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. 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.

2. If step 1 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.

I will return from a business trip on Friday and then try to recreate the problem.

The follow up bug is LP #2012068.