| 2024-06-26 06:41:55 |
Daniel van Vugt |
bug |
|
|
added bug |
| 2024-06-26 06:42:06 |
Daniel van Vugt |
nominated for series |
|
Ubuntu Noble |
|
| 2024-06-26 06:42:06 |
Daniel van Vugt |
bug task added |
|
mutter (Ubuntu Noble) |
|
| 2024-06-26 06:42:06 |
Daniel van Vugt |
nominated for series |
|
Ubuntu Oracular |
|
| 2024-06-26 06:42:06 |
Daniel van Vugt |
bug task added |
|
mutter (Ubuntu Oracular) |
|
| 2024-06-26 06:42:16 |
Daniel van Vugt |
mutter (Ubuntu Oracular): assignee |
|
Jeremy Bícha (jbicha) |
|
| 2024-06-26 06:42:18 |
Daniel van Vugt |
mutter (Ubuntu Oracular): milestone |
|
ubuntu-24.10 |
|
| 2024-06-26 06:42:23 |
Daniel van Vugt |
mutter (Ubuntu Noble): status |
New |
Triaged |
|
| 2024-06-26 06:42:25 |
Daniel van Vugt |
mutter (Ubuntu Noble): importance |
Undecided |
Low |
|
| 2024-06-26 06:42:30 |
Daniel van Vugt |
mutter (Ubuntu Noble): assignee |
|
Daniel van Vugt (vanvugt) |
|
| 2024-06-26 06:42:33 |
Daniel van Vugt |
mutter (Ubuntu Noble): milestone |
|
ubuntu-24.04.1 |
|
| 2024-06-26 07:03:16 |
Daniel van Vugt |
tags |
noble oracular triple-buffering |
noble oracular triple-buffering vrr |
|
| 2024-06-27 05:52:11 |
Daniel van Vugt |
description |
[ Impact ]
Fullscreen direct scanout is not used if you enable the hidden experimental VRR feature in Mutter 46.
[ Test Plan ]
0. Find a monitor that is VRR capable.
1. Set MUTTER_DEBUG=kms in /etc/environment
2. Enable VRR (TODO: need to relearn all the steps required)
3. Reboot.
4. Log into a Wayland session.
5. Open Google Chrome, start an animation like https://www.vsynctester.com/ and make it full screen (F11).
6. journalctl -f /usr/bin/gnome-shell | grep Post
7. Verify the "Post" messages you see mention direct scan out and not "composite".
[ Where problems could occur ]
Since the fix affects the runtime decision of whether to allow triple buffering or stay double buffering, the main risk is that triple buffering wouldn't be used in some situation where we would rather have it to maintain a smoother frame rate.
[ Other Info ]
First reported upstream in:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_2062222
We DO NOT recommend enabling the VRR feature anyway because it is still buggy:
https://gitlab.gnome.org/GNOME/mutter/-/issues/3419 |
[ Impact ]
Fullscreen direct scanout is not used if you enable the hidden experimental VRR feature in Mutter 46.
[ Test Plan ]
0. Find a monitor that is VRR capable.
1. Set MUTTER_DEBUG=kms in /etc/environment
2. Enable VRR (TODO: need to relearn all the steps required)
3. Reboot.
4. Log into a Wayland session.
5. Open Google Chrome, start an animation like https://www.vsynctester.com/ and make it full screen (F11).
6. journalctl -f /usr/bin/gnome-shell | grep Post
7. Verify the "Post" messages you see mention direct scan out and not "composite".
[ Where problems could occur ]
Since the fix affects the runtime decision of whether to allow triple buffering or stay double buffering, the main risk is that triple buffering wouldn't be used in some situation where we would rather have it to maintain a smoother frame rate.
[ Other Info ]
First reported upstream in:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_2062222
We DO NOT recommend enabling the VRR feature anyway because it is still buggy (bug 2066080) |
|
| 2024-06-27 06:09:00 |
Daniel van Vugt |
description |
[ Impact ]
Fullscreen direct scanout is not used if you enable the hidden experimental VRR feature in Mutter 46.
[ Test Plan ]
0. Find a monitor that is VRR capable.
1. Set MUTTER_DEBUG=kms in /etc/environment
2. Enable VRR (TODO: need to relearn all the steps required)
3. Reboot.
4. Log into a Wayland session.
5. Open Google Chrome, start an animation like https://www.vsynctester.com/ and make it full screen (F11).
6. journalctl -f /usr/bin/gnome-shell | grep Post
7. Verify the "Post" messages you see mention direct scan out and not "composite".
[ Where problems could occur ]
Since the fix affects the runtime decision of whether to allow triple buffering or stay double buffering, the main risk is that triple buffering wouldn't be used in some situation where we would rather have it to maintain a smoother frame rate.
[ Other Info ]
First reported upstream in:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_2062222
We DO NOT recommend enabling the VRR feature anyway because it is still buggy (bug 2066080) |
[ Impact ]
Fullscreen direct scanout is not used if you enable the hidden experimental VRR feature in Mutter 46.
[ Test Plan ]
0. Find a monitor that is VRR capable.
1. Set CLUTTER_PAINT=damage-region in /etc/environment
2. gsettings set org.gnome.mutter experimental-features '["variable-refresh-rate"]'
3. Reboot.
4. Log into a Wayland session.
5. Don't panic. The screen is meant to turn red whenever something changes.
6. In Settings > Display verify that variable refresh rate is detected and enabled.
7. Open a web browser, start an animation like https://www.vsynctester.com/
8. Press F11 to make it full screen.
9. Verify the screen has now stopped being red.
10. Press F11 again to exit full screen.
11. Verify the screen has gone red again.
[ Where problems could occur ]
Since the fix affects the runtime decision of whether to allow triple buffering or stay double buffering, the main risk is that triple buffering wouldn't be used in some situation where we would rather have it to maintain a smoother frame rate.
[ Other Info ]
First reported upstream in:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_2062222
We DO NOT recommend enabling the VRR feature anyway because it is still buggy (bug 2066080) |
|
| 2024-06-27 06:10:46 |
Daniel van Vugt |
description |
[ Impact ]
Fullscreen direct scanout is not used if you enable the hidden experimental VRR feature in Mutter 46.
[ Test Plan ]
0. Find a monitor that is VRR capable.
1. Set CLUTTER_PAINT=damage-region in /etc/environment
2. gsettings set org.gnome.mutter experimental-features '["variable-refresh-rate"]'
3. Reboot.
4. Log into a Wayland session.
5. Don't panic. The screen is meant to turn red whenever something changes.
6. In Settings > Display verify that variable refresh rate is detected and enabled.
7. Open a web browser, start an animation like https://www.vsynctester.com/
8. Press F11 to make it full screen.
9. Verify the screen has now stopped being red.
10. Press F11 again to exit full screen.
11. Verify the screen has gone red again.
[ Where problems could occur ]
Since the fix affects the runtime decision of whether to allow triple buffering or stay double buffering, the main risk is that triple buffering wouldn't be used in some situation where we would rather have it to maintain a smoother frame rate.
[ Other Info ]
First reported upstream in:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_2062222
We DO NOT recommend enabling the VRR feature anyway because it is still buggy (bug 2066080) |
[ Impact ]
Fullscreen direct scanout is not used if you enable the hidden experimental VRR feature in Mutter 46.
[ Test Plan ]
0. Find a monitor that is VRR capable.
1. Set CLUTTER_PAINT=damage-region in /etc/environment
2. gsettings set org.gnome.mutter experimental-features '["variable-refresh-rate"]'
3. Reboot.
4. Log into a Wayland session.
5. Don't panic. The screen is meant to turn red whenever something changes.
6. In Settings > Display verify that variable refresh rate is detected and enabled.
7. Open Google Chrome (Firefox won't work) and start an animation like https://www.vsynctester.com/
8. Press F11 to make it full screen.
9. Verify the screen has now stopped being red.
10. Press F11 again to exit full screen.
11. Verify the screen has gone red again.
[ Where problems could occur ]
Since the fix affects the runtime decision of whether to allow triple buffering or stay double buffering, the main risk is that triple buffering wouldn't be used in some situation where we would rather have it to maintain a smoother frame rate.
[ Other Info ]
First reported upstream in:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_2062222
We DO NOT recommend enabling the VRR feature anyway because it is still buggy (bug 2066080) |
|
| 2024-06-27 06:11:28 |
Daniel van Vugt |
description |
[ Impact ]
Fullscreen direct scanout is not used if you enable the hidden experimental VRR feature in Mutter 46.
[ Test Plan ]
0. Find a monitor that is VRR capable.
1. Set CLUTTER_PAINT=damage-region in /etc/environment
2. gsettings set org.gnome.mutter experimental-features '["variable-refresh-rate"]'
3. Reboot.
4. Log into a Wayland session.
5. Don't panic. The screen is meant to turn red whenever something changes.
6. In Settings > Display verify that variable refresh rate is detected and enabled.
7. Open Google Chrome (Firefox won't work) and start an animation like https://www.vsynctester.com/
8. Press F11 to make it full screen.
9. Verify the screen has now stopped being red.
10. Press F11 again to exit full screen.
11. Verify the screen has gone red again.
[ Where problems could occur ]
Since the fix affects the runtime decision of whether to allow triple buffering or stay double buffering, the main risk is that triple buffering wouldn't be used in some situation where we would rather have it to maintain a smoother frame rate.
[ Other Info ]
First reported upstream in:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_2062222
We DO NOT recommend enabling the VRR feature anyway because it is still buggy (bug 2066080) |
[ Impact ]
Fullscreen direct scanout is not used if you enable the hidden experimental VRR feature in Mutter 46.
[ Test Plan ]
0. Find a monitor that is VRR capable.
1. Set CLUTTER_PAINT=damage-region in /etc/environment
2. gsettings set org.gnome.mutter experimental-features '["variable-refresh-rate"]'
3. Reboot.
4. Log into a Wayland session.
5. Don't panic. The screen is meant to turn red whenever something changes.
6. In Settings > Display verify that variable refresh rate is detected and enabled.
7. Open Google Chrome (Firefox won't work) and start an animation like https://www.vsynctester.com/
8. Press F11 to make it full screen.
9. Verify the screen has now stopped being red.
10. Press F11 again to exit full screen.
11. Verify the screen has gone red again.
If the screen went black at the end, don't panic. That's a separate bug 2066080.
[ Where problems could occur ]
Since the fix affects the runtime decision of whether to allow triple buffering or stay double buffering, the main risk is that triple buffering wouldn't be used in some situation where we would rather have it to maintain a smoother frame rate.
[ Other Info ]
First reported upstream in:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_2062222
We DO NOT recommend enabling the VRR feature anyway because it is still buggy (bug 2066080) |
|
| 2024-06-28 09:03:58 |
Daniel van Vugt |
mutter (Ubuntu Noble): status |
Triaged |
In Progress |
|
| 2024-07-05 11:44:55 |
Timo Aaltonen |
mutter (Ubuntu Noble): status |
In Progress |
Fix Committed |
|
| 2024-07-05 11:44:59 |
Timo Aaltonen |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2024-07-05 11:45:01 |
Timo Aaltonen |
bug |
|
|
added subscriber SRU Verification |
| 2024-07-05 11:45:16 |
Timo Aaltonen |
tags |
noble oracular triple-buffering vrr |
noble oracular triple-buffering verification-needed verification-needed-noble vrr |
|
| 2024-07-09 06:03:13 |
Daniel van Vugt |
tags |
noble oracular triple-buffering verification-needed verification-needed-noble vrr |
noble oracular triple-buffering verification-done-noble verification-needed vrr |
|
| 2024-07-22 08:27:41 |
Daniel van Vugt |
tags |
noble oracular triple-buffering verification-done-noble verification-needed vrr |
noble oracular triple-buffering verification-done verification-done-noble vrr |
|
