[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]
** Changed in: mutter (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Incomplete: Not seen since GNOME 41.
** Changed in: gnome-shell (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => (unassigned)
** Changed in: mutter (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => (unassigned)
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
That's great, but:
(a) When you reported this bug in GNOME 41 you didn't have the triple
buffering feature (libmutter-9-0 41.3-3ubuntu1); and
(b) If you are using jammy-proposed then even that (mutter
42~beta-1ubuntu2) does not yet have the
MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING feature.
So it
I saw on
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_1289561
that you introduced a new environment variable
MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING and subscribed to jammy-proposed
to try it out.
The problem does not occur since the updates!
I haven't even set the environment
This is definitely a bug in mutter (gnome-shell). Other people reported
it to me in recent months per comment #3.
** Changed in: gnome-shell (Ubuntu)
Status: Invalid => Confirmed
** Information type changed from Private to Public
** Also affects: mutter (Ubuntu)
Importance: Undecided
