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

This bug is filed against ubiquity, which is an installer, not a terminal. It is unclear what you mean by a "native terminal". Please elaborate.

I am deeply sorry - I must have selected the wrong option in 'ubuntu-bug'.
I am referring to the native terminal installed on ubuntu 22.04, which for
the last few days seems to be lagging due to some latest update. There is
an input delay, noticeable, and the deleting of input text comes with a
delay, too.

sob., 30 mar 2024 o 21:25 Steve Langasek <email address hidden>
napisał(a):

> This bug is filed against ubiquity, which is an installer, not a
> terminal. It is unclear what you mean by a "native terminal". Please
> elaborate.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2059847
>
> Title:
> Input lag in native terminal
>
> Status in ubiquity package in Ubuntu:
> New
>
> Bug 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/ubuntu/+source/ubiquity/+bug/2059847/+subscriptions
>
>

I believe it is related to one of those packages:

There is also a recent discussion here:
https://askubuntu.com/questions/1509058/input-delay-on-terminal-ubuntu-22-04-4

Status changed to 'Confirmed' because the bug affects multiple users.

Seems to be reported upstream at https://gitlab.gnome.org/GNOME/mutter/-/issues/3384.

The upstream bug unfortunately also made it into Ubuntu update packages in https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2054510.

If anyone experiences problems with Wayland then please subscribe to bug 1970389 instead.

I can confirm the issue (I am on ubuntu 22.04 nvidia + x11). gnome-terminal, emacs and similar applications was lagging. Starting an application that updated the screen continuously (such as glxgears) seems to have alleviated the problem.

Downgrading mutter to from 42.9-0ubuntu7 (which I got in the latest upgrade yesterday) to 42.0-3ubuntu2 (release, which was easy to get hold of) seems to have fixed the problem.

So I'm on release 23.10 kernel 6.7.10-060710-generic x11 + nvidia 545 drivers + gnome 45.2
yesterday I upgraded these packages:

2024-03-31 14:25:59 upgrade mutter-common:all 45.2-0ubuntu3 45.2-0ubuntu4
2024-03-31 14:25:59 upgrade gir1.2-mutter-13:amd64 45.2-0ubuntu3 45.2-0ubuntu4
2024-03-31 14:25:59 upgrade libmutter-13-0:amd64 45.2-0ubuntu3 45.2-0ubuntu4
2024-03-31 14:25:59 upgrade mutter-common-bin:amd64 45.2-0ubuntu3 45.2-0ubuntu4
2024-03-31 14:25:59 upgrade libpulse-mainloop-glib0:amd64 1:16.1+dfsg1-2ubuntu4 1:16.1+dfsg1-2ubuntu4.1
2024-03-31 14:25:59 upgrade libpulse0:amd64 1:16.1+dfsg1-2ubuntu4 1:16.1+dfsg1-2ubuntu4.1
2024-03-31 14:25:59 upgrade libxnvctrl0:amd64 510.47.03-0ubuntu1 550.54.14-0ubuntu1
2024-03-31 14:25:59 upgrade nvidia-settings:amd64 510.47.03-0ubuntu1 550.54.14-0ubuntu1
2024-03-31 14:25:59 upgrade snapd:amd64 2.60.4+23.10.1 2.61.3+23.10

and the bug appeared afterward unfortunately I couldn't downgrade to mutter 45.2-0ubuntu3 as it was no longer available through package manager but I downgraded my mutter to 45.0-3ubuntu3 but the issues persists. 45.0-3ubuntu3.

an interesting thing is that the gnome-console is fine but other vte based terminals have severe lag. Does anyone know how to downgrade my mutter to specific version without apt? Do I just have to build it from the git and replace it? (I'm scared of breaking my environment)

I am seeing similar interactivity issues on fully updated 22.04 on a Dell Precision laptop with Nvidia + X11 that started a day or so ago. Most noticeable in the terminal with lag/stuttering and seemingly lost keyboard inputs, but also affecting other apps with stuttering keyboard inputs and sometimes seemingly lost mouse clicks.

I will try downgrading mutter and suggested.....

> [amirsalarsafaei] I downgraded my mutter to 45.0-3ubuntu3 but the issues persists

Mentioning just in case:

You should downgrade all the packages built from mutter's source that you have installed, including libmutter-13-0, mutter-common, mutter-common-bin etc. (Or at least I don't know which one really matters.)

And then you need to log out of your graphical session and log back in, otherwise the previous mutter keeps running.

I'm pointing these out because this suspected mutter change is the only relevant that has a reasonable chance of causing the issues, and multiple people have reported that downgrading fixed the issue for them, yet you report that it didn't for you. At this point we have to consider that you might have made a mistake during downgrading, rather than the bug being somewhere else.

> how to downgrade my mutter to specific version without apt?

I'd download these older packages from packages.ubuntu.com (as you presumably already did with mutter), install them with `dpkg -i`, and put them on "hold" (something like: `echo "mutter hold" | sudo dpkg --set-selections`, and repeat for the other packages).

> an interesting thing is that the gnome-console is fine but other vte based terminals have severe lag.

gnome-console uses gtk4 (and in turn the gtk4 variant of vte), others use gtk3 (and in turn the gtk3 variant of vte). (I'm just stating this as a fact. Don't ask how it triggers the bug to manifest with one but not with the other, I don't know.)

Egmont Koblinger
Thanks for your reply after my comment I found out the issue that there is other binary that contributes and I use hold method to downgrade and now the issue is gone:D. the issue is indeed with the package I just hope they remove the buggy version as soon as possible because it is still is available on my release.

I have similar problem. I'm currently using Ubuntu 22.04.4 LTS (x86_64). Since some days (maybe three?) I see very odd behaviour from programs running in gnome-terminal (or xfce4-terminal if it does not matter, I guess the problem is not the terminal itself but VTE probably or similar? - no problem when using KDE's Konsole for example!). I also have nvidia's driver.

Some programs "only" have very significant input delay, sometimes like 1 sec or so. However interestingly some programs (most notably neomutt) has "infinite" delay, ie, it lags behind exactly one key. For example if I move upwards in the email list, then pressing down still moves up once. And so on, it seems to be true for all keys. Other applications running in terminal seems to "only" have more significant delay, but it's not always consistent. Especially ssh'ing to a remote machine is a very bad experience now, but even on the local host, without any ssh involved just the shell, it's very notable.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.4 LTS
Release: 22.04
Codename: jammy
$ dpkg -l | grep mutter
ii gir1.2-mutter-10:amd64 42.9-0ubuntu7 amd64 GObject introspection data for Mutter
ii libmutter-10-0:amd64 42.9-0ubuntu7 amd64 window manager library from the Mutter window manager
ii mutter-common 42.9-0ubuntu7 all shared files for the Mutter window manager

It appears this is a recurrence of bug 1912246.

Same issue, I've noticed something very strange. If the below lines are commented out, the lag takes a few minutes to kick in (vs immediately when not commented out).
edit /usr/lib/udev/rules.d/61-gdm.rules
comment out the 2 lines:
RUN+="/usr/libexec/gdm-runtime-config set daemon PreferredDisplayServer xorg"
RUN+="/usr/libexec/gdm-runtime-config set daemon WaylandEnable false"
As a side note, Wayland does not well work for me, however, /etc/gdm3/custom.conf forces x11.
i.e.
echo $XDG_SESSION_TYPE
x11

I'm experiencing the same issue. Lag persists across gnome-terminal, gnome-console (kgx), and terminator (all of which are based on VTE). To keep productivity up, I've switched to xterm until the bug is resolved.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.4 LTS
Release: 22.04
Codename: jammy

$ dpkg -l | grep "mutter" | tr -s " " | cut -d " " -f 1-3
ii gir1.2-mutter-10:amd64 42.9-0ubuntu7
ii libmutter-10-0:amd64 42.9-0ubuntu7
ii mutter-common 42.9-0ubuntu7

$ dpkg -l | grep " nvidia-" | tr -s " " | cut -d " " -f 1-3
ii linux-modules-nvidia-535-generic-hwe-22.04 6.5.0-26.26~22.04.1
ii nvidia-compute-utils-535 535.161.07-0ubuntu0.22.04.1
ii nvidia-driver-535 535.161.07-0ubuntu0.22.04.1
ii nvidia-firmware-535-535.161.07 535.161.07-0ubuntu0.22.04.1
ii nvidia-kernel-common-535 535.161.07-0ubuntu0.22.04.1
ii nvidia-kernel-source-535 535.161.07-0ubuntu0.22.04.1
ii nvidia-prime 0.8.17.1
ii nvidia-settings 510.47.03-0ubuntu1
ii nvidia-utils-535 535.161.07-0ubuntu0.22.04.1

I've found a workaround:

I conducted a fresh installation of Ubuntu 22.04.4 and subsequently marked specific packages for holding using the following commands:

$ sudo apt-mark hold gir1.2-mutter-10
$ sudo apt-mark hold libmutter-10-0
$ sudo apt-mark hold mutter-common

Following this, I proceeded to update all packages.
So, I'm currently utilizing version "42.9-0ubuntu5" of the mutter packages, instead of version "42.9-0ubuntu7."

Now, my system is with packages:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.4 LTS
Release: 22.04
Codename: jammy

$ dpkg -l | grep "mutter" | tr -s " " | cut -d " " -f 1-3
hi gir1.2-mutter-10:amd64 42.9-0ubuntu5
hi libmutter-10-0:amd64 42.9-0ubuntu5
hi mutter-common 42.9-0ubuntu5

$ dpkg -l | grep " nvidia-" | tr -s " " | cut -d " " -f 1-3
ii linux-modules-nvidia-535-generic-hwe-22.04 6.5.0-26.26~22.04.1
ii nvidia-compute-utils-535 535.161.07-0ubuntu0.22.04.1
ii nvidia-driver-535 535.161.07-0ubuntu0.22.04.1
ii nvidia-firmware-535-535.161.07 535.161.07-0ubuntu0.22.04.1
ii nvidia-kernel-common-535 535.161.07-0ubuntu0.22.04.1
ii nvidia-kernel-source-535 535.161.07-0ubuntu0.22.04.1
ii nvidia-prime 0.8.17.1
ii nvidia-settings 510.47.03-0ubuntu1
ii nvidia-utils-535 535.161.07-0ubuntu0.22.04.1

No need to reinstall the OS. I've posted a script for downgrading mutter packages for Ubuntu 23.10, 23.04, and 22.04 here:
https://askubuntu.com/a/1509288/96411

I've fetched some older versions (again, I am running 22.04.4) of packages gir1.2-mutter-10 libmutter-10-0 and mutter-common and made them into hold status. After a very ugly and dangerous move, namely editing /var/lib/dpkg/status by hand (to comply the dependencies of gnome-shell which was broken by forcing older versions of packages ... maybe I should have simply installed also older version of gnome-shell, hmm ...), now everything works perfectly again.

Based on mikabytes's answer, I've found another solution that not will not leave apt in a temporary broken state. For Ubuntu 22.04.4:

Download the packages:
$ wget -nc https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu5/+build/26711789/+files/gir1.2-mutter-10_42.9-0ubuntu5_amd64.deb
$ wget -nc https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu5/+build/26711789/+files/libmutter-10-0_42.9-0ubuntu5_amd64.deb
$ wget -nc https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu5/+build/26711789/+files/mutter-common_42.9-0ubuntu5_all.deb

Install the packages:
$ sudo dpkg -i *mutter*.deb

Mark as hold:
$ sudo apt-mark hold gir1.2-mutter-10
$ sudo apt-mark hold libmutter-10-0
$ sudo apt-mark hold mutter-common

@ Daniel van Vugt,

The faulty change has a timestamp of 22 Feb, and the package began to arrive at users probably on 29 Mar. That's a difference of 5 weeks.

I'm not familiar with Ubuntu's internal procedures, I don't know how things work, which component (e.g. building packages, QA, somewhat wider testing in -proposed etc.) took how long, but overall 5 weeks is pretty long.

As I understand from comments in upstream mutter#3384, it's not immediately obvious to you guys what and why exactly goes wrong and how to properly fix all this. It needs investigation first.

This means that my rough guess is that, if everything goes well, it could take maybe 1-2 weeks to develop a fix and another 5 weeks for the regular release prodecure?

Do you have any wild estimate on how many people were affected by the old bug that this update fixed, and how many are affected by the new one? The old one seems to be about software rendering, i.e. when running inside a virtual machine. The new one seems to affect people using an NVidia video card with its proprietary driver. Sounds to me that the new issue probably affects way more people.

I'm wondering: Is there some guideline, best practice, runbook rule etc. describing how to handle such a situation? If so, what does it say?

Wouldn't the right thing be to release new updated packages that revert this change ASAP (like, in a day or two at most, skipping QA and -proposed etc.), and then start to work on the proper fix that fixes both issues at the same time?

The old issue could possibly affect more people because it was for a large commercial partner. Maybe, maybe not. But we don't need to pick and choose which is more important when we can fix everyone's bugs without reverting anything.

I proposed two fixes for this Nvidia bug yesterday:

  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3685
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3684

and I intend to make a PPA available with a fix in the next day or so. That way no one is waiting for the slow process of getting an official update released.

This one really affects my productivity. It's not only terminal it's also slack and some other apps.
Looking forward to @Daniel's PPA.
This also raises a question of testing upstream packages by Ubuntu team, as clearly this wasn't tested in all possible usage cases. I understand not everything can be tested in depth, but a bug of this magnitude needs to be triaged ASAP and not in weeks time frame. It's bad for enterprise users, and it's bad for all the newcomers. We decade old Ubuntu users are kinda used to this situations, not happy but used to it.

This bug was properly triaged one day after it was submitted. On a weekend and public holiday even.

The proposed fix is ready for testing on 22.04:
https://launchpad.net/~vanvugt/+archive/ubuntu/mutter

Unfortunately 23.10 is having issues with flaky test cases so hasn't been published yet.

And no I don't think we ever had much chance of catching this in early testing, because:

* I didn't know some of the code being moved is only used on Nvidia.

* Even after I started testing Nvidia in response to this bug and developing a fix, the problem is very subtle for me. Almost imperceptible other than the log messages. So I would not have noticed it as a bug myself.

* No one on the team who does use Nvidia has mentioned it to me yet.

Test fixes now published for both 22.04 and 23.10:

https://launchpad.net/~vanvugt/+archive/ubuntu/mutter

Amazing work @vanvugt, and thank you for the speedy update, holidays, and all. The fix is working great on my 23.10 system.

Is there any chance we might see a fix for 23.04 as well?

No 23.04 won't get a fix and also shouldn't have the bug, because it reached end-of-life in January;

  https://wiki.ubuntu.com/Releases

That said, I've seen evidence that there might be other ways to trigger similar issues on Nvidia so it's possible other releases could get into a similar state and need the same fix. But for now the only supported releases that definitely contain the bug are 22.04 and 23.10.

Great! Thank you for the information.

Should we remove the ppa after the official packages are released?

I can confirm the lag is gone on my 23.10 system using X11 with nvidia-driver-550 when using the PPA packages.

Thank you!

To get rid of the terminal slowness, what should I do?

> Should we remove the ppa after the official packages are released?

When a higher official version number is available from the archive, your system should automatically start using that. So this particular PPA is harmless to keep active but that's not true for all PPAs.

You should still remove the PPA when you no longer need it because it will raise some annoying flags from bots if you try to report new Ubuntu bugs while using a PPA.

> To get rid of the terminal slowness, what should I do?

sudo add-apt-repository ppa:vanvugt/mutter
sudo apt update
sudo apt upgrade

and reboot should be enough.

Probably not related, but "nvidia-driver-535" was mentioned above in a post. I'm now using ppa:vanvugt/mutter and it seems to be fine, but apt also upgraded nvidia driver from 525 to 535 (maybe not related at all just the new nvidia driver was presented now?). Since then I have hard lock-ups on my system what I've never seen before (no keyboard and mouse works). After forced power-off I see this in the kernel log file:

Apr 5 15:42:57 rygel kernel: [ 3282.354685] NVRM: GPU at PCI:0000:01:00: GPU-78091d7e-2007-c450-19a1-f764cae07b00
Apr 5 15:42:57 rygel kernel: [ 3282.354689] NVRM: Xid (PCI:0000:01:00): 79, pid='<unknown>', name=<unknown>, GPU has fallen off the bus.
Apr 5 15:42:57 rygel kernel: [ 3282.354691] NVRM: GPU 0000:01:00.0: GPU has fallen off the bus.
Apr 5 15:42:57 rygel kernel: [ 3282.354730] NVRM: A GPU crash dump has been created. If possible, please run
Apr 5 15:42:57 rygel kernel: [ 3282.354730] NVRM: nvidia-bug-report.sh as root to collect this data before
Apr 5 15:42:57 rygel kernel: [ 3282.354730] NVRM: the NVIDIA kernel module is unloaded.
Apr 5 15:43:02 rygel kernel: [ 3287.474709] NVRM: Error in service of callback
Apr 5 15:48:05 rygel kernel: [ 3590.071558] Asynchronous wait on fence NVIDIA:nvidia.prime:11cbb timed out (hint:intel_atomic_commit_ready [i915])

I've never seen anything similar before, though I have this very system/install with nvidia's driver since more than a year or so. Since it's probably a totally different issue (though I am not 100% sure), I've reported here: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2060303

It seems now this hard lock up occurs several times per day :( Though the terminal slowness/keyboard input lag/etc is gone, which is good, of course!

Daniel (@vanvugt) Thank you very much for your hard work, out-of-band patch (the ppa!), and speed addressing this extremely subtle, yet annoying bug... much appreciated!

The fix in the PPA is not working for me on Jammy: the lag may be gone, but some rendering is intermittently missed.

Some info:

linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1
nvidia-driver-550 550.67-0ubuntu1.22.04.1

Maybe related in journalctl:

Apr 06 09:47:33 alphasite gnome-shell[2505]: Can't update stage views actor <unnamed>[<MetaWindowGroup>:0x5b2bd9670320] is on because it needs an allocation.
Apr 06 09:47:33 alphasite gnome-shell[2505]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x5b2bdb6eb320] is on because it needs an allocation.
Apr 06 09:47:33 alphasite gnome-shell[2505]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x5b2bdb6eea60] is on because it needs an allocation.

I think something similar was happening on nvidia-driver-535; I upgraded to 550 in an attempt to fix this.

Comment #37 needs a new bug report please. It looks like hybrid GPUs?

Comment #39 should be discussed in bug 2007742. Not here.

I can also confirm the lag is gone on my 22.04 laptop using X11 with nvidia-driver-550 when using the PPA packages.

Thanks!

Here's the debdiff for jammy.

And here's the debdiff for mantic.

Everyone's been discussing bug 2007742 as something that causes only log spam, no other issues. My system is still failing to update the screen after keypresses in gnome-terminal. So maybe those log messages aren't relevant, but it looks like this bug 2059847 is not fully & correctly fixed.

> sudo add-apt-repository ppa:vanvugt/mutter
> sudo apt update
> sudo apt upgrade

I have done the following above but still having lagging issues. Although the lag appears to be much better in the terminal window. But every other window it's quite apparent after a few minutes of using the OS after a reboot.

My Setup
- 2 monitor driven by NVIDIA (`GA104M [GeForce RTX 3070 Mobile / Max-Q]) running driver `server-open::550.54.14`
- 1 laptop screen driven by Intel graphics (`TigerLake-H GT1 [UHD Graphics`)

I have no reverted back to downgrading mutter as per previous posted and lag has subsided however I can't use NVIDIA 550 driver with the old mutter for some reason so I am stuck using intel graphics which doesn't do a great job driving all 3 screens I have. NVIDA not downgrading is a different issue though mover the freezing/lagging still exist even though mutter was fixed.

threadbareobserve, the nvidia driver can be downgraded to 535 without too much work. I'd make sure all the related packages are removed before installing 535.

Might help the developers to know what version of Ubuntu you're running.

I'm running a 22.04 desktop with a 4070 card, and the PPA does *not* fix the problem for me. It removes the lag, but that means the corrupted screen just happens faster. This is a bit intermittent and hard to pin down, but I've particularly noticed this after attempting to paste text into Gnome-Terminal; only the first few pasted characters might be echoed, then it gets into a state where keyboard input is processed but not all of it is echoed.

Are the unresolved issues only occurring with multi-monitor or multi-GPU systems?

Nathan, if you experience corruption then please see bug 1876632.

I've now tested everything I can reasonably test:
  - Nvidia 545
  - Nvidia 550
  - Nvidia-only, single monitor
  - Nvidia-only, dual monitors
  - Nvidia+Intel hybrid, one monitor each

Confirmed the bug occurs in Nvidia-only configurations when the fix is not present. And confirmed the bug does not occur in any configurations when the fix is present.

So I suspect threadbareobserve is experiencing a different issue. Maybe using Wayland instead of X11?

P.S. Nathan, please report your "corrupted screen" in a new bug if it is not already covered by bug 1876632.

Hi Daniel,

No, not multi-GPU. It's an AMD system with no integrated graphics and only one Nvidia card. One monitor plugged in, one TV plugged in to that card via HDMI. But the TV is usually turned off, and disabled in Settings | Displays. Running Xorg, not Wayland.

This doesn't look like bug 1876632; it's not suspend- or VT-switch-related. Maybe I shouldn't have called it "corruption"; what I'm seeing looks like gnome-terminal just... deciding not to render something that it should; characters don't echo. No wild colors or randomized textures or anything like that. Seems like either a problem within gnome-terminal, or GPU command buffers just getting dropped on the floor. Awfully similar to this bug.

Dropped all the `savoury1` PPAs from my system and will keep an eye on this to see if I can find a way to reproduce it.

- Ubuntu 22.04.4 LTS (5.15.0-56-generic)
- I am using X11 when nvidia driver is in use.
    - Checked via observing `XDG_SESSION_TYPE` variable
- I am using on-demand feature for nvidia but switching to performance mode only does not help.

My primary issue is keyboard input lag. It is not as bad as it used to be but it exist.
- I notice it in terminal window and vscode as these are the applications I use mostly
- Sometimes it take a few minutes to appear after a reboot sometimes it appears right away.

Other than the keyboard input lag I notice some lagging when scrolling in Chrome. However this is less apparent.

I can't downgrade nvidia driver, this is likely an unrelated to this bug though.
- Debian package manager just install nvidia 550 regardless of the package I choose.
- `ubuntu-driver` think drivers are already installed if I try to install a specific version.
- `ubuntu-driver` autoinstall/install just install 550

Upstream Gnome 46 made a lot of changes recently to improve performance and input lag in Gnome-Terminal. Those changes are separate from this bug. I don't know whether those changes were backported to Ubuntu 22.04, which ships Gnome 42. That's a question for Daniel or someone else at Canonical.

See https://bxt.rs/blog/just-how-much-faster-are-the-gnome-46-terminals/ and note that the graphs are only talking about lag in the neighborhood of 40-50ms, which is probably just barely perceptible.

I wasn't having any issue until I did a software update about 2 weeks back when this issue starting appearing for others. I am slowly accepting that I need to wipe my system and spend a day setting up my dev environment it is frustrating but this lag is killing my productivity.

See also bug 1777708 for those using multiple keyboards or other input devices.

I'd like to resolve any confusion from the last 10 comments or so. This bug is only for people who have "MetaSyncRing" messages in their system log:

  journalctl -b0 | grep MetaSyncRing

like:

  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

If you don't have any MetaSyncRing messages then please open new bugs.

> Upstream Gnome 46 made a lot of changes recently to improve performance and input lag in Gnome-Terminal. Those changes are separate from this bug.

Exactly.

> I don't know whether those changes were backported to Ubuntu 22.04, which ships Gnome 42.

They weren't, and almost certainly won't be.

> the graphs are only talking about lag in the neighborhood of 40-50ms, which is probably just barely perceptible.

Exactly. If anyone's having latency problems big enough that make them follow this bug and try mutter packages from a PPA, then upgrading the terminal won't fix them.

Running "journalctl -b0 | grep MetaSyncRing", I confirm having this bug, which appeared roughly 2 w-ago after classical update.

This implies lack of responsiveness (up to 2 seconds lags) in terminal as well as in GUI, especially when dragging objects, scrolling, double-clicking and so on.

Configuration:
 * 6.5.0-27-generic #28~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 15 10:51:06 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
 * NVIDIA-SMI 535.161.07

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.

Came here to say that either there is another bug than the "MetaSyncRing" bug or that is not a clear indicator of this bug.

Like others I had upgraded a couple of days ago and had horrible stutter in vte based terminals, other apps were fine. Wayland resolved the issue, but there are huge problems with Wayland in other ways so back to x11 I had to go.

Installed the ppa from Daniel (vanvugt) with the versions of mutter there and all problems have ceased.

But to re-itterate, I never had MetaSyncRing issues in any logs.

Just wanted to say thanks though, a very speedy fix from Daniel on something which was impacting daily usability. Top work.

@gazhay
`
I agree. The input lag has not been fixed I am using X11 I don't even know what `MetaSyncRing` is I don't have any these logs.

I've tried various NVIDIA drivers with no luck.

After a reboot it seems ok but over time it quickly starts to lag much more.

@vanvugt

I can confirm that the ppa solves the input lag on my system:

Ubuntu 22.04.4 LTS, using X11 and NVIDIA Driver Version: 525.147.05

Thank you.

Just want to add that the bug also affects GnuCash and basically makes it unusable. The updated mutter from the PPA fixed it.

Ubuntu 22.04, Xorg and NVidia 535.171.04.

Hello Daniel van Vugt (@vanvugt)!

Would you mind applying your latest patches to your PPA? So we can test the new packages.

- mutter_42.9-0ubuntu8.debdiff
- mutter_45.2-0ubuntu5.debdiff

Thanks,

There are no more "latest patches". The PPA is already the latest as it contains the same fix as 42.9-0ubuntu8 and 45.2-0ubuntu5 will.

@vanvugt

I can confirm that the ppa solves the input lag on my system:

Ubuntu 22.04.4 LTS, using X11/GNOME and NVIDIA Driver Version: 535.147.05

Thank you.

Will this fix come out for 22.04.04 LTS ?

The fix will come as an automatic update in future.

On second thoughts, 46.1 might not make it into the main release so let's patch this in for Noble.

I opened a similar bug and @vanvugt advised me to come here.
I do have the MetaSyncRing messages that pop up in the journalctl command, so my bug indeed relates
I read everything and will try the PPA if need be.

But I'm using a driver that nobody mentioned, which was selected by Dell who assembled the machine and installed the OS.
On Nvidia driver section, I'm using "Set the power ondemand mode by default from oem-fix-gfx-nvidia-ondemandmode". I also have drives 535 and 470 available in the menu, but when I install them, my default setting disappears. I had to fully reinstall the OS to get it back. Nvidia themselves advise on their download page to not necessarily use their proprietary drivers on some Linux distribs, so I stuck with my default driver.

Will the PPA and the mutter downgrade be of use with this default setting ?
Also, installing proprietary pilot from the Software & update menu raised an error, so I aborted the process.

I'm running :

- Ubuntu 22.4.04 LTS
- GNOME 42.9 (latest official update)
- X11
- NVIDIA T400 4GB

Thank you

The Nvidia driver version and Mutter version are unrelated to each other so that doesn't sound like a problem.

https://salsa.debian.org/gnome-team/mutter/-/commit/6cf0e31b3e23556edfbba7669f97935ba118895a

This bug was fixed in the package mutter - 46.0-1ubuntu7

---------------
mutter (46.0-1ubuntu7) noble; urgency=medium

  [ Daniel van Vugt ]
  * debian/control: mutter-common now breaks libmutter back to focal.
    Because we have dropped X11 fractional scaling support for now,
    `org.gnome.mutter.x11.gschema.xml` is no longer shipped and those
    older versions of libmutter will fail to start(LP: #2060423)
  * Add compositor-sync-ring-Allow-the-gpu_fence-to-be-moved.patch
    to fix lag and freezes on the Nvidia Xorg driver (LP: #2059847)

 -- Jeremy Bícha <email address hidden> Tue, 16 Apr 2024 08:46:54 -0400

$apt update .. etc.
$apt search mutter ...
mutter/jammy-updates,now 42.9-0ubuntu7 amd64 [installed,automatic]
  Example window manager using GNOME's window manager library

Seems I have "42.9". How do I get the new 46.0 release on Ubuntu 22.4.04 LTS?

Thanks!

> How do I get the new 46.0 release on Ubuntu 22.4.04 LTS?

You don't. Please use this instead:

https://launchpad.net/~vanvugt/+archive/ubuntu/mutter

Thanks. Things feel better now.

This does appear to fix the issue for me on 22.4.04 LTS

sudo add-apt-repository ppa:vanvugt/mutter
sudo apt update
Then upgrade mutter-common, libmutter-10-0 and gir1.1-mutter-10 (I'm not certain if all 3 of these are required or not).
This will get you version 42.9-0ubuntu7
Reboot !! (required)

Hello Daniel,

Thank you so much for your hard work. I can confirm that, with your fix, my machine is back to its usual snappy self.

OS:

Ubuntu 22.04.4 LTS
Gnome Version: 42.9
X11
Nvidia Driver 535.171.04

Hardware:

Lenovo ThinkPad P15 Gen 1
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile]

Just as a datapoint, the PPA has resolved my lag issues on my Nvidia/xorg setup.

Thanks!

Details:

Ubuntu 22.04.4 LTS

modinfo nvidia
...
version: 535.171.04

I had those `MetaSyncRing: Sync object is not ready -- were events handled properly?` journal entries as well, and did not reappear after PPA upgrade

This does appear to fix the issue for me on 23.10

```
sudo add-apt-repository ppa:vanvugt/mutter
sudo apt update
sudo apt upgrade
sudo shutdown -R now
```

Thanks a lot for this fix!

Thanks - this fix appears to have resolved my lag issues.

OS: Ubuntu 22.04.04 LTS
$XDG_SESSION_TYPE: x11
nVidia: 535.171.04

Mobo/CPU: MSI MAG B550M BAZOOKA / AMD Ryzen 5 5600X
Video card: MSI GeForce GT1030 2GB PCI Express

Mostly this was affecting Gnome terminal for me, but just prior to applying this patch (thanks again!!) I used GnuCash and that lagged too.

I have been experiencing this problem since I updated on 4/22, been away. After the update gnome-term is very slow to echo.

Dpkg:
||/ Name Version Architecture Description
+++-====================-=============-============-===========================>
ii libmutter-10-0:amd64 42.9-0ubuntu7 amd64 window manager library from>
in libmutter-14-0 <none> amd64 (no description available)

Distributor ID: Ubuntu
Description: Ubuntu 22.04.4 LTS
Release: 22.04
Codename: jammy

Nvidia version 535.171.04

The PPA referred to in previous posts as a potential fix seems to have done the trick.

Thanks.

Hey guys... hey Daniel,

Do you guys know when the fix will officially be available for 22.4.04 LTS? Is it expected in the next few days or weeks, or will it take a long time to happen?

Thanks a lot!

OS: Ubuntu 22.04.04 LTS
$XDG_SESSION_TYPE: x11
nVidia: 535.171.04

This fix also solves an annoying flickering issue with IntelliJ Idea

OS: Ubuntu 22.04.04 LTS
$XDG_SESSION_TYPE: x11
nVidia: 535.171.04

Yep, the system has improved significantly. I haven't noticed any laggy behavior.

Thanks, Daniel!

Coincident with this bug, I'm experiencing other bugs, so I think they may be related,

Is there a timeline on this merging to Jammy?

The other bugs:

* emacs is super laggy (500ms - 1000ms delays on typing)

* gnome-terminal of course (500ms - indefinite delays on typing)

* screen flickers and freezes on startup, and resolves after ~10s

* 50% of the time, screen never turns back on after suspend, requiring hard reboot (Ctrl+REISUB)

* I get a random "System problem detected" after every startup

I'd rather catch this fix from the main PPA once it's been tested enough, any timeline on it merging to Jammy?

In Ubuntu 22.04, I just got an update for mutter (42.9-0ubuntu7.1), replacing the one from @Daniel's PPA (42.9-0ubuntu7vv1).

However, the bug resurfaced with this new version.

Regrettably, it seems this update didn't include Daniel van Vugt's proposed fix.

Yep, same issue for me. I have not applied this update yet:

--------------------------------------------------------------------------------------------

From "apt changelog mutter-common" run just seconds ago:

mutter (42.9-0ubuntu7.1) jammy-security; urgency=medium

  * No-change rebuild in the -security pocket.

 -- Marc Deslauriers <email address hidden> Tue, 07 May 2024 17:12:45 -0400

--------------------------------------------------------------------------------------------

From "apt-cache policy mutter-common "
mutter-common:
  Installed: 42.9-0ubuntu7vv1
  Candidate: 42.9-0ubuntu7.1
  Version table:
     42.9-0ubuntu7.1 500
        500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
        500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages
        500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages
 *** 42.9-0ubuntu7vv1 500
        500 https://ppa.launchpadcontent.net/vanvugt/mutter/ubuntu jammy/main amd64 Packages
        500 https://ppa.launchpadcontent.net/vanvugt/mutter/ubuntu jammy/main i386 Packages
        100 /var/lib/dpkg/status
     42.0-3ubuntu2 500
        500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
        500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages

--------------------------------------------------------------------------------------------

Since there was "No Change" in the official version, can Daniel quickly bump the version of his TEMP fix to "42.9-0ubuntu7.1vv1" (or equiv) so it becomes the latest again and we can wait for the next update?

Same for me.

OMG, what an incredibly stupid move by the ubuntu maintainers. I have the same problem as anyone else who has been forcefully downgraded and I tried to solve it by reverting to Daniel's version. However, this "downgrade" would uninstall a lot of GNOME related packages (including `gnome-shell`):

```
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libnvidia-cfg1-525 libnvidia-common-525 libnvidia-compute-525 libnvidia-compute-525:i386 libnvidia-decode-525 libnvidia-decode-525:i386 libnvidia-egl-wayland1
  libnvidia-encode-525 libnvidia-encode-525:i386 libnvidia-extra-525 libnvidia-fbc1-525 libnvidia-fbc1-525:i386 libnvidia-gl-525 libnvidia-gl-525:i386
  nvidia-compute-utils-525 nvidia-dkms-525 nvidia-driver-525 nvidia-firmware-535-535.161.07 nvidia-utils-525 xserver-xorg-video-nvidia-525
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  notification-daemon policykit-1-gnome python3-update-manager update-manager update-manager-core
The following packages will be REMOVED:
  chrome-gnome-shell gdm3 gir1.2-mutter-10 gnome-control-center gnome-remote-desktop gnome-shell gnome-shell-extension-appindicator gnome-shell-extension-desktop-icons-ng
  gnome-shell-extension-prefs gnome-shell-extension-ubuntu-dock gnome-shell-extensions libmutter-10-0 ubuntu-desktop ubuntu-desktop-minimal ubuntu-session
The following NEW packages will be installed:
  notification-daemon policykit-1-gnome
The following packages will be upgraded:
  python3-update-manager update-manager update-manager-core
The following packages will be DOWNGRADED:
  mutter-common
3 upgraded, 2 newly installed, 1 downgraded, 15 to remove and 13 not upgraded.
Need to get 1.246 kB of archives.
After this operation, 15,0 MB disk space will be freed.
Do you want to continue? [Y/n]
```

Seems like we're stuck and have to wait for a proper fix ... again! I've been using Ubuntu for about 20 years and have never been so close to switching to a different distribution. The way they handle this bug is absolutely ridiculous.

Hello Marek, or anyone else affected,

Accepted mutter into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu8 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Marek, or anyone else affected,

Accepted mutter into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu5 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-mantic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Testing of Latest Proposed mutter-common. Installed and rebooted. Unfortunately, the stutters in terminal have RETURNED.

$ sudo apt-cache policy mutter-common
mutter-common:
  Installed: 42.9-0ubuntu8
  Candidate: 42.9-0ubuntu8
  Version table:
 *** 42.9-0ubuntu8 400
        400 http://us.archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
        400 http://us.archive.ubuntu.com/ubuntu jammy-proposed/main i386 Packages
        100 /var/lib/dpkg/status
     42.9-0ubuntu7.1 500
        500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
        500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages
        500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages
     42.9-0ubuntu7vv1 500
        500 https://ppa.launchpadcontent.net/vanvugt/mutter/ubuntu jammy/main amd64 Packages
        500 https://ppa.launchpadcontent.net/vanvugt/mutter/ubuntu jammy/main i386 Packages
     42.0-3ubuntu2 500
        500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
        500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages

Once again, showing MetaSyncRing objects in the journal:

$ sudo journalctl -b0 | grep MetaSyncRing
May 10 07:27:28 desktop org.gnome.Shell.desktop[2876]: Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly?
May 10 07:27:40 desktop gnome-shell[3681]: Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly?
May 10 07:27:40 desktop gnome-shell[3681]: Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly?
May 10 07:27:40 desktop gnome-shell[3681]: Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly?
May 10 07:27:40 desktop gnome-shell[3681]: Window manager warning: MetaSyncRing: Too many reboots -- disabling

All autopkgtests for the newly accepted mutter (45.2-0ubuntu5) for mantic have finished running.
The following regressions have been reported in tests triggered by the package:

gdm3/unknown (armhf)
mutter/45.2-0ubuntu5 (arm64, s390x)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/mantic/update_excuses.html#mutter

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Also testing the proposed fix, and it did not solve the issue for me after installing and rebooting. I am still getting significant lag in the terminal. The recommendation from comment #36 had been working perfectly until this morning.

$ sudo apt-cache policy mutter-common
mutter-common:
  Installed: 42.9-0ubuntu8
  Candidate: 42.9-0ubuntu8
  Version table:
 *** 42.9-0ubuntu8 100
        100 /var/lib/dpkg/status
     42.9-0ubuntu7.1 500
        500 http://ca.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
        500 http://ca.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages
        500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages
     42.9-0ubuntu7vv1 500
        500 https://ppa.launchpadcontent.net/vanvugt/mutter/ubuntu jammy/main amd64 Packages
        500 https://ppa.launchpadcontent.net/vanvugt/mutter/ubuntu jammy/main i386 Packages
     42.0-3ubuntu2 500
        500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
        500 http://ca.archive.ubuntu.com/ubuntu jammy/main i386 Packages

I tested the proposed fix for jammy and it did solve the issue for me. I upgraded both the libmutter-10-0 and mutter package (which also installs the updated dependencies listed below) and then rebooted. The libmutter-10-0 dependency appears to be necessary to remove the lag issues but the new version is not marked as required when installing mutter/mutter-common. Therefore, only upgrading mutter does not resolve the issue.

My policies:

mutter:
  Installed: 42.9-0ubuntu8
  Candidate: 42.9-0ubuntu8
  Version table:
 *** 42.9-0ubuntu8 100
        100 /var/lib/dpkg/status
     42.9-0ubuntu7.1 500
        500 http://at.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages
        500 http://security.ubuntu.com/ubuntu jammy-security/universe amd64 Packages
     42.9-0ubuntu7vv1 500
        500 https://ppa.launchpadcontent.net/vanvugt/mutter/ubuntu jammy/main amd64 Packages
     42.0-3ubuntu2 500
        500 http://at.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages

libmutter-10-0:
  Installed: 42.9-0ubuntu8
  Candidate: 42.9-0ubuntu8
  Version table:
 *** 42.9-0ubuntu8 100
        100 /var/lib/dpkg/status
     42.9-0ubuntu7.1 500
        500 http://at.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
     42.9-0ubuntu7vv1 500
        500 https://ppa.launchpadcontent.net/vanvugt/mutter/ubuntu jammy/main amd64 Packages
     42.0-3ubuntu2 500
        500 http://at.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

gir1.2-mutter-10:
  Installed: 42.9-0ubuntu8
  Candidate: 42.9-0ubuntu8
  Version table:
 *** 42.9-0ubuntu8 100
        100 /var/lib/dpkg/status
     42.9-0ubuntu7.1 500
        500 http://at.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
     42.9-0ubuntu7vv1 500
        500 https://ppa.launchpadcontent.net/vanvugt/mutter/ubuntu jammy/main amd64 Packages
     42.0-3ubuntu2 500
        500 http://at.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

mutter-common:
  Installed: 42.9-0ubuntu8
  Candidate: 42.9-0ubuntu8
  Version table:
 *** 42.9-0ubuntu8 100
        100 /var/lib/dpkg/status
     42.9-0ubuntu7.1 500
        500 http://at.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
        500 http://at.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages
        500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages
     42.9-0ubuntu7vv1 500
        500 https://ppa.launchpadcontent.net/vanvugt/mutter/ubuntu jammy/main amd64 Packages
        500 https://ppa.launchpadcontent.net/vanvugt/mutter/ubuntu jammy/main i386 Packages
     42.0-3ubuntu2 500
        500 http://at.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
        500 http://at.archive.ubuntu.com/ubuntu jammy/main i386 Packages

Following mgruberb's advice of also installing libmutter-10-0 fixed the issue for me as well. Thanks all!

Hi all, I'm new here and never done this before but I've done the necessary to use the proposed packages because this bug is really really annoying, making some stuff unusable.

I'm at the last step, when I should just upgrade my packages from proposed, but I'm freaking out because upgrading `mutter` and `libmutter-10-0` would apparently remove some unrelated (from my point of view) packages I use daily.

Here is the output of my upgrade simulation:

---
$> sudo apt-get install mutter/jammy-proposed libmutter-10-0/jammy-proposed -s

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Selected version '42.9-0ubuntu8' (Ubuntu:22.04/jammy-proposed [amd64]) for 'mutter'
Selected version '42.9-0ubuntu8' (Ubuntu:22.04/jammy-proposed [all]) for 'mutter-common' because of 'mutter'
Selected version '42.9-0ubuntu8' (Ubuntu:22.04/jammy-proposed [amd64]) for 'libmutter-10-0'
The following packages were automatically installed and are no longer required:
  gir1.2-accountsservice-1.0 gir1.2-adw-1 gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-3.0 gir1.2-gpaste-1.0 gir1.2-graphene-1.0 gir1.2-gtk-4.0 gir1.2-gweather-3.0
  gir1.2-json-1.0 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-upowerglib-1.0 gnome-bluetooth-3-common gnome-shell-common gnome-shell-pomodoro-data gstreamer1.0-pipewire libgnome-bluetooth-3.0-13 switcheroo-control
  xwayland
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  mutter-common notification-daemon policykit-1-gnome python3-update-manager update-manager update-manager-core
The following packages will be REMOVED:
  chrome-gnome-shell gdm3 gir1.2-mutter-10 gnome-shell gnome-shell-extension-appindicator gnome-shell-extension-desktop-icons-ng gnome-shell-extension-gpaste gnome-shell-extension-ubuntu-dock
  gnome-shell-extensions-gpaste gnome-shell-pomodoro ubuntu-desktop ubuntu-desktop-minimal ubuntu-session
The following NEW packages will be installed:
  notification-daemon policykit-1-gnome
The following packages will be upgraded:
  libmutter-10-0 mutter mutter-common python3-update-manager update-manager update-manager-core
6 upgraded, 2 newly installed, 13 to remove and 0 not upgraded.
Remv chrome-gnome-shell [10.1-5]
Remv ubuntu-desktop [1.481.1]
Remv ubuntu-desktop-minimal [1.481.1]
Remv gdm3 [42.0-1ubuntu7.22.04.4]
Inst policykit-1-gnome (0.105-7ubuntu3 Ubuntu:22.04/jammy [amd64])
Inst notification-daemon (3.20.0-4build1 Ubuntu:22.04/jammy [amd64])
Remv gnome-shell-extension-ubuntu-dock [72~ubuntu5.22.04.2.1]
Remv gnome-shell-extension-desktop-icons-ng [43-2ubuntu1]
Remv gnome-shell [42.9-0ubuntu2.1] [gnome-shell-extension-gpaste:amd64 gnome-shell-pomodoro:amd64 gnome-shell-extension-appindicator:amd64 ubuntu-session:amd64 ]
Remv gir1.2-mutter-10 [42.9-0ubuntu7.1] [gnome-shell-extension-gpaste:amd64 gnome-shell-pomodoro:amd64 gnome-shell-extension-appindicator:amd64 ubuntu-session:amd64 ]
Remv gnome-shell-extension-appindicator [42-2~fakesync1] [gnome-shell-extension-gpaste:amd64 gnome-shell-pomodoro:amd64 ubuntu-session:amd64 ]
Remv gnome-shell-extensions-gpaste [3.42.6-1] [gnome-shell-extension-gpaste:amd64 gnom...

Hello JK (m0d), same sad behavior.
Why i can't just downgrade 1 package via...
`sudo apt install libmutter-10-0=42.9-0ubuntu7vv1`
Many gnome packages will be removed after this downgrade.

May be someone have another solution for do this safely?
Ubuntu 22.04.4 now is unusable for my work purposes..

How on Earth did this get SNAFU'd again 😅

My goodness.
First time I've experienced broken --> fixed --> broken (in exact manner as pre-fix) of a STANDARD package from OFFICIAL sources.

This is nvidia-driver tier boobery.

Here's the "fix" snippet folks:
sudo apt install -y --allow-downgrades \
gir1.2-mutter-10=42.9-0ubuntu7vv1 \
mutter-common=42.9-0ubuntu7vv1 \
libmutter-10-0=42.9-0ubuntu7vv1;

To keep the versions pinned,
I have a `/etc/apt/preferences.d/mutter-bug-pin-1001`:

Package: gir1.2-mutter-10
Pin: version 42.9-0ubuntu7vv1
Pin-Priority: 1001

Package: mutter-common
Pin: version 42.9-0ubuntu7vv1
Pin-Priority: 1001

Package: libmutter-10-0
Pin: version 42.9-0ubuntu7vv1
Pin-Priority: 1001

Thanks Deku.

With just a very quick test (applied then rebooted), the snippet posted above seems to be working for me with Ubuntu 22.04.4 LTS.

I had to add the apt option --allow-downgrades

Mark

Don't know why but I can't make this work.

---
$> sudo apt install -y -s --allow-downgrades gir1.2-mutter-10=42.9-0ubuntu7vv1 mutter-common=42.9-0ubuntu7vv1 libmutter-10-0=42.9-0ubuntu7vv1

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package gir1.2-mutter-10 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package libmutter-10-0 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package mutter-common is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Version '42.9-0ubuntu7vv1' for 'gir1.2-mutter-10' was not found
E: Version '42.9-0ubuntu7vv1' for 'mutter-common' was not found
E: Version '42.9-0ubuntu7vv1' for 'libmutter-10-0' was not found
---

And question: if I downgrade these packages, will it still be automatically upgraded when the fix is released, or will it stay pinned to this particular version ?

> First time I've experienced broken --> fixed --> broken (in exact manner
> as pre-fix) of a STANDARD package from OFFICIAL sources.

That is not an accurate description of the events here. This was an issue
introduced in mutter 45.2-0ubuntu4 and 42.9-0ubuntu7. The only subsequent
versions of this package in official sources are 42.9-0ubuntu7.1 (which was
just published by the security team), and 45.2-0ubuntu5 nd 42.9-0ubuntu8
which are the fixes that have just been accepted into the -proposed pocket.

A fix in a test ppa is not an "official" source.

Still an issue. Amazed the fix hasn't landed on 22.04 yet. Anyone we can bribe to get this addressed sooner?

> That is not an accurate description of the events here. This was an issue
> introduced in mutter 45.2-0ubuntu4 and 42.9-0ubuntu7. The only subsequent
> versions of this package in official sources are 42.9-0ubuntu7.1 (which was
> just published by the security team), and 45.2-0ubuntu5 nd 42.9-0ubuntu8
> which are the fixes that have just been accepted into the -proposed pocket.

> A fix in a test ppa is not an "official" source.

Ah, true true; thanks for the correction vorlon.

> Here's the "fix" snippet folks:

Thanks a lot @Deku King! This bug is driving me crazy, since it affects all parts of the GUI and makes my PC almost unusable. Except for gaming, which is not affected. Hmm... maybe I should check if I accidentally booted the wrong OS...

> The only subsequent versions of this package in official sources are 42.9-0ubuntu7.1 (which was
just published by the security team)

And that "security" release fixed what exactly?

Let's see: https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu7.1

Ah, nothing, just a rebuild.

I had to downgrade the mutter packages on Ubuntu 22.04.4 today as the lag returned after the latest update. Did almost the same as Deku King although opted to deprioritize the 42.9-0ubuntu7.1 packages instead of locking the older ones.

Package: gir1.2-mutter-10
Pin: version 42.9-0ubuntu7.1
Pin-Priority: 1

Package: libmutter-10-0
Pin: version 42.9-0ubuntu7.1
Pin-Priority: 1

Package: mutter
Pin: version 42.9-0ubuntu7.1
Pin-Priority: 1

Package: mutter-common
Pin: version 42.9-0ubuntu7.1
Pin-Priority: 1

I have not tested proposed yet but will do that shortly.

Installing the packages below seems to work for me (on Ubuntu 22.04.4, X11, nvidia-550.78). No terminal lag is observed.

mutter=42.9-0ubuntu8
mutter-common=42.9-0ubuntu8
libmutter-10-0=42.9-0ubuntu8
gir1.2-mutter-10=42.9-0ubuntu8

This is awful. 22.04 is back to being treacle again. Halp!

Using these packages seems to work: https://bugs.launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu8

Ubuntu LTS 22.04.4

I ran Deku's script, from message 102 above:

sudo apt install -y --allow-downgrades \
gir1.2-mutter-10=42.9-0ubuntu7vv1 \
mutter-common=42.9-0ubuntu7vv1 \
libmutter-10-0=42.9-0ubuntu7vv1;

That cleared things up, no lag / MetaSyncRing errors, but Ubuntu now wants to re-upgrade the packages back to 42.9-0ubuntu7.1

I tried installing the 0ubuntu8 packages from Tais in message 111, but apt couldn't find them

@mark You need to enable the proposed archive to get the packages I mentioned. See https://wiki.ubuntu.com/Testing/EnableProposed. I highly recommend using the "selective" approach.

I've been fighting with this bug for about 2 months now.
I've tried the new mutter fixes but nothing seemed to work.

The only thing that has worked for me is listed below
1. Reinstall Ubuntu LTS 22.04.4 without any upgrade or just don't connect it to the internet.
2. After ubuntu install first thing you do is put a hold the mutter packages
   ```
   sudo dpkg -i *mutter*.deb
   echo libmutter-$package hold | sudo dpkg --set-selections
   ```
3. Upgrade NVIDIA to `nvidia-driver-535` proprietary.

Nobody seems to care but as I stated several times in this thread, for some people (including me) upgrading these packages will remove some other packages that apparently need the former ones. This is not an option.

See the output of `sudo apt-get install mutter/jammy-proposed libmutter-10-0/jammy-proposed -s` on my computer in one of my previous comments (#100) for details.

I would really appreciate somebody to give me a hand here, I don't have that much xp with apt specifics so it might be obvious to some of you.

I use ubuntu as my main and only driver for my everyday dev work and it is barely usable since one or two months now. I will have to change distro if I don't find a quick solution as it is impacting vscode intelliJ, terminal, browser responsivness and more.

I'm just running glxgears all the time :(

Antoine (@toniopelo), it is the same as for me. I do not have Wayland installed (mutter) - only X11 - and an upgrade of just mutter-common and libmutter-10-0 from the Jammy Proposed PPA does NOT fix the issue. As soon as I try to install mutter (which I don't need or want), apt proposes making massive deletions/changes to my install. This is NOT an option either.

Whatever Daniel van Vugt (vanvugt) created for dependencies on his "temp" PPA worked and did not require the massive install changes and fixed the problem. The Jammy Proposed PPA has different dependencies and makes it a non-option.

I add my request to please fix this, OR, create another temp PPA with the same dependencies and a version that gets ahead in priority of the current (not proposed) jammy PPA.

Here is a temporary solution that I am using in a few Ubuntu 22.04 installations that I currently manage.

1) Open a TTY (Ctrl + Alt + F3)

2) Remove mutter-common: sudo apt remove mutter-common gir1.2-mutter-10 libmutter-10-0

This will remove a lot of other important packages. So basically you will end up with a non-functional desktop. But TTY will thankfully still work.

3) Add the test-fix ppa (if you haven't already): sudo add-apt-repository ppa:vanvugt/mutter

4) Install specific versions of the affected packages:
sudo apt install --allow-downgrades gir1.2-mutter-10=42.9-0ubuntu7vv1 mutter-common=42.9-0ubuntu7vv1 libmutter-10-0=42.9-0ubuntu7vv1

5) Pin these packages:
sudo apt-mark hold mutter gir1.2-mutter-10 libmutter-10-0 libmutter-10-dev libmutter-test-10 mutter-10-tests mutter-common

6) Then install all the packages that went missing:
sudo apt install ubuntu-desktop^

7) Update packages and then reboot:
sudo apt update && sudo apt upgrade

Let me know if this works. Thanks!

This appears to fix the issue for me on mantic (23.10) using the mantic-proposed repo.

45.2-0ubuntu5 - for: gir1.2-mutter-13 libmutter-13-0 mutter-common mutter

I did have to purge the ppa to get get to install. Maybe I did something to get those vv version pinned.

I confirmed that I don't get the strange delay (the display persisted up to 1-2s after I would hit a key sometimes).

I also confirmed that I don't see MetaSyncRing messages on this boot. Oh, and I rebooted after installing the packages.

Sorry for the delay and confusion. I was away for most of the last two weeks.

It looks like a few things happened:

1. The security team inserted an update which took precedence over the PPA. This is normal and correct. Just unlucky timing that I was away at the same time AND the debdiff in comment #42 didn't get attention for a month (also because much of the team are travelling).

2. Some people had packages automatically removed. I'm not sure what caused this, it might have been the PPA or more likely might have been all the manual hacking that's gone on here. And rightfully so -- it was a bit of an emergency bug. But I've just tested upgrades to 42.9-0ubuntu8 in a fresh VM and cannot reproduce any upgrade issues. It might be a good idea if everyone just purges the PPA and manually installs the 42.9-0ubuntu8 packages...

3. People mistakenly install/upgrade 'mutter'/'mutter-common' alone when really it's 'libmutter-10-0' that provides the fix. E.g. comment #96.

Overall it looks like the fix is sound and jammy has been verified by comments #98 and #99.

> The only thing that has worked for me is listed below
> 1. Reinstall Ubuntu LTS 22.04.4 without any upgrade or just don't connect it to the internet.

To anyone who considers reinstalling the OS due to this issue (because you messed up your system beyond repair, or whatever): Why not go for 24.04? This very issue is fixed there properly, and you save yourself from a future upgrade. (Yes I know for LTS guys it's usually recommended to wait for the .1 subrelease, but given the severity of this issue, dist-upgrading right now might be a viable option to consider.)

To anyone on 23.10 which will EOL in 2 months anyway: Why not dist-upgrade now?

Just my 2 cents. (I'm not trying to defend Ubuntu in this badly messed up situation; I'm just trying to bring yet another possible solution to its users' attention.)

I don't understand how to re-fix this on 22.04 after the original PPA fix — any instructions?

@egmont-gmail For users on 22.04, would you suggest upgrading to 24.04 as well ?
I guess the right upgrade path would be to upgrade to 23.10 first and then to 24.04.
Is this something you would recommend or are there some important pitfalls to know about beforehand ?

In order to avoid removing vital packages when installing the proposed package(s) on Ubuntu 22.04, I installed the following packages together:

sudo apt install gir1.2-mutter-10/jammy-proposed libmutter-10-0/jammy-proposed

@toniopelo I don't know about others but I'm inclined toward waiting for Ubuntu 24.04.1 because of my personal experience. I was eager to upgrade to Ubuntu 24.04 for unrelated reasons but reverted to Ubuntu 22.04.4 due to experiencing display/GPU issues that I didn't have before.

I do not want to reinstall Ubuntu 22.04.4 just 3 months before I install Ubuntu 24.04.1 Too much work.

OK. I bit the bullet (and it turned out to be not-that-painful). From the Jammy Proposed PPA, I installed:

     sudo apt install libmutter-10-0=42.9-0ubuntu8
     sudo apt install gir1.2-mutter-10=42.9-0ubuntu8

and autoremoved everything it proposed.

I then rebooted normally, and was presented with a console terminal screen (autoremove had removed gnome-shell, gdm, and a bunch of other things). How 1980s!

I then installed

     sudo apt install ubuntu-desktop

and rebooted normally.

Everything seems to have returned AND no results from sudo journalctl -b0 | grep MetaSyncRing

Hope this helps others. :-) Thanks Daniel for taking this seriously.

@sldayo OMG, you got it right!
Finally this is fixed on my machine, thanks, A LOT.

Apparently it was upgrading mutter to the jammy-proposed version explicitly that caused the dependency removing mess, so your command works fine and only upgrade the necessary packages.
I can confirm, after a reboot everything is fine and no results from `sudo journalctl -b0 | grep MetaSyncRing`

So the right command to install the jammy-proposed fix is this one from @sldayo (comment #127) :

`sudo apt install gir1.2-mutter-10/jammy-proposed libmutter-10-0/jammy-proposed`

Then reboot and it works fine :).

> @egmont-gmail For users on 22.04, would you suggest upgrading to 24.04 as well ?
> Is this something you would recommend or are there some important pitfalls to know about beforehand ?

@toniopelo I cannot make a generic recommendation. It depends on your circumstances, priorities, short-term goals, long-term goals, etc.

If, apart from this very issue, you're super happy with 22.04 and don't plan to upgrade for many-many years, potentially jumping straight to 26.04 or 28.04, then I'd recommend to stay on 22.04, find a workaround or wait patiently until the fix is properly released.

If you'd upgrade to 24.04 anyway, maybe in the following months, then upgrading right now (and getting rid of this issue once and for all) might not be a bad idea.

> I guess the right upgrade path would be to upgrade to 23.10 first and then to 24.04.

As far as I know, it's either through all the releases (22.04 -> 22.10 -> 23.04 -> 23.10 -> 24.04) which is no longer possible as 22.10 and 23.04 have already EOL'ed; or from LTS to LTS, i.e. 22.04 -> 24.04. I don't think other types of dist-upgrades are supported. I might be wrong, though.

Ok, thanks for the thorough answer @egmont-gmail.
I fixed the issue for now as stated in my last comment though, so I'm gonna stay on 22.04 if it stays fixed.

@sldayo Can you help? This is what I get:

$ sudo apt install gir1.2-mutter-10/jammy-proposed libmutter-10-0/jammy-proposed
[sudo] password for donn:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package gir1.2-mutter-10 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package libmutter-10-0 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Release 'jammy-proposed' for 'gir1.2-mutter-10' was not found
E: Release 'jammy-proposed' for 'libmutter-10-0' was not found

Anyone got instructions for dummies for me ? :D

@donn-ingle Did you enable jammy-proposed first?

See the following posts:

- #92 by vorlon
- #115 by taisph

@sladyo - Thanks. I hope I manage all that! Should I do this, or wait for some official 22.04 solution? Don't want to further snafu the whole thing.

ETA - I went ahead and it seems ok. Gulp! Thanks.

You don't really need to enable jammy-proposed. Just download the 3 proposed packages:

 * https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu8/+build/28435945/+files/gir1.2-mutter-10_42.9-0ubuntu8_amd64.deb

 * https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu8/+build/28435945/+files/libmutter-10-0_42.9-0ubuntu8_amd64.deb

 * https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu8/+build/28435945/+files/mutter-common_42.9-0ubuntu8_all.deb

and if you already had the 'mutter' package (which you don't need) then also:

 * https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu8/+build/28435945/+files/mutter_42.9-0ubuntu8_amd64.deb

And install them as one:

  sudo dpkg -i *.deb

Daniel;

Thanks for the update. Installed successfully and seems to be working fine
now. I have put the packages on hold this time to prevent unintended
upgrades like the last week.

If you can't hear the dogwoods barking you're taking things too seriously.

On Wed, May 15, 2024 at 1:30 AM Daniel van Vugt <email address hidden>
wrote:

> You don't really need to enable jammy-proposed. Just download the 3
> proposed packages:
>
> *
>
> https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu8/+build/28435945/+files/gir1.2-mutter-10_42.9-0ubuntu8_amd64.deb
>
> *
>
> https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu8/+build/28435945/+files/libmutter-10-0_42.9-0ubuntu8_amd64.deb
>
> *
>
> https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu8/+build/28435945/+files/mutter-
> common_42.9-0ubuntu8_all.deb
> <https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu8/+build/28435945/+files/mutter-common_42.9-0ubuntu8_all.deb>
>
> and if you already had the 'mutter' package (which you don't need) then
> also:
>
> *
>
> https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu8/+build/28435945/+files/mutter_42.9-0ubuntu8_amd64.deb
>
> And install them as one:
>
> sudo dpkg -i *.deb
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (2065489).
> 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 Released
> Status in mutter source package in Jammy:
> Fix Committed
> Status in mutter source package in Mantic:
> Fix Committed
> Status in mutter source package in Noble:
> Fix Released
>
> 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
> Unam...

Thank you Daniel. I removed the now-overruled PPA from earlier in this thread and directly installed those 4 packages on my 22.04 workstation. Works great after a reboot.

Downloading / installing the four packages vanvugt recommended in #135 + a reboot fixed my terminal.

Thank you!

X11 / Nvidia 535.171.04 / Ubuntu 22.04.4

>You don't really need to enable jammy-proposed. Just download the 3 proposed packages:

I first tried to install these 3 packages, albeit not with the suggested method of installing them all at once as a bundle with the dpkg command proposed by Daniel, and I ended up with a broken desktop (was getting some “Failed to start VirtualBox Linux kernel module…” errors on boot), which I fixed running sudo apt install --reinstall ubuntu-gnome-desktop).

Enabling jammy-proposed seems to have fixed the issue though. Thanks!

Using 550.78 nvidia driver

I enabled jammy-proposed, as well as following the guide on https://wiki.ubuntu.com/Testing/EnableProposed to enable selective upgrading from proposed, then ran the following command:

sudo apt install gir1.2-mutter-10/jammy-proposed libmutter-10-0/jammy-proposed mutter-common/jammy-proposed

This installed the same set of packages mentioned in #135. After a reboot, all of my issues with the terminal seem to have gone away. So the fix looks good from here.

Anyone planning to install this fix from proposed should enable selective upgrading unless they want to test every package currently in proposed.

In Ubuntu 22.04.4 with NVidia driver 535.171.04 and windowing system X11, I downloaded and installed the packages recommended in #135: after a reboot, my terminal was fixed.

Thank you @vanvugt!

Exactly the configuration Leonardo (#141) and tim (#138) have, and for me the 4 packages from daniel (#135) also did the trick :-)
Thanks!!!