[Bug 2017097] Re: [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed

This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: https://iso.qa.ubuntu.com/qatracker/reports/bugs/2017097 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, w

[Bug 2017097] Re: [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed

How do you determine shell fps? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2017097 Title: [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed To manage notifica

[Bug 2017097] Re: [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed

To get FPS in the system journal set environment: CLUTTER_SHOW_FPS=1 which will give you accurate FPS but not accurate render times because OpenGL is asynchronous. To get accurate render times too you will need to slow it down a little by adding: COGL_DEBUG=sync-frame -- You received this

[Bug 2017097] Re: [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed

Think I found it. The new version of triple buffering in mutter 44.0 is too aggressive at scaling back to double buffering. So that's why 22.04 and 22.10 felt faster on Pi than 23.04 does right now. The workaround is to add this to /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always ** Tag

[Bug 2017097] Re: [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed

See also bug 2017137 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2017097 Title: [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed To manage notifications about

[Bug 2017097] Re: [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed

** Description changed: + [ Impact ] + On a Raspberry Pi 400, GNOME Shell runs at 30 FPS unless the CPU is being stressed in which case it becomes a smooth 60 FPS. Seems like a frequency scaling issue. + + [ Workaround ] + + Add this to /etc/environment: + + MUTTER_DEBUG_TRIPLE_BUFFERI

[Bug 2017097] Re: [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed

** Changed in: mutter (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2017097 Title: [raspi] GNOME Shell runs at 30 FPS unless the CP

[Bug 2017097] Re: [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed

Fix committed to https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441 but I am waiting till there is a 44.1 tag before rebasing, branching, and proposing a new triple buffering patch to salsa. I will also be away till Monday so it probably won't happen before then. -- You received this bug

[Bug 2017097] Re: [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed

** Tags added: fixed-upstream -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2017097 Title: [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed To manage notificati

[Bug 2017097] Re: [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed

Fixed in mutter 44.1 which is now in Ubuntu 23.10 ** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2017097 T

[Bug 2017097] Re: [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed

** Also affects: mutter (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu Lunar) Status: New => In Progress -- You received this bug notification because you are a member of Ubu