[nvidia] XIO: fatal IO error is killing gnome-shell (black screen, only the X mouse cursor moving)

[Yosha872]

Until yesterday (or tonight) my computer was running fine, but today I could not reach the Gnome desktop after the login window. I shutdown, restarted same thing, then I have open a terminal (CTRL+F1 or F2) tried '$ startx' and get a error message. So I tried 'sudo apt update && upgrade' (Curl recieved a update) then rebooted, then now I can access gnome desktop.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 24.04 LTS
Release: 24.04
Codename: noble

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
Uname: Linux 6.8.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus.0000.01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.183.01 Sun May 12 19:39:15 UTC 2024
 GCC version:
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 5 16:19:55 2024
DistUpgraded: 2024-04-28 15:58:09,572 DEBUG icon theme changed, re-reading
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: This is the first time
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Aspire E5-575G [1025:1094]
   Subsystem: Acer Incorporated [ALI] GM107M [GeForce GTX 950M] [1025:1094]
InstallationDate: Installed on 2023-09-19 (321 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 1d57:fa60 Xenta 2.4G Wireless Mouse
 Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Qualcomm Atheros QCA9377 Bluetooth
 Bus 001 Device 004: ID 04f2:b573 Chicony Electronics Co., Ltd HD WebCam
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
MachineType: Acer Aspire E5-575G
ProcEnviron:
 LANG=fr_FR.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=<set>
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-39-generic root=UUID=7a808742-50c6-42f2-9ff3-d1faeb2d8470 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to noble on 2024-04-28 (99 days ago)
dmi.bios.date: 10/24/2017
dmi.bios.release: 0.0
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.32
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Ironman_SK
dmi.board.vendor: Acer
dmi.board.version: V1.32
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 2.30
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.32:bd10/24/2017:br0.0:efr2.30:svnAcer:pnAspireE5-575G:pvrV1.32:rvnAcer:rnIronman_SK:rvrV1.32:cvnChassisManufacturer:ct10:cvrChassisVersion:skuAspireE5-575G_115F_1.32:
dmi.product.family: KBL
dmi.product.name: Aspire E5-575G
dmi.product.sku: Aspire E5-575G_115F_1.32
dmi.product.version: V1.32
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

[Daniel van Vugt (vanvugt)]

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.

[Yosha872 (yosha)]

1. File attached.
2. I have a crash '_opt_cxoffice_bin_wine-preloader.1000.crash' dated of august 04th 2024. I did ubuntu-bug YOURFILE.crash, but after the Ubuntu window I had no Number given.
3. https://errors.ubuntu.com/user/ID sends me to 'No errors have been reported from this system '

[Yosha872 (yosha)]

File.

[Daniel van Vugt (vanvugt)]

Thanks but I don't see any evidence of crashes in those logs.

What is the content of /var/lib/whoopsie/whoopsie-id on the machine?

[Yosha872 (yosha)]

It is: fd5b837a36a1a181362fc4a3fdb6cfb947bf5c12785193b13ff102c03931de090e84e78a107b8eeb771d2ceb50271a9f351f2fa602bf0721a4f775482a64c00c

[Daniel van Vugt (vanvugt)]

Thanks, there are no shell crashes reported for that machine. And I still don't see any log messages that would explain a black screen.

Please try selecting 'Ubuntu on Wayland' from the login screen and tell us if it is more reliable.

[Yosha872 (yosha)]

Ok if the issue happens again I will do it (currently latests 2 or 3 boots were OK).

Note: perhaps it had somethings related to the Accessibility menu that I had enabled.

[Yosha872 (yosha)]

Today the issue happened again. My computer was off, once powered the only thing I had was a Cross cursor on the screen. No login screen.

After doing CTRL+Alt+DEL nothing happens (just the cursor changed from the X cross to a usual mouse cursor). When doing CTRL+ALT+F1 I get the Ubuntu login screen that says a user is already connected (me, I have autologin enabled), after login in the desktop did appear fine.

So I think the issue has something related with autologin.

[Daniel van Vugt (vanvugt)]

Please check that Wayland has NOT been disabled in /etc/gdm3/custom.conf

And if the login screen issue happens again then from Ctrl+Alt+F4 please run:

  journalctl -b0 > failednow.txt

and attach the resulting text file here.

BTW, the very fact that you can see an X cross on a black screen means you're using X. Please disable auto-login and try selecting 'Ubuntu on Wayland' on the login screen.

[Yosha872 (yosha)]

After a few days, trouble again. I attach '/etc/gdm3/custom.conf' and 'failednow.txt' (note: after CTRL+ALT+F4, when going back to CTRL+ALT+F1 and get the Ubuntu login screen, I have no 'Ubuntu on wayland' option, usually i think it is as the bottom right of the screen).

[Daniel van Vugt (vanvugt)]

> Please disable auto-login and try selecting 'Ubuntu on Wayland' on the login screen.

That means AutomaticLoginEnable=false in /etc/gdm3/custom.conf

[Yosha872 (yosha)]

After a few days fine (with autologin disabled), the issue has just occured again. Log attached.

[Daniel van Vugt (vanvugt)]

Thanks. It looks like the login screen crashed;

août 16 00:34:28 Aspire-E5-575G org.gnome.Shell.desktop[1624]: XIO: fatal IO error 4 (Appel système interrompu) on X server ":0"
août 16 00:34:28 Aspire-E5-575G org.gnome.Shell.desktop[1624]: after 3038 requests (3038 known processed) with 3 events remaining.

but the user session did not crash. So it's possible the death of the login screen shell caused a VT switch and that made you think the user session was lost. So next time it happens please try pressing Ctrl+Alt+F2 to return to your session.

I also noticed this, which will prevent Wayland from being used:

août 16 00:34:23 Aspire-E5-575G systemd[1998]: <email address hidden> - GNOME Shell on Wayland was skipped because of an unmet condition check (ConditionEnvironment=XDG_SESSION_TYPE=wayland).
août 16 00:34:23 Aspire-E5-575G systemd[1998]: Starting <email address hidden> - GNOME Shell on X11...

[Daniel van Vugt (vanvugt)]

Please try adding:

  MUTTER_SYNC=1

to /etc/environment and then reboot. It may give us better crash reports.

[Yosha872 (yosha)]

I added MUTTER_SYNC=1, see:
$ cat /etc/environment
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin"
MUTTER_SYNC=1

The login did work 1 or 2 times until the issue occurs again. CTRL+ALT+F1 to F2 did not help to get the desktop (login did work but the issue was the same). After rebooting, on the login screen I had the icon back at the bottom right (to enable Wayland). Log attached.

Note: perhaps the issue has something related to the fact that I downgrade my screen resolution (1920x1080 => 1364x768). I noticed that after the reboot and login successful, the resolution was back to 1920x1080.

[Daniel van Vugt (vanvugt)]

Thanks. Looks like there's a similar crash:

août 17 23:41:22 Aspire-E5-575G org.gnome.Shell.desktop[1570]: XIO: fatal IO error 11 (Ressource temporairement non disponible) on X server ":0"
août 17 23:41:22 Aspire-E5-575G org.gnome.Shell.desktop[1570]: after 4519 requests (4519 known processed) with 5 events remaining.

but still that machine isn't sending us any shell crash reports. Do you have any relevant files in /var/crash?

It looks like mutter/gnome-shell can catch X IO errors, but doesn't by default?! I guess they're so rare that no developers ever noticed a need.

The error is likely originating from the Nvidia Xorg driver so try using the 'Additional Drivers' app to install the 550 driver instead.

[Daniel van Vugt (vanvugt)]

Sorry I just remembered the Nvidia 550 driver will be hidden from the GUI on most systems.

This should get you most of the way:

  sudo apt purge nvidia-driver-535
  sudo apt install nvidia-driver-550 linux-modules-nvidia-550-generic libnvidia-egl-wayland1

[Yosha872 (yosha)]

> but still that machine isn't sending us any shell crash reports. Do you have any relevant
> files in /var/crash?

No, nothing new.

Computer upgraded to driver v550.