Ubuntu UI screen image freezes randomly during usage after fresh 21.04 install, suspecting Wayland

[Ciro Santilli 六四事件 法轮功]

Also submitted at: https://askubuntu.com/questions/1344736/ubuntu-ui-freezes-randomly-after-fresh-21-04-install-suspecting-wayland

Let me know if there's any way to collect more useful information if there is ever a future crash, or a better place to report.

I was running 20.10 previously with NVIDIA drivers,

Then four days ago, I did a clean 21.04 install without installing the NVIDIA drivers, and since then the UI has frozen three times on my.

I am unable to determine exactly what action triggered the freeze.

The third time, I was just looking at a webpage, I wasn't even touching my mouse at that exact moment, and then it just froze.

I am then unable to see anything move on the screen, including after Ctrl + Alt + Fn, the last image just stays fixed.

The third time was also a bit different.

A few seconds after freezing, it actually went down to a black terminal screen as during boot messages and then I was redirected to the login screen, as if I had been logged out.

I was able to login, my programs were closed, so I was effectively logged out.

Then two Apport windows showed up, and one of them contained several references to Xwayland. Under `/var/crash/_usr_bin_Xwayland.1000.crash` I see one of them:

- `ProcCmdline: /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1000/.mutter-Xwaylandauth.48ZQ40 -listen 4 -listen 5 -displayfd 6 -initfd 7
- `StackTraceAddressSignature` contained mentions of Xwayland and nouveau_dri.so:

  ```
  StacktraceAddressSignature: /usr/bin/Xwayland:6:/usr/lib/x86_64-linux-gnu/libc-2.33.so+864:/usr/bin/Xwayland+13cb40:/usr/bin/Xwayland+14866f:/usr/bin/Xwayland+13b1a7:/usr/lib/x86_64-linux-gnu/libc-2.33.so+864:/usr/lib/x86_64-linux-gnu/libc-2.33.so+749:/usr/lib/x86_64-linux-gnu/libc-2.33.so+123d6:/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0+25d7:/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0+2537:/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0+265f:/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0+2a77:/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2.0.0+31aa:/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so+93b943:/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so+93bc61:/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so+17cc01
  ```

I also checked and I am using Wayland (the default since 21.04 apparently): https://askubuntu.com/questions/904940/how-can-i-tell-if-i-am-running-wayland/1344287#1344287

Hardware:

- Lenovo ThinkPad P51
- NVIDIA Quadro M1200 4GB GDDR5 GPU

Just after the crash, dmesg contained the following possibly interesting lines:

```
[ 9556.450894] nouveau 0000:01:00.0: gr: TRAP ch 3 [00ff8cf000 Xwayland[3831]]
[ 9556.450907] nouveau 0000:01:00.0: gr: GPC0/TPC2/MP trap: global 00000004 [MULTIPLE_WARP_ERRORS] warp 3c000d [OOR_REG]
[ 9556.454264] nouveau 0000:01:00.0: gr: TRAP ch 3 [00ff8cf000 Xwayland[3831]]
[ 9556.454283] nouveau 0000:01:00.0: gr: GPC0/TPC0/MP trap: global 00000004 [MULTIPLE_WARP_ERRORS] warp 3e000d [OOR_REG]
[ 9556.466339] nouveau 0000:01:00.0: gr: TRAP ch 3 [00ff8cf000 Xwayland[3831]]
[ 9556.466351] nouveau 0000:01:00.0: gr: GPC0/TPC3/MP trap: global 00000004 [MULTIPLE_WARP_ERRORS] warp 3e000d [OOR_REG]
[ 9698.230726] nouveau 0000:01:00.0: Xwayland[3831]: failed to idle channel 5 [Xwayland[3831]]
[ 9713.230743] nouveau 0000:01:00.0: Xwayland[3831]: failed to idle channel 5 [Xwayland[3831]]
[ 9713.231918] nouveau 0000:01:00.0: fifo: fault 00 [READ] at 0000000000056000 engine 07 [HOST0] client 06 [HUB/HOST] reason 02 [PTE] on channel 5 [00ff0d9000 Xwayland[3831]]
[ 9713.231930] nouveau 0000:01:00.0: fifo: channel 5: killed
[ 9713.231932] nouveau 0000:01:00.0: fifo: runlist 0: scheduled for recovery
[ 9713.231939] nouveau 0000:01:00.0: fifo: engine 5: scheduled for recovery
[ 9713.231943] nouveau 0000:01:00.0: Xwayland[3831]: channel 5 killed!
[ 9717.642691] nouveau 0000:01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
[ 9717.642702] nouveau 0000:01:00.0: fifo: runlist 0: scheduled for recovery
[ 9717.642709] nouveau 0000:01:00.0: fifo: channel 3: killed
[ 9717.642714] nouveau 0000:01:00.0: fifo: engine 0: scheduled for recovery
[ 9717.643113] nouveau 0000:01:00.0: Xwayland[3831]: channel 3 killed!
[ 9719.351714] apport-gtk[119654]: segfault at 18 ip 00007f337637d194 sp 00007ffd95094dc0 error 4 in libgtk-3.so.0.2404.21[7f3376274000+385000]
[ 9719.351721] Code: c4 08 5b 5d c3 90 f3 0f 1e fa 48 8b 7f 10 48 85 ff 74 0b e9 ce c6 ff ff 66 0f 1f 44 00 00 48 83 ec 08 48 89 d7 e8 0c 36 17 00 <48> 8b 40 18 48 8b 78 10 e8 ef 03 09 00 48 83 c4 08 48 89 c7 e9 a3
[ 9744.187533] rfkill: input handler enabled
[ 9745.940823] rfkill: input handler disabled
[ 9775.737572] rfkill: input handler enabled
[ 9777.953055] rfkill: input handler disabled
```

Related:

- https://askubuntu.com/questions/1334177/ubuntu-21-04-wayland-gimp-black-window GIMP works fine
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 21.04
InstallationDate: Installed on 2021-06-05 (4 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia
Package: gnome-shell 3.38.4-1ubuntu2
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
Tags: hirsute
Uname: Linux 5.11.0-18-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

[Daniel van Vugt (vanvugt)]

Thanks for the bug report. Please run this command to send us additional system info:

  apport-collect 1931387

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

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

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.

[Ciro Santilli 六四事件 法轮功 (cirosantilli)]

apport information

[Ciro Santilli 六四事件 法轮功 (cirosantilli)]

apport information

[Ciro Santilli 六四事件 法轮功 (cirosantilli)]

apport information

[Ciro Santilli 六四事件 法轮功 (cirosantilli)]

apport information

[Ciro Santilli 六四事件 法轮功 (cirosantilli)]

apport information

[Ciro Santilli 六四事件 法轮功 (cirosantilli)]

Ran apport-collect 1931387 now.

1. sends but I see no ID, on https://errors.ubuntu.com/user/ID I see the relevant one: https://errors.ubuntu.com/oops/35d7be60-c90b-11eb-9ab8-fa163e6cac46

[Ciro Santilli 六四事件 法轮功 (cirosantilli)]

* note: I installed the NVIDIA driver after the last crash, so apport-collect may have different data related to that, previously I was on nouveau. Everything else should be the same.

[Daniel van Vugt (vanvugt)]

Thanks, I can see a clear crash from comment #7:

Xwayland: ../nouveau/pushbuf.c:723: nouveau_pushbuf_data: Assertion `kref' failed.

It's being tracked in bug 1497593. But it should not happen again now that you have installed the NVIDIA driver.

[Ciro Santilli 六四事件 法轮功 (cirosantilli)]

Thanks a lot for looking into this Daniel! I'll follow the duplicate.