Activity log for bug #1967707

Date Who What changed Old value New value Message
2022-04-04 03:13:47 Daniel van Vugt bug added bug
2022-04-04 03:14:01 Daniel van Vugt tags jammy nvidia nvidia-wayland wayland-session
2022-04-04 03:14:09 Daniel van Vugt bug task added nvidia-graphics-drivers-510 (Ubuntu)
2022-04-04 03:16:32 Daniel van Vugt mutter (Ubuntu): assignee Daniel van Vugt (vanvugt)
2022-04-04 03:17:12 Daniel van Vugt 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. Then when the messages start, restarting gnome-shell won't fix it. You have to reboot the whole machine. 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. Then when the messages start, restarting gnome-shell won't fix it. You have to reboot the whole machine so it seems like something has latched in the nvidia-drm kernel driver.
2022-04-04 09:47:25 Daniel van Vugt mutter (Ubuntu): importance Undecided Medium
2022-04-04 09:47:30 Daniel van Vugt mutter (Ubuntu): status New In Progress
2022-04-04 09:47:38 Daniel van Vugt bug task deleted nvidia-graphics-drivers-510 (Ubuntu)
2022-04-04 10:34:54 Daniel van Vugt 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. Then when the messages start, restarting gnome-shell won't fix it. You have to reboot the whole machine so it seems like something has latched in the nvidia-drm kernel driver. 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.
2022-04-04 10:35:09 Daniel van Vugt summary Nvidia Wayland sessions sometimes flood the log with [clutter_frame_clock_notify_presented: code should not be reached] Nvidia Wayland sessions sometimes flood the log with "clutter_frame_clock_notify_presented: code should not be reached"
2022-09-09 07:18:20 Daniel van Vugt mutter (Ubuntu): status In Progress Triaged
2022-11-02 09:45:11 Daniel van Vugt bug watch added https://gitlab.gnome.org/GNOME/mutter/-/issues/2489
2022-11-02 09:45:11 Daniel van Vugt bug task added mutter
2022-11-02 10:50:55 Bug Watch Updater mutter: status Unknown New
2023-07-12 08:48:22 Daniel van Vugt tags jammy nvidia nvidia-wayland wayland-session jammy logspam nvidia nvidia-wayland wayland-session
2023-10-05 03:54:57 Daniel van Vugt mutter (Ubuntu): status Triaged In Progress
2024-01-23 03:26:17 Daniel van Vugt bug task deleted mutter
2024-05-14 09:01:46 Daniel van Vugt tags jammy logspam nvidia nvidia-wayland wayland-session jammy logspam noble nvidia nvidia-wayland wayland-session
2024-06-17 01:52:23 Daniel van Vugt mutter (Ubuntu): status In Progress Fix Committed
2024-06-17 01:52:33 Daniel van Vugt tags jammy logspam noble nvidia nvidia-wayland wayland-session fixed-in-mutter-47 fixed-upstream jammy logspam noble nvidia nvidia-wayland wayland-session
2024-06-18 09:02:57 Daniel van Vugt mutter (Ubuntu): milestone ubuntu-24.10
2024-06-25 05:54:25 Daniel van Vugt tags fixed-in-mutter-47 fixed-upstream jammy logspam noble nvidia nvidia-wayland wayland-session fixed-in-mutter-47 fixed-upstream jammy logspam noble nvidia nvidia-wayland performance wayland-session
2024-06-25 06:03:47 Daniel van Vugt 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. [ 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.
2024-06-25 06:03:57 Daniel van Vugt nominated for series Ubuntu Noble
2024-06-25 06:03:57 Daniel van Vugt bug task added mutter (Ubuntu Noble)
2024-06-25 06:03:57 Daniel van Vugt nominated for series Ubuntu Oracular
2024-06-25 06:03:57 Daniel van Vugt bug task added mutter (Ubuntu Oracular)
2024-06-25 06:04:03 Daniel van Vugt mutter (Ubuntu Noble): assignee Daniel van Vugt (vanvugt)
2024-06-25 06:04:07 Daniel van Vugt mutter (Ubuntu Noble): importance Undecided Medium
2024-06-25 06:04:25 Daniel van Vugt bug task deleted mutter (Ubuntu Noble)
2024-06-25 08:46:59 Daniel van Vugt nominated for series Ubuntu Noble
2024-06-25 08:46:59 Daniel van Vugt bug task added mutter (Ubuntu Noble)
2024-06-25 08:47:07 Daniel van Vugt mutter (Ubuntu Noble): status New Triaged
2024-06-25 08:47:10 Daniel van Vugt mutter (Ubuntu Noble): importance Undecided Medium
2024-06-25 08:47:13 Daniel van Vugt mutter (Ubuntu Noble): assignee Daniel van Vugt (vanvugt)
2024-06-25 08:47:17 Daniel van Vugt mutter (Ubuntu Noble): milestone ubuntu-24.04.1
2024-06-25 22:55:21 Launchpad Janitor mutter (Ubuntu Oracular): status Fix Committed Fix Released
2024-06-28 09:02:55 Daniel van Vugt mutter (Ubuntu Noble): status Triaged In Progress
2024-07-05 11:41:03 Timo Aaltonen mutter (Ubuntu Noble): status In Progress Fix Committed
2024-07-05 11:41:05 Timo Aaltonen bug added subscriber Ubuntu Stable Release Updates Team
2024-07-05 11:41:09 Timo Aaltonen bug added subscriber SRU Verification
2024-07-05 11:41:23 Timo Aaltonen tags fixed-in-mutter-47 fixed-upstream jammy logspam noble nvidia nvidia-wayland performance wayland-session fixed-in-mutter-47 fixed-upstream jammy logspam noble nvidia nvidia-wayland performance verification-needed verification-needed-noble wayland-session
2024-07-09 09:22:18 Daniel van Vugt tags fixed-in-mutter-47 fixed-upstream jammy logspam noble nvidia nvidia-wayland performance verification-needed verification-needed-noble wayland-session fixed-in-mutter-47 fixed-upstream jammy logspam noble nvidia nvidia-wayland performance verification-done-noble verification-needed wayland-session
2024-07-22 08:27:49 Daniel van Vugt tags fixed-in-mutter-47 fixed-upstream jammy logspam noble nvidia nvidia-wayland performance verification-done-noble verification-needed wayland-session fixed-in-mutter-47 fixed-upstream jammy logspam noble nvidia nvidia-wayland performance verification-done verification-done-noble wayland-session
2024-07-31 03:15:47 Launchpad Janitor mutter (Ubuntu Noble): status Fix Committed Fix Released
2024-07-31 03:16:25 Chris Halse Rogers removed subscriber Ubuntu Stable Release Updates Team