You're talking about bug 2059847, not this one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054510
Title:
Incomplete screen redraws in virtual machines running Xorg
To manage notifications
Update on Jammy yesterday installed libmutter version 42.9-0ubuntu7.1
and the slow behavior has returned. Shoulda pinned the ppa version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054510
Title:
** Changed in: mutter (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054510
Title:
Incomplete screen redraws in virtual machines running
The above issue is being tracked in bug 2059847.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054510
Title:
Incomplete screen redraws in virtual machines running Xorg
To manage notifications
Another most likely duplicate: https://github.com/gnome-
terminator/terminator/issues/899
And yet another most likely duplicate:
https://bbs.archlinux.org/viewtopic.php?id=294164. Here a user claims
that downgrading gnome-shell and mutter fixes the issue, and points to
upstream issue
During the last barely more than 24 hours, at least 4 people have
reported/confirmed heavy latencies newly appearing in their GNOME
Terminal. One person with Ubuntu 23.10 and two people with Ubuntu 22.04
(one of which comments has just been removed).
This bug was fixed in the package mutter - 42.9-0ubuntu7
---
mutter (42.9-0ubuntu7) jammy; urgency=medium
* Add build-Set-built-headers-as-libmutter_dep-sources.patch to prevent
occasional build failures depending on parallelism (LP: #2055530)
* Add
This bug was fixed in the package mutter - 45.2-0ubuntu4
---
mutter (45.2-0ubuntu4) mantic; urgency=medium
[ Kai-Heng Feng ]
* Fix mirror mode on reduced blanking panel. (LP: #2051074)
[ Daniel van Vugt ]
* Add compositor-x11-Sync-again-at-the-end-of-before_paint.patch
Yes, please make sure the flaky tests are marked as such in the
autopkgtests. SRUs are not released until either the test passes or the
package version is marked as badtest in the britney hints.
(A retry has caused it to pass on armhf)
--
You received this bug notification because you are a
Sorry I only just figured out that comment #17 is about mantic, not
jammy.
https://ubuntu-archive-team.ubuntu.com/proposed-
migration/mantic/update_excuses.html#mutter
And the Debian fix I mentioned in comment #18 is actually in 44.8-1
onward *and* 45.2-2 onward. So mantic would get the fix for
Thanks for the fix!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054510
Title:
Incomplete screen redraws in virtual machines running Xorg
To manage notifications about this bug go to:
Done: https://salsa.debian.org/gnome-
team/mutter/-/commit/1e2c8fedb0bcd293501420390c3bea48f9049301
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054510
Title:
Incomplete screen redraws in virtual
It can be put into the next mutter update but there is no reason to
delay the currently proposed update for it. This seems like a never-
ending problem that we're discovering old intermittent build failures in
an old GNOME release. We will fix them as they are discovered, but not
all of them need
Should [0] be part of the SRU to avoid the test failure?
[0] https://salsa.debian.org/gnome-
team/mutter/-/commit/98302806f85ffe4cd67768fe63992ba32e77146a
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That test passed in the actual build:
https://launchpadlibrarian.net/719148617/buildlog_ubuntu-jammy-armhf.mutter_42.9-0ubuntu7_BUILDING.txt.gz
It is known to be a flaky test (moreso on Arm) and its failure is not related
to the code changes here.
The test failure on armhf persists:
939s # Running test: mutter-13/fullscreen-maximize.test
940s # Executing: mutter-13/fullscreen-maximize.test
941s # FAIL: mutter-13/fullscreen-maximize.test (Child process exited with code
1)
941s not ok - mutter-13/fullscreen-maximize.test
--
You received
There is an armhf DEP8 failure that I just retriggered, let's see if it
passes in the next run.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054510
Title:
Incomplete screen redraws in virtual
Verified fixed on jammy using mutter version 42.9-0ubuntu7 and the test
plan in the bug description.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification
Hello Daniel, 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-0ubuntu7
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
That failing test case:
1180s # FAIL: mutter-13/minimized.test (Child process exited with code
133)
is known to be flaky. I've seen it fail on unrelated changes upstream.
And it is indeed unrelated to these changes.
The rebuild has now succeeded:
Here's the fixes for jammy build failures in 42.9-0ubuntu6
** Patch added: "mutter_42.9-0ubuntu7.debdiff"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2054510/+attachment/5751114/+files/mutter_42.9-0ubuntu7.debdiff
--
You received this bug notification because you are a member of
Verified fixed on Mantic using Mutter version 45.2-0ubuntu4.
** Description changed:
[ Impact ]
When using software rendering on Xorg (so usually just in VMs), some
parts of app windows may fail to redraw.
https://gitlab.gnome.org/GNOME/mutter/-/issues/2880
[ Test Plan ]
Oh I see the issue with 'meta-enum-types.h'. It's generated at build
time and most likely someone forgot to declare dependencies on that. So
at random times, depending on how parallel your build is, it might not
be built before it gets included.
--
You received this bug notification because you
Mantic built OK, except on arm64 and armhf due to known flaky tests. We
can try rebuilding for those.
Jammy failed to build mostly due to a new bug 2055519 (unrelated to our
changes). So we should add a fix for that and roll a new version. amd64
also failed with "fatal error:
Stange. Jammy is failing to build for a reason unrelated to anything
that has changed since the last update:
In file included from ../src/backends/meta-backend-private.h:39,
from ../src/backends/x11/meta-backend-x11.h:31,
from
Hello Daniel, 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-0ubuntu6
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Daniel, 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-0ubuntu4
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
27 matches
Mail list logo
