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 |
|