Package Details: mutter-performance 1:47.1.r2.g74cf8ac0f-2

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)

Required by (16)

Sources (4)

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 install mutter & gnome-shell packages 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/

Latest Comments

« First ‹ Previous 1 .. 31 32 33 34 35 36 37 38 39 40 41 .. 64 Next › Last »

Saren commented on 2019-05-31 15:32 (UTC)

@Terence I understand. We just need a way to rename package without losing all the users and stuff...

Terence commented on 2019-05-31 14:32 (UTC)

Our lord and savior vanvugt just published https://gitlab.gnome.org/GNOME/mutter/merge_requests/602 that should fix the last stuttering problems. It is taking the role of what the revert patch was doing and thus confirming that it's safe to use it thanks to his other MRs.

@Saren We should really consider renaming the package to something like mutter-performance to align it to gnome-shell-performance as what it was primarily made for is now fixed.

Terence commented on 2019-05-31 14:26 (UTC)

@kode54 I fixed it, thanks.

kode54 commented on 2019-05-30 01:58 (UTC)

Mutter !579 was merged 5 days ago, so the cherry-pick on 8ba1e42c is no longer applicable, and needs to be removed from the prepare process for the build to succeed.

Terence commented on 2019-05-22 22:17 (UTC)

@deezid ok I'll keep the patch for now but you might want to check if your issue as been reported ans if not create new one.

deezid commented on 2019-05-22 22:14 (UTC)

@Terence: Still need the nvidia revert patch to have smooth zoom animations when using the mouse in shell. Compiled two different versions and without the patch the zoom animation is always laggy...

archenoah commented on 2019-05-21 09:48 (UTC)

had to uncomment: git cherry-pick -n b3192d6b

Terence commented on 2019-05-16 13:28 (UTC)

@glorious-yellow: I don't want to enable it by default for Nvidia users.

glorious-yellow commented on 2019-05-14 19:56 (UTC)

I think we can do: pacman -Q nvidia && _revert=1

Terence commented on 2019-05-13 20:01 (UTC)

@DeadMetaler This sounds like a gnome-shell performance problem. Please check if this is the same as https://gitlab.gnome.org/GNOME/gnome-shell/issues/1271. Otherwise, consider opening a new issue about it.

In the end I'd really like to get rid of the 781835-workaround because reverting it means anything making use of https://www.linuxtopia.org/online_books/gui_toolkit_guides/gtk+_gnome_application_development/sec-mainloop_3.html will hang/never be called.