| 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) |
Should have been fixed in gnome-42 base.
Below is just for users of gnome-41 based packages.
!1441 is not ready for multi-display support (in Wayland) now.
You'd better not use this package or change _merge_requests_to_use= in PKGBUILD not to use !1441.
Workaround for the Wayland Multi-display freezing issue :
-> Add MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 in ~/.config/environment.d/envvars.conf
Source : https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_1265504
By @JordanViknar
Hey, I'm having the same problem as @JordanViknar,
the second monitor freezes for me, as soon as I open the first window of any program. Happens for me with mutter-performance (also with the changed commit) as well as with mutter-dynamic-buffering, but not with the original mutter package.
@JordanViknar Test mutter-dynamic-buffering aur package and tell me the result.
I was already compiling with makepkg due to issues with this particular package on my usual AUR helpers (pamac and yay) (I can confirm I'm using Arch Linux and not Manjaro despite having Pamac).
The latest version didn't fix the issue, it did "reverse" it though (it was now the primary display getting stuck instead of the non-primary one).
I couldn't try your alternative commit, because the build was failing on the checks following the compilation (I tried yesterday and I already forgot the specific element that was failing, but it was somewhere between the 100th and 110th check, I can try again if that'd help you).
Also, I don't know if that's related, but I'm using the gdm-plymouth and libgdm-plymouth packages.
@JordanViknar Please test the latest version and if it doesn't help, change
_commit=561ec4f3e722ea365c535aea4e03b496b20cb8c9 # tags/41.1^25
to
_commit=8de96d3d7c40e6b5289fd707fdd5e6d604f33e8f # tags/41.1^0
in PKGBUILD and try building & installing it via makepkg -sric
@JordanViknar Did it work with the previous verison?
I'd like to warn the maintainers (and users) of this package that it has caused me issues when used with a secondary monitor. If you combine both screens, only the primary display will work properly : the other display will just freeze on one of the first few frames, and it will not unfreeze until you change the mode. I was using it alongside gnome-shell-performance, and while uninstalling gnome-shell-performance did not fix the problem, uninstalling this package did solve it. I can only assume then that the problem is caused by one of the patches applied to mutter in this package.
System Info that might be useful :
CPU : Intel Celeron N3450 (4) @ 2.200GHz
GPU : Intel HD Graphics 500
Kernel : 5.15.4-zen1-1-zen
(On a side note, it is quite effective at boosting performance, even more than gnome-shell-performance. If you don't have secondary monitors, feel free to install it.)
This package, together with gnome-shell-performance, drastically improved the GNOME performance for me. No more stuttering animations. Thank you!
Hi, I'm a new co-maintainer of gnome-shell-performance and mutter-performance packages. Please don't hesitate to give us/me advice and bug reports.
Thanks.
@Terence
Whether you are able to continue maintenance of this package or not can I just say a huge thank you for the work you have put into this! It has been the difference between a show-stoppingly juddery desktop and one that was a joy to work with.
Thank you.
I hope we are able to find a maintainer :o)
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/