The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
-- 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
