Arch Linux User Repository

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.

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

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/

@kal I think it's because gnome itself is getting faster than before. It still boosts performance in my low-spec machine.

You can also try gnome-shell-performance to see if this works for you too.

First of all thanks so much guys for your work on this package it makes such a difference day-to-day!

Anyway, after upgrading to Gnome 42, mutter-performance appears to build and install fine. However, in use, it seems to make no difference?! Under Gnome 41, silky smooth but with Gnome 42 it's almost as if the patch is not being applied at all - strange.

Do you think I am doing something wrong? Any help would be appreciated.

Thank you.

@laurentrepond Reboot the machine and try building the package again.

Or add --nocheck option when building the package.

Hangs on:

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

with:

stderr:
Starting D-Bus daemons (session & system)...
Starting mocked services...
Running test case...
mutter-Message: 10:05:56.452: Running Mutter Test (using mutter 42.0) as a Wayland display server
mutter-Message: 10:05:56.460: Added device '/dev/dri/renderD128' (i915) using no mode setting.
mutter-Message: 10:05:56.479: Created gbm renderer for '/dev/dri/renderD128'
mutter-Message: 10:05:56.479: Boot VGA GPU /dev/dri/renderD128 selected as primary
mutter-Message: 10:05:56.489: Using Wayland display name 'mutter-test-display'
Window manager warning: Failed to set environment variable WAYLAND_DISPLAY for gnome-session: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.SessionManager" does not exist
mutter-Message: 10:05:56.495: Added virtual monitor Meta-0
mutter-Message: 10:05:56.640: Removed virtual monitor Meta-0

The package build gets stuck on "[1168/1173] Linking target src/tests/mutter-monitor-unit"

Does anyone has the same issue?

@ewout This also happens in the official package. Maybe you should make a bug report to the package's maintainer.

File "/usr/lib/mutter-10/plugins/libdefault.so" from package "mutter-performance" is missing dependency "libmutter-clutter-10.so.0"

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.

@abrattic I guess the crash is from backported !1441.

Unfortunately, !1441 is synced to mutter 42 now, so backport to 41 is unlikely trivial.