[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

[Daniel van Vugt]

Everyone should also pay attention to the date and time shown in the
output from 'journalctl -b0 | grep MetaSyncRing'. If you have installed
the PPA then we only care about timestamps after the PPA was installed
and after you logged in again to apply the change.

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

Title:
  Input lag or freezes on Nvidia desktops with X11 after logging
  "MetaSyncRing: Sync object is not ready -- were events handled
  properly?"

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Jammy:
  In Progress
Status in mutter source package in Mantic:
  In Progress
Status in mutter source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  Input or the entire screen may freeze at times on systems using the
  Nvidia Xorg driver with GNOME.

  [ Test Plan ]

  0. Set up a desktop with Nvidia driver 545 or 550.
  1. Log into Ubuntu, ensuring it's a Xorg session.
  2. Open a Terminal, resize it vigorously, and type several lines of text.
  3. Run: journalctl -b0 | grep MetaSyncRing
  4. Verify the above command does NOT show "MetaSyncRing" messages such as:

  Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly?
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly?
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly?
  Window manager warning: MetaSyncRing: Too many reboots -- disabling

  [ Where problems could occur ]

  Anywhere in Nvidia (proprietary driver) Xorg sessions since the code
  being modified is only used with that driver.

  [ Original Description ]

  There is a noticeable delay in input while using the native terminal.
  I belive it was caused by a recent software update, as this issue is
  relatively new.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 30 19:57:13 2024
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2024-03-30 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220)
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions