| Git Clone URL: | https://aur.archlinux.org/mutter-performance.git (read-only, click to copy) |
|---|---|
| Package Base: | mutter-performance |
| Description: | GNOME Mutter Development Kit |
| Upstream URL: | https://gitlab.gnome.org/GNOME/mutter |
| Licenses: | GPL-2.0-or-later |
| Submitter: | Terence |
| Maintainer: | glorious-yellow |
| Last Packager: | glorious-yellow |
| Votes: | 74 |
| Popularity: | 0.000005 |
| First Submitted: | 2019-07-09 09:35 (UTC) |
| Last Updated: | 2025-09-26 01:43 (UTC) |
According to Daniel van Vugt: "Also note the second commit of https://gitlab.gnome.org/GNOME/mutter/merge_requests/363 provides a fix for this bug too. It replaces the first commit of https://gitlab.gnome.org/GNOME/mutter/merge_requests/281"
Does that mean we can safely switch off patch 281 and use only 363?
@Saren, Aha, thank you for the info.
@ValentinRO It is 3.32 that broke the extensions. The patches we added change low-level things that is very very unlikely related to shell extensions. Many of your extensions should have update for 3.32, if not look into github or even issues, most of the time you can change some files to get your extensions working again.
@Terence, this time I managed to install both mutter-workaround & shell-performance with clean os install (without touching settings in nvidia app).
See install log, you will see that I have manually updated the gsettings-desktop-schemas too: https://pastebin.com/gPJThqkD
Unfortunately, this broke some gnome extensions, I'm not sure if it is related to shell-performance.
This are the list which broke the extensions: https://extensions.gnome.org/extension/1362/custom-hot-corners/ https://extensions.gnome.org/extension/307/dash-to-dock/ https://extensions.gnome.org/extension/7/removable-drive-menu/
Furthermore, I got also update notification on the extension (which it won't update even if it says so): https://extensions.gnome.org/extension/19/user-themes/ https://extensions.gnome.org/extension/307/dash-to-dock/ https://extensions.gnome.org/extension/7/removable-drive-menu/
If this is related to shell-performance and to avoid headache, I will try this time only with mutter-workaround, with cherry-pick disabled # clutter-actor: Add detail to captured-event signal [performance]
@Terence We could detect whether gnome-shell-performance is installed and apply patches or not, just like what gnome-shell-performance is currently detecting mutter-781835-workaround to decide applying MR276 or not.
However it would be a catch 22 as they will be detecting each other...
@Saren ValentinRO pointed out an important issue we need to think about...
@ValentinRO yeah.
@Terence, Well, I was planning to install it too, only wasn't sure if it was included in mutter-workaround or not, it brought me to confusion when I read:
I guess you get more benefit with gnome-shell-performance installed than without?
@ValentinRO I'm trying to figure out what is the best approach but in the meantime, if you do not want to install gnome-shell-performance, you need to disable the cherry-pick below # clutter-actor: Add detail to captured-event signal [performance]
@Terence, no without it, should I install it after mutter-workaround before reboot?
@ValentinRO do you use gnome-shell-performance package as well?
Pinned Comments
Saren commented on 2018-08-30 14:52 (UTC) (edited on 2020-10-06 05:50 (UTC) by Saren)
If you are getting errors like
fatal: bad revision '73e8cf32'while building this package, refer to PKGBUILD and see which patches caused this. Then, go to the related URLs, replace the commit hashes. If there are conflicts, comment out the patches.Please notify me in comment section if this happens.
The optional performance patches are by default enabled.
A package for gnome-shell performance patches: https://aur.archlinux.org/packages/gnome-shell-performance/