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 .. 28 29 30 31 32 33 34 35 36 37 38 .. 64 Next › Last »

Saren commented on 2019-07-04 15:30 (UTC)

Yo, just going to say that I get 60fps at almost all time now with nvidia card.

glorious-yellow commented on 2019-07-02 17:36 (UTC) (edited on 2019-07-02 17:36 (UTC) by glorious-yellow)

@ismet

If you go to https://gitlab.gnome.org/GNOME/mutter/merge_requests/189/commits, you can see that the new commit hash is 76462a2f.

Replace 00b4dace with 76462a2f in PKGBUILD and it should work.

ismet commented on 2019-07-02 17:31 (UTC)

I'm getting "fatal: bad revision '00b4dace'" error while building the package. I referred to PKGBUILD and went to related URL (https://gitlab.gnome.org/GNOME/mutter/merge_requests/189). But, I didn't understand what to do next. How can I replace the commit hashes as @Saren mentioned?

Vash63 commented on 2019-07-01 12:01 (UTC)

https://gitlab.gnome.org/GNOME/mutter/merge_requests/661

Another new MR that looks promising, supposed to fix the regressions that !168 had

Terence commented on 2019-06-20 13:48 (UTC)

@alex4401 @deezid Thanks, updated.

deezid commented on 2019-06-20 13:02 (UTC)

@Terence: !602 has been updated to df38ad3c !168 has been updated to 657cb4b5

alex4401 commented on 2019-06-20 11:54 (UTC)

"cogl: Remove GLX "threaded swap wait" used on Nvidia [performance]" (MR602) breaks the build (bad revision 'f12eddc1')

Terence commented on 2019-06-17 16:57 (UTC)

Weird mwohah, please report your findings in the issue.

Gert-dev commented on 2019-06-17 16:16 (UTC)

FYI, I was looking into reporting the broken keybindings issue, but I noticed that it may not be due to 579, after all. I seem to only get this issue sporadically. I got it once with 579 disabled, but it seems to happen more often with 579 enabled.

It seems to be fixable by refreshing GNOME shell (Alt+F2 and "r").

Terence commented on 2019-06-13 12:05 (UTC)

@deezid Thanks for the report, I knew about !568, I was waiting for my issue to be resolved to merge it but now it looks good :)

« First ‹ Previous 1 .. 28 29 30 31 32 33 34 35 36 37 38 .. 64 Next › Last »