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

danitetus commented on 2018-11-27 16:52 (UTC) (edited on 2018-11-27 16:52 (UTC) by danitetus)

Build error

fatal: bad revision '68af9783'

m3thodic commented on 2018-11-26 09:14 (UTC) (edited on 2018-11-26 09:16 (UTC) by m3thodic)

Running the latest stock mutter from extra with only the following diffs from https://gitlab.gnome.org/GNOME/mutter/merge_requests/171 with (from what I can tell so far), decent results.

I backported the PR to patch cleanly with 3.30.2-1 which you can grab here for testing: https://gist.github.com/tonylambiris/eea7f90398e1a0a201a452e36b180277

  # Put the following line in prepare() right above NOCONFIGURE=1 ./autogen.sh
  patch -Np1 -F3 -i ../Sync-to-the-hardware-refresh-rate.patch

glorious-yellow commented on 2018-11-25 20:39 (UTC)

Also got "clutter: Fix offscreen-effect painting of clones" working, by downloading the patch file, removing the changes for meson.build, and applying the patch with git apply

glorious-yellow commented on 2018-11-22 19:45 (UTC) (edited on 2018-11-25 20:39 (UTC) by glorious-yellow)

Got "Geometric (GPU-less) picking" to work with git cherry-pick 0feecfe8 -X ours

Saren commented on 2018-11-19 05:01 (UTC)

@Terence ehh, nay.

Terence commented on 2018-11-18 12:53 (UTC)

@Saren an other way around would be to fork the mutter repo and apply the conflicting commits there. Yea or nay ?

Saren commented on 2018-11-17 11:14 (UTC)

@Terence it seems that patches would be better than git cherry-picking now...

Terence commented on 2018-11-16 17:02 (UTC)

@Saren it was working fine but vanvugt rebased all its PR from master, which now can't be applied as-is because of the meson support.. If you are fine with it, I'll do a patch approach for the commits concerned.

Saren commented on 2018-11-16 14:51 (UTC)

It's on fire, fixing...

Terence commented on 2018-11-15 14:55 (UTC)

@Saren I'm working on the new version :)

« First ‹ Previous 1 .. 46 47 48 49 50 51 52 53 54 55 56 .. 60 Next › Last »