Public bug reported:

Package:
  nvidia-driver-535

  System:
  - Ubuntu 22.04 (jammy)
  - Kernel: 6.8.0-100-generic
  - NVIDIA driver: 535.288.01-0ubuntu0.22.04.1
  - xserver-xorg-video-nvidia-535: 535.288.01-0ubuntu0.22.04.1
  - gnome-shell: 42.9-0ubuntu2.3
  - Chrome: 145.0.7632.109-1
  - GPU: NVIDIA GeForce RTX 3090
  - Session: GNOME on Xorg (not Wayland), fractional scaling enabled

Summary:
  I have repeated hard freezes requiring forced reboot. Pattern is consistent: 
Google Meet call under normal usage (multiple participants, active audio), then 
full desktop freeze. In both incidents, logs show repeated nvidia-drm modeset 
ownership errors plus heavy GNOME compositor allocation warnings and display 
re-probe churn.

  Incident windows:
  - Thu 2026-02-19 (boot -5): freeze around 16:17 EST
  - Mon 2026-02-23 (boot -1): freeze around 13:41 EST, reboot at 13:44 EST

  Steps to reproduce (best-effort):
  1. Boot kernel 6.8.0-100, log into GNOME Xorg.
  2. Keep fractional scaling enabled:
     - x11-randr-fractional-scaling
     - scale-monitor-framebuffer
  3. Use multiple displays (I have four, `xrandr | grep "current"` gives a 
total resolution of 16128 x 4938).
  4. Join Google Meet with active audio for an extended period.
  5. Eventually desktop freezes hard and requires reboot.

Expected result:
  System remains responsive.

Actual result:
  Desktop hard-freezes. Input becomes unusable and I must hard reboot.

  Key log evidence:
  - NVIDIA DRM errors (both freeze boots):
    - 2026-02-23T09:37:03 and 13:27:10:
      [nvidia-drm] Failed to grab modeset ownership
    - 2026-02-19T14:27:58:
      [nvidia-drm] Failed to grab modeset ownership
  - GNOME compositor warnings (both freeze boots):
    - "Can't update stage views actor ... needs an allocation"
    - Counts:
  - Xorg/NVIDIA display churn:
    - Repeated NVIDIA(GPU-0) monitor re-probe lines
    - Counts:
      - boot -1: 2809
      - boot -5: 2145
  - Chrome/WebRTC errors also present during incident windows:
    - sdp_offer_answer.cc:500 codec-collision errors
    - Counts:
      - boot -1: 13
      - boot -5: 4

Negative findings:
  - No kernel panic/Oops/BUG/lockup/OOM signatures in incident boots.
  - No NVRM Xid logged.

  Additional context:
  This started in close proximity to updates on 2026-02-18 (kernel 6.8.0-100 
and NVIDIA 535 components updated). Not proof of causation, but timeline may be 
relevant.

Request:
  Please investigate possible regression/instability in nvidia-driver-535 + 
nvidia-drm on this kernel/Xorg path
  (fractional scaling + multi-monitor + Meet/WebRTC load appears to trigger it).

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nvidia-driver-535 535.288.01-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 6.8.0-100.100~22.04.1-generic 6.8.12
Uname: Linux 6.8.0-100-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.10
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 23 14:58:15 2026
InstallationDate: Installed on 2024-08-09 (562 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
SourcePackage: nvidia-graphics-drivers-535
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-535 (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug jammy third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2142512

Title:
  Recurrent hard desktop freeze on GNOME Xorg with nvidia-driver-535
  during Google Meet; repeated nvidia-drm   modeset ownership errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2142512/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to