Public bug reported:
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.
** Affects: mutter (Ubuntu)
Importance: Undecided
Assignee: Daniel van Vugt (vanvugt)
Status: New
** Affects: nvidia-graphics-drivers-510 (Ubuntu)
Importance: Undecided
Status: New
** Tags: jammy nvidia nvidia-wayland wayland-session
** Tags added: jammy nvidia nvidia-wayland wayland-session
** Also affects: nvidia-graphics-drivers-510 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Description changed:
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.
+ have to reboot the whole machine so it seems like something has latched
+ in the nvidia-drm kernel driver.
--
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:
New
Status in nvidia-graphics-drivers-510 package in Ubuntu:
New
Bug 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.
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
