mirror of
https://github.com/brl/mutter.git
synced 2025-02-16 13:24:09 +00:00
clutter/frame-clock: Schedule a frame at least once per second
Users of Debian arm64 (aarch64) report that on at least some GPUs or screens, after time-based screen blanking has occurred, it is not possible to unlock the screen. Bisection indicates that this regressed in commit 209b1ba3, so presumably this is because a refresh rate of 0 is reported while the screen is blanked, leading to the frame clock pausing forever. Fixes: 209b1ba3 "clutter/frame-clock: Adapt refresh rate from to frame info" Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/1536 Bug-Debian: https://bugs.debian.org/974172 Signed-off-by: Simon McVittie <smcv@debian.org> Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1601>
This commit is contained in:
parent
58930e9e1f
commit
1a1f1eccba
@ -197,7 +197,8 @@ clutter_frame_clock_notify_presented (ClutterFrameClock *frame_clock,
|
|||||||
frame_clock->last_presentation_time_us = g_get_monotonic_time ();
|
frame_clock->last_presentation_time_us = g_get_monotonic_time ();
|
||||||
}
|
}
|
||||||
|
|
||||||
frame_clock->refresh_rate = frame_info->refresh_rate;
|
if (frame_info->refresh_rate > 1)
|
||||||
|
frame_clock->refresh_rate = frame_info->refresh_rate;
|
||||||
|
|
||||||
switch (frame_clock->state)
|
switch (frame_clock->state)
|
||||||
{
|
{
|
||||||
|
Loading…
x
Reference in New Issue
Block a user