| Git Clone URL: | https://aur.archlinux.org/mutter-performance.git (read-only, click to copy) |
|---|---|
| Package Base: | mutter-performance |
| Description: | Window manager and compositor for GNOME |
| Upstream URL: | https://gitlab.gnome.org/GNOME/mutter |
| Licenses: | GPL-2.0-or-later |
| Groups: | gnome |
| Conflicts: | mutter |
| Provides: | libmutter-16.so, mutter |
| Submitter: | Terence |
| Maintainer: | glorious-yellow |
| Last Packager: | glorious-yellow |
| Votes: | 76 |
| Popularity: | 0.013505 |
| First Submitted: | 2019-07-09 09:35 (UTC) |
| Last Updated: | 2025-04-14 05:13 (UTC) |
Running the latest stock mutter from extra with only the following diffs from https://gitlab.gnome.org/GNOME/mutter/merge_requests/171 with (from what I can tell so far), decent results.
I backported the PR to patch cleanly with 3.30.2-1 which you can grab here for testing: https://gist.github.com/tonylambiris/eea7f90398e1a0a201a452e36b180277
# Put the following line in prepare() right above NOCONFIGURE=1 ./autogen.sh
patch -Np1 -F3 -i ../Sync-to-the-hardware-refresh-rate.patch
Also got "clutter: Fix offscreen-effect painting of clones" working, by downloading the patch file, removing the changes for meson.build, and applying the patch with git apply
Got "Geometric (GPU-less) picking" to work with git cherry-pick 0feecfe8 -X ours
@Terence ehh, nay.
@Saren an other way around would be to fork the mutter repo and apply the conflicting commits there. Yea or nay ?
@Terence it seems that patches would be better than git cherry-picking now...
@Saren it was working fine but vanvugt rebased all its PR from master, which now can't be applied as-is because of the meson support.. If you are fine with it, I'll do a patch approach for the commits concerned.
It's on fire, fixing...
@Saren I'm working on the new version :)
fatal: bad revision 'd29a1c4a'
Commenting out lines 64 and 65 fixed it.
Pinned Comments
<deleted-account> commented on 2023-05-02 11:11 (UTC)
gnome-44 diffs: https://gist.github.com/FiestaLake/aaf26db49292840aef43210001b4e080
For people using [staging] & [gnome-unstable] branch (or [testing] branch in the near future).
Apply the patch with
git am {patchname}.patch<deleted-account> commented on 2023-02-13 04:41 (UTC)
Hi, I'm the co-maintainer of the package.
Unfortunately, my laptop's gpu died a few days ago. So I cannot bring lots of changes to the package. The only thing I can do right now is upgrading the package along with mr1441 only.
Sorry for the situation and I hope you understand it. If you want to be a co-maintainer of this package, please contact fiestalake@disroot.org and/or the other maintainers. Thanks.
<deleted-account> commented on 2022-10-27 15:54 (UTC)
gnome-43 diffs: https://gist.github.com/FiestaLake/d6d9e597fe693b3f55d92890880e463c
For people using [testing] branch.
Apply the patch with
git am {patchname}.patchSaren 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/