Package Details: mutter-performance 1:47.3-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.172346
First Submitted: 2019-07-09 09:35 (UTC)
Last Updated: 2024-12-23 10:16 (UTC)

Dependencies (66)

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 .. 50 51 52 53 54 55 56 57 58 59 60 .. 64 Next › Last »

tannisroot commented on 2018-12-07 09:48 (UTC)

also GPU-less picking and clutter patches compatible with 3.30: https://gitlab.gnome.org/GNOME/mutter/merge_requests/189#note_380775

tannisroot commented on 2018-12-03 22:21 (UTC) (edited on 2018-12-07 09:48 (UTC) by tannisroot)

You can use this to resolve conflict with "Sync to the hardware refresh rate, not just 60.00Hz [performance]": https://gitlab.gnome.org/GNOME/mutter/merge_requests/318/commits

A.J commented on 2018-11-30 14:32 (UTC)

still there is error :

fatal: bad revision '68af9783'

it can build with it commented out .

danitetus commented on 2018-11-27 16:52 (UTC) (edited on 2018-11-27 16:52 (UTC) by danitetus)

Build error

fatal: bad revision '68af9783'

m3thodic commented on 2018-11-26 09:14 (UTC) (edited on 2018-11-26 09:16 (UTC) by m3thodic)

Running the latest stock mutter from extra with only the following diffs from https://gitlab.gnome.org/GNOME/mutter/merge_requests/171 with (from what I can tell so far), decent results.

I backported the PR to patch cleanly with 3.30.2-1 which you can grab here for testing: https://gist.github.com/tonylambiris/eea7f90398e1a0a201a452e36b180277

  # Put the following line in prepare() right above NOCONFIGURE=1 ./autogen.sh
  patch -Np1 -F3 -i ../Sync-to-the-hardware-refresh-rate.patch

glorious-yellow commented on 2018-11-25 20:39 (UTC)

Also got "clutter: Fix offscreen-effect painting of clones" working, by downloading the patch file, removing the changes for meson.build, and applying the patch with git apply

glorious-yellow commented on 2018-11-22 19:45 (UTC) (edited on 2018-11-25 20:39 (UTC) by glorious-yellow)

Got "Geometric (GPU-less) picking" to work with git cherry-pick 0feecfe8 -X ours

Saren commented on 2018-11-19 05:01 (UTC)

@Terence ehh, nay.

Terence commented on 2018-11-18 12:53 (UTC)

@Saren an other way around would be to fork the mutter repo and apply the conflicting commits there. Yea or nay ?

Saren commented on 2018-11-17 11:14 (UTC)

@Terence it seems that patches would be better than git cherry-picking now...

« First ‹ Previous 1 .. 50 51 52 53 54 55 56 57 58 59 60 .. 64 Next › Last »