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 clutter/ clutter- frame-clock. c:332): clutter_ frame_clock_ notify_ presented: code should not be reached clutter/ clutter- frame-clock. c:332): clutter_ frame_clock_ notify_ presented: code should not be reached clutter/ clutter- frame-clock. c:332): clutter_ frame_clock_ notify_ presented: code should not be reached clutter/ clutter- frame-clock. c:332): clutter_ frame_clock_ notify_ presented: code should not be reached
[ 13.106163] computer gnome-shell[1264]: (../clutter/
[ 13.112490] computer gnome-shell[1264]: (../clutter/
[ 13.125302] computer gnome-shell[1264]: (../clutter/
[ 13.142242] computer gnome-shell[1264]: (../clutter/
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.