| Git Clone URL: | https://aur.archlinux.org/mutter-performance.git (read-only, click to copy) |
|---|---|
| Package Base: | mutter-performance |
| Description: | A window manager for GNOME | Attempts to improve performances with non-upstreamed merge-requests and frequent stable branch resync |
| Upstream URL: | https://gitlab.gnome.org/GNOME/mutter |
| Licenses: | GPL-2.0-or-later |
| Groups: | gnome |
| Conflicts: | mutter |
| Provides: | libmutter-15.so, mutter |
| Submitter: | Terence |
| Maintainer: | Terence (Saren, saltyming) |
| Last Packager: | saltyming |
| Votes: | 78 |
| Popularity: | 0.183115 |
| First Submitted: | 2019-07-09 09:35 (UTC) |
| Last Updated: | 2024-10-22 08:26 (UTC) |
@Terence Getting the same error as @nik9 for !724, and I don't use the test part. It might be related to https://gitlab.gnome.org/GNOME/mutter/merge_requests/724#note_664956 (recent changes), not entirely sure.
On a similar vain, pick_mr '!762' e9ba9dc2 'merge' produces fatal: bad revision 'e9ba9dc2' I could fix this by changing to: pick_mr '!762' 'renderer-native: Check that frame_info != NULL' from https://gitlab.gnome.org/GNOME/mutter/merge_requests/762#note_664985
@nik9 I think this is just the test part? It should work if you use makepkg --nocheck
FAILED: clutter/clutter/libmutter-clutter-5.so.0.0.0 when !724 is enabled
@glitsj16 Forgot to remove it from the array. It was merged and then cherry-picked to gnome-3-34.
What's up with !909? In the history I see it was added [url=https://aur.archlinux.org/cgit/aur.git/commit/?h=mutter-performance&id=c72a386e79d4]here[/url], subsequently got [url=https://aur.archlinux.org/cgit/aur.git/commit/?h=mutter-performance&id=7856f09de6c8]removed[/url] but it is still in the [color=blue]_merge_requests_to_use[/color] array...
I tried reviving !909 in its prior form (pick_mr '!909' b1b7c597^..765c8a3a 'merge') but that throws a [color=crimson]fatal: bad revision 'b1b7c597^..765c8a3a'[/color] message. When using it like [color=steelblue]pick_mr '!909' "x11-display: Don't unset the X11 focused window after setting one"[/color] (mind the double-quote to not break on the single quote inside the title) efe5bed5b is found for !909 and the build happily proceeds. Can someone confirm whether or not !909 should still be referenced in the array?
No issues here with !719 & !762. NVIDIA 440, 1080Ti, Manjaro
@Saren sorry but creating a file in your home like that is awful. What can be done instead as you mentioned is creating an ENV containing the PR the PKGBUILD would check and use.
Well, editing PKGBUILD every update VS creating a file once and forget it, I prefer the latter. Maybe I could make use of environment variables (/etc/environment) next update.
Ah, yes, very nice with the array!
@TheAifam5 @gedgon @ciupenhaue I added!719 and !762 which fixes one issue of !719. You need to add them to the _merge_requests_to_use array.
Pinned Comments
saltyming commented on 2022-03-22 09:37 (UTC) (edited on 2024-10-22 08:27 (UTC) by saltyming)
If you have a problem during any system update with
mutter-performance&gnome-shell-performance, please installmutter&gnome-shellpackages from the main repository and do full upgrade first, then build the performance packages later.If you are using [gnome-unstable] and [extra-testing] repositories, use mutter-performance-unstable
The default patch list includes "Dynamic triple buffering(!1441)", "text-input-v1(!3751)".
Latest Dynamic triple buffering patch has several included MRs from the main development branch to achieve maximum performance.
To enable a specific MR in the Merge Requests List, add an line "_merge_requests_to_use+=('<MR number>')" at the end of PKGBUILD. (Because if you edit the line directly you can be able to end up with merge conflict upon updates.)
You can see some patches' git history here: https://git.saltyming.net/sungmg/mutter-performance-source/
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/