Package Details: mutter-performance 1:46.1+r8+gc23274cd2-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
Groups: gnome
Conflicts: mutter
Provides: libmutter-14.so, mutter
Submitter: Terence
Maintainer: Terence (Saren, saltyming)
Last Packager: saltyming
Votes: 76
Popularity: 0.97
First Submitted: 2019-07-09 09:35 (UTC)
Last Updated: 2024-05-23 11:29 (UTC)

Required by (12)

Sources (7)

Pinned Comments

saltyming commented on 2022-03-22 09:37 (UTC) (edited on 2023-09-02 03:43 (UTC) by saltyming)

Please note that a debug option is disabled in this package.

To disable building the docs package, set an env: _disable_docs=y

To enable the check() process, set an env: _enable_check=y


If the building process is getting failed on check() like

83/114 mutter:core+mutter/backends/native / native-unit TIMEOUT 180.01s killed by signal 15 SIGTERM

then you might want to do one of these:

0) Unset an env: _enable_check=y

1) Kill your pipewire session manager; killall $(pacman -Qq pipewire-session-manager).

2) Reboot the machine.

3) Pass a variable --nocheck to makepkg (which can be passed along with --mflags first if you are using paru) to temporarily disable a check() process.

4) Add a line options=(!check) to the package's PKGBUILD file to disable a check() process.

And try again.

Terence commented on 2020-08-31 16:26 (UTC) (edited on 2020-08-31 16:26 (UTC) by Terence)

@NettoHikari or anyone unable to compile with the following error:

lto1: internal compiler error: bytecode stream: expected tag identifier_node instead of LTO_UNKNOWN

You need to rebuild sysprof and then try again.

Reference: https://bugs.archlinux.org/task/67686.

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 .. 47 48 49 50 51 52 53 54 55 56 57 .. 60 Next › Last »

caioalonso commented on 2018-11-09 13:59 (UTC) (edited on 2018-11-09 13:59 (UTC) by caioalonso)

fatal: bad revision 'd29a1c4a'

Commenting out lines 64 and 65 fixed it.

Saren commented on 2018-11-06 13:56 (UTC)

@jeckhack oops nice catch! Fixing in next package. I hope it does not cause issues...

jeckhack commented on 2018-11-05 01:17 (UTC)

I think you apply 216 twice in PKGBUILD. First time in cherry pick, then in git apply -3

Saren commented on 2018-11-03 09:16 (UTC)

@glorious-yellow just added that, thanks.

glorious-yellow commented on 2018-11-02 20:40 (UTC)

Found a very important patch:

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

This completely fixes the slowdown over time issue

wscsprint3r commented on 2018-10-24 17:03 (UTC)

This is a true game changer!

tannisroot commented on 2018-10-19 20:25 (UTC)

Ok. What about removing !168 then? It introduces very heavy stutter when dragging windows if you have a mouse with 1000hz polling rate.

glorious-yellow commented on 2018-10-18 21:02 (UTC)

@tannisroot According to the comments, MR 265 introduces some bugs. We should wait until it's stabilized before adding it.

tannisroot commented on 2018-10-18 18:11 (UTC)

This one should be very useful too: https://gitlab.gnome.org/GNOME/mutter/merge_requests/265/commits

glorious-yellow commented on 2018-10-17 20:40 (UTC)

@Saren You should make a meta package that installs both mutter-781835-workaround and gnome-shell-performance