Package Details: mutter-performance 1:46.2+r6+g62e559d75-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.84
First Submitted: 2019-07-09 09:35 (UTC)
Last Updated: 2024-05-31 11:54 (UTC)

Required by (12)

Sources (4)

Pinned Comments

saltyming commented on 2022-03-22 09:37 (UTC) (edited on 2024-05-26 07:35 (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. Note that it can be problematic in some versions/setups.

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 may 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 the check() process.

4) Add a line options=(!check) to the package's PKGBUILD file to disable the 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 .. 4 5 6 7 8 9 10 11 12 13 14 .. 60 Next › Last »

kal commented on 2022-05-21 22:33 (UTC)

Does this patch still work on X11/Intel ? For me, on Wayland - silky smooth but X11 is stuttery :-(

Thanks in advance!

saltyming commented on 2022-05-20 11:53 (UTC)

@allexj It depends on performance of your machine.

allexj commented on 2022-05-15 17:17 (UTC)

This package does not help fixing the animation lag (reported here: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3760 )

saltyming commented on 2022-05-04 07:50 (UTC)

@gandalfmagic Done.

gandalfmagic commented on 2022-05-03 17:33 (UTC) (edited on 2022-05-03 17:34 (UTC) by gandalfmagic)

Hi, this update (42.0+r93+g5e5480e62-1) breaks the mouse cursor on some configurations (mostly nvidia with wayland gbm it seems).

Here is the issue on the bug-tracker: https://gitlab.gnome.org/GNOME/mutter/-/issues/2250

This MR should solve the problem: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2397

Thank you

saltyming commented on 2022-05-03 14:41 (UTC)

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

kal commented on 2022-05-03 14:33 (UTC)

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.

saltyming commented on 2022-04-21 09:25 (UTC)

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

Or add --nocheck option when building the package.

laurentrepond commented on 2022-04-21 09:23 (UTC)

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

frandieguez commented on 2022-04-19 08:50 (UTC)

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

Does anyone has the same issue?

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 60 Next › Last »