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.186852
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 .. 34 35 36 37 38 39 40 41 42 43 44 .. 64 Next › Last »

deezid commented on 2019-05-04 11:50 (UTC)

@Terence, disabled !460 and the framedrops I mentioned earlier are gone. Maybe it's updated pkgbuild though? Not sure

Saren commented on 2019-05-04 05:25 (UTC)

@Terence if it does not hurt us in anyway, keep it.

Terence commented on 2019-05-03 21:14 (UTC)

@Saren I figured out !460 is Wayland-only and its purpose is to keep the shell snappy while cpu-hungry tasks are running. Should we still keep it?

Terence commented on 2019-05-03 16:30 (UTC)

@Saren yeah didn't think it all through with the branch change... I reverted it for gnome-shell as well and fixed conflicts.

deezid commented on 2019-05-03 16:06 (UTC) (edited on 2019-05-03 16:08 (UTC) by deezid)

Overall what I noticed is that there's basically no lag anymore but some frame drops here and there, especially in apps like Chrome while scrolling. 4K60p and even 8K in YouTube is fine though.

deezid commented on 2019-05-03 16:04 (UTC)

Latest build works fine here.

Terence commented on 2019-04-30 21:43 (UTC)

@Tio There is no error shown in your log and please report back without using an aur helper.

Tio commented on 2019-04-30 21:35 (UTC)

Error

Synchronizing package databases...
Starting full system upgrade...
Cloning mutter-781835-workaround build files...
Checking mutter-781835-workaround dependencies...
Building mutter-781835-workaround...
==> Making package: mutter-781835-workaround 3.32.1+3+g9a795d3d0-1 (mar 30 abr 2019 23:34:44 CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Cloning mutter-781835-workaround git repo...
Cloning into bare repository '/tmp/pamac-build/mutter-781835-workaround/mutter-781835-workaround'...

Saren commented on 2019-04-30 12:21 (UTC)

@terence I saw you switched the git from a commit to a branch, this will hurt... I am getting conflicts that is unable to build for now, making a rel=2 soon.

kode54 commented on 2019-04-11 06:42 (UTC)

Replace revision f5a1ec1c with 34fae0f5. This is only going to keep hurting more and more, as all of @vanvugt's PRs keep getting rebased constantly instead of getting accepted.

« First ‹ Previous 1 .. 34 35 36 37 38 39 40 41 42 43 44 .. 64 Next › Last »