This bug was fixed in the package mutter - 46.2-1ubuntu0.24.04.1
---------------
mutter (46.2-1ubuntu0.24.04.1) noble; urgency=medium
[ Daniel van Vugt ]
* New upstream release 46.2 (LP: #2068598)
- Fixed mouse clicks falling through to the window behind (LP: #2026194)
- Fixed a crash in meta_wayland_transaction_commit (LP: #2061739)
- Fixed night light getting stuck on (LP: #2066902)
* New upstream release 46.1 (LP: #2064735):
- Fixed blank screen on hybrid GPU machines using nouveau (LP: #2066931)
- Fixed a monitor hotplug crash (LP: #2050865)
- Improved performance on secondary GPU monitors (LP: #2038801)
* Refreshed patches:
- Support-Dynamic-triple-double-buffering.patch (LP: #2070437, LP: #2070438)
- meson-Do-not-mark-CI-test-tools-as-required.patch
- Mark-several-additional-tests-as-flaky.patch
* Add clutter/conform gesture tests to the list of known flaky ones:
it's a new test in Mutter 46 and not yet reliable.
* Add build-Compile-schemas-locally-for-use-in-build-tests.patch to compile
gsettings schemas for use in build tests. Debian CI requires this now and
it makes rebuilds more resilient against infrastructure changes.
* Add wayland-Disable-linux-drm-syncobj-v1.patch to avoid enabling major
new features in Noble updates, as detailed in:
https://lists.ubuntu.com/archives/ubuntu-release/2024-May/006087.html
* Add backends-Handle-null-views-instead-of-creating-dummy-view.patch
to prevent "clutter_frame_clock_notify_presented: code should not be
reached" log spam in some Nvidia Wayland sessions (LP: #1967707)
* Add backends-Restore-support-for-X11-cursor-themes.patch to restore
support for X11 cursor themes, which was lost in Mutter 46.0
(LP: #2062377, LP: #2063869)
[ Jeremy Bícha ]
* Stop compiling gsettings schemas in debian/rules
* Opt into Salsa CI
* Drop packaging references to Hurd since this is Linux-only
* Update libmutter-14-0.symbols
* Update Breaks
* Refreshed patches:
- window-Add-ability-to-override-the-edge-constraints.patch
- x11-Add-support-for-fractional-scaling-using-Randr.patch
* Drop upstreamed patches:
- Nvidia-secondary-GPU-copy-acceleration.patch
- compositor-sync-ring-Allow-the-gpu_fence-to-be-moved.patch
[ Marco Trevisan ]
* Add place-Always-center-initial-setup.patch (LP: #2016013)
-- Daniel van Vugt <[email protected]> Fri, 28 Jun 2024
17:35:12 +0800
** Changed in: mutter (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1967707
Title:
Nvidia Wayland sessions sometimes flood the log with
"clutter_frame_clock_notify_presented: code should not be reached"
Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Noble:
Fix Released
Status in mutter source package in Oracular:
Fix Released
Bug description:
[ Impact ]
Nvidia Wayland sessions sometimes flood the log with
"clutter_frame_clock_notify_presented: code should not be reached"
This is almost harmless except that it wastes disk space and the high
frequency of messages (one per frame) impacts desktop performance.
[ Test Plan ]
0. Start with either an Nvidia-only desktop providing that bug 2060268
is NOT fixed yet; or an Nvidia desktop which also has an integrated
GPU enabled such that Nvidia is configured as the primary (boot) GPU
in the BIOS and a monitor is plugged into EACH GPU.
1. Log into a Wayland session.
2. Run:
journalctl -f /usr/bin/gnome-shell
and verify there is not a flood of messages with each screen
redraw.
[ Where problems could occur ]
Wayland multi-GPU startup is the code affected here so any
configuration expecting to use multiple GPUs simultaneously in a
Wayland session may be affected.
While bug 2060268 is unresolved even single GPU Nvidia systems will be
affected due to the phantom GPU resulting from that bug.
[ Original description ]
Nvidia Wayland sessions sometimes flood the log with:
[ 13.105877] computer gnome-shell[1264]:
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
code should not be reached
[ 13.106163] computer gnome-shell[1264]:
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
code should not be reached
[ 13.112490] computer gnome-shell[1264]:
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
code should not be reached
[ 13.125302] computer gnome-shell[1264]:
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
code should not be reached
[ 13.142242] computer gnome-shell[1264]:
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
code should not be reached
I've been seeing the issue for months although it only seems to happen
*after* something has gone wrong in mutter. Not by default.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967707/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
