Package Details: mutter-performance 1:47.4-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.077814
First Submitted: 2019-07-09 09:35 (UTC)
Last Updated: 2025-01-15 11:01 (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 .. 19 20 21 22 23 24 25 26 27 28 29 .. 64 Next › Last »

ciupenhauer commented on 2020-02-07 01:01 (UTC)

@glitsj16 no way did that just work!! :O It's crazy the performance difference I get in shell on my laptop with powersave governor. You are a Saint mate

glitsj16 commented on 2020-02-07 00:13 (UTC)

@ciupenhauer No clue why !724 hasn't been merged yet. But I did manage to find a way to include it without a manual rebase: (1) don't put !724 in the _merge_requests_to_use array; (2) add 'https://gitlab.gnome.org/GNOME/mutter/merge_requests/724.diff' to the source array and updpkgsums; (3) put this at the bottom of the prepare() function: 'patch -Np1 -i ../724.diff'; (4) additionally you might want to add these at the top of the build() function (cfr. mutter PKGBUILD): CFLAGS="${CFLAGS/-O2/-O3} -fno-semantic-interposition -fno-strict-aliasing" LDFLAGS+=" -Wl,-Bsymbolic"

ciupenhauer commented on 2020-02-06 23:34 (UTC)

does anyone know if !724 will get merged before release? I can't manage to build this with it, manual rebase seems tricky. Is there any reason it wasn't merged yet?

FuelFlo commented on 2020-02-03 19:14 (UTC)

@glitj16 thx! I just meant they'll also need to be updated in the package.

glitsj16 commented on 2020-02-03 17:16 (UTC)

@FuelFlo You can use these hashes:

  • for !983: pick_mr '!983' 9b7fe584 'merge'

  • for !1000: pick_mr '!1000' 62d608c2 'merge'

Additionally you can use '_commit=4959ae8bc4670cbd09c683d20fd07ded735e4dab # gnome-3-34'.

FuelFlo commented on 2020-02-03 17:08 (UTC)

Hey, the commit hashes of !983 and !1000 need to be fixed.

Terence commented on 2020-01-30 23:51 (UTC)

Thanks for the info glitsj16 and TheAimfam5. I will update this package and gnome-shell-performance over the weekend.

glitsj16 commented on 2020-01-30 23:30 (UTC)

FYI, !575 just got merged https://gitlab.gnome.org/GNOME/mutter/commit/2731be6929ca8b14e3b0ddf5fd2aebce722b5664 https://gitlab.gnome.org/GNOME/mutter/commit/5257c6ecc2d2c843ecc1ad5558e6a471eff5c7ee

theaifam5 commented on 2019-12-29 02:47 (UTC) (edited on 2019-12-29 02:51 (UTC) by theaifam5)

Just for info when someone gets same issue....

'!762' throws an error while compiling tests, when all (except '!429') are enabled:

/usr/bin/ld: /tmp/libmutter-clutter-5.so.0.0.0.ebY103.ltrans16.ltrans.o: in function `clutter_actor_continue_paint':
<artificial>:(.text+0x820f): undefined reference to `clutter_stage_get_no_clear_hint'
/usr/bin/ld: /tmp/libmutter-clutter-5.so.0.0.0.ebY103.ltrans6.ltrans.o: in function `clutter_stage_set_property':
<artificial>:(.text+0x7af0): undefined reference to `clutter_stage_set_no_clear_hint'
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.

'!429' throws an error, when all are enabled:

Merging latest commits for !429...
Found ^ for !429
fatal: bad revision '^..'

'!724' works for me, when all (except '!429' and '!762') are enabled