Package Details: mutter-performance 3.34.3+1+g78a45e181-4

Git Clone URL: (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:
Licenses: GPL
Groups: gnome
Conflicts: mutter
Provides: mutter, mutter-781835-workaround
Replaces: mutter-781835-workaround
Submitter: Terence
Maintainer: Terence (Saren)
Last Packager: Saren
Votes: 44
Popularity: 1.05
First Submitted: 2019-07-09 09:35
Last Updated: 2020-02-07 05:10

Dependencies (22)

Required by (12)

Sources (5)

Pinned Comments

Terence commented on 2019-06-10 19:14

If you are getting cogl/cogl/ ERROR: dependency glesv2 not found. or similar, install

Saren commented on 2018-08-30 14:52

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:

If applicable, $ touch ~/.i_dont_use_wayland_on_gnome and $ touch ~/.i_dont_use_multiple_keyboard_layouts for extra patches.

Latest Comments

1 2 3 4 5 6 ... Next › Last »

Saren commented on 2020-02-12 10:30

Oops, it seems like I pushed my pick which is not safe for everyone. If you are experiencing crashes or weird stuff because you are using Wayland/multiple monitors/keyboard layouts, use _merge_requests_to_use=('!575' '!983' '!1000') instead.

ciupenhauer commented on 2020-02-11 20:04

@glitsj16 sorry, meant the 3 !7xx MRs, bug doesn't happen with !719 & !762, without !724. All 3 need to be there at same time. Also noticed it only happens when you have external monitor plugged in

glitsj16 commented on 2020-02-11 19:24

@ciupenhauer Usually I'm on Wayland using mesa. I can reproduce the crash there. Never noticed it before because I have 'blank screen' set to 'Never' in the power saving settings. So thanks for mentioning it here. Not sure about the third MR involved you mention in your post, as I read !762 twice :) But I'm willing to experiment if you can throw that out here.

ciupenhauer commented on 2020-02-11 16:19

@glitsj16 are you on X or wayland? I get a crash on wayland when waking up the display from blank screen on Wayland with !719 and !762 and !762. Either !762 alone or the other 2 don't give this bug. Also no issue on X with all 3

glitsj16 commented on 2020-02-07 01:48

@ciupenhauer Glad to help. I only put those pieces together for !724 a few days ago. Actual credit (and sainthood perks) should go to for finding a way to easily incorporate MR patches (see Getting truly amazing performance here too now. I also use a GS extension from and I rarely see gnome-shell go over 4% CPU usage. Just putting this out here for who wants to give it a try.

ciupenhauer commented on 2020-02-07 01:01

@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

@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 '' 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

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

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

glitsj16 commented on 2020-02-03 17:16

@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'.