Package Details: mutter-performance 1:47.0+r18+g625965d95-1

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.99
First Submitted: 2019-07-09 09:35 (UTC)
Last Updated: 2024-09-21 16:33 (UTC)

Required by (18)

Sources (5)

Pinned Comments

saltyming commented on 2022-03-22 09:37 (UTC) (edited on 2024-09-20 11:57 (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 to achieve maximum performance (!4015).

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 2 3 4 5 6 7 8 9 10 11 .. 64 Next › Last »

saltyming commented on 2024-01-15 13:25 (UTC)

@NGStaph Done.

NGStaph commented on 2024-01-15 05:19 (UTC)

consider adding #3304 https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3304

saltyming commented on 2024-01-11 13:25 (UTC)

@ewout not available in stable branch (45) yet. Tho I will try cherry-picking it later.

ewout commented on 2023-12-13 13:02 (UTC)

Consider including MR !3448 if possible.

m_perf commented on 2023-12-05 09:16 (UTC) (edited on 2023-12-05 09:17 (UTC) by m_perf)

@willov There's already such option: you need to add '579' to _merge_requests_to_use, it will revert the offending commit.

If you use an AUR helper, I suggest you to do so by adding a new line containing: _merge_requests_to_use+=('579'). (Because if you edit the line directly you'll end up with merge conflict upon updates)

willov commented on 2023-11-24 05:50 (UTC) (edited on 2023-11-24 05:51 (UTC) by willov)

I recently discovered the source of my stuttering problem when using an multibutton/MMO mouse. In short, pressing keys on two different keyboards triggers a reload, which introduces lag. The solution is proposed here: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1858#note_818548

Essentially, remove the line case XkbNewKeyboardNotify: from ./src/backends/x11/meta-backend-x11.c. I edited the PKGBUILD to contain sed -i '/case XkbNewKeyboardNotify:/d' src/backends/x11/meta-backend-x11.c at the end of the prepare phase, and it immediately removed the stuttering.

Perhaps this can be included optionally (e.g. with an environment variable)? It might be detrimental to people using multiple keyboards with different layouts, bit it is a massive improvement for people with MMO-mice.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 .. 64 Next › Last »