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

tannisroot commented on 2018-10-17 18:51 (UTC)

I suggest to add this patch too: https://gitlab.gnome.org/GNOME/mutter/merge_requests/216/commits

jc-aur commented on 2018-10-15 08:02 (UTC)

@tannisroot sorry, just got back home. Yes, I have a Logitech G502, if I recall right it has 1000Hz polling rate, why? Just for curiosity sake, I disconnected it, used the mouse pad from the laptop and suddenly the experience was a lot better, why is so?

tannisroot commented on 2018-10-14 21:24 (UTC)

@jc-aur do you happen to have a mouse with 1000hz polling rate?

jc-aur commented on 2018-10-14 21:08 (UTC) (edited on 2018-10-14 21:09 (UTC) by jc-aur)

@Vash63 @glorious-yellow I'm experiencing the same performance as @tannisroot, everything works buttery-smooth but moving windows around, especially when moving a window between monitors. I'm running a Nvidia GTX 980M with the latest driver, running on Xorg

glorious-yellow commented on 2018-10-14 19:32 (UTC)

@Vash63 Interesting, for me only maximize/minimize animations are laggy

Vash63 commented on 2018-10-14 19:25 (UTC)

Follow up to @tannisroot's comment, was debugging this with him in discord while we were testing this patch set. It seems to be commit 0feecfe8 causing the problems - after I commented that out the performance problems went away.

Specifically, the performance seemed to get very very bad if two large windows were on top of each other while you moved them. Single digit framerates.

Otherwise, this package is awesome and once I disabled that patch it's noticeably smoother than stock mutter.

tannisroot commented on 2018-10-14 18:25 (UTC) (edited on 2018-10-14 18:25 (UTC) by tannisroot)

I've tried this and everything is buttery smooth, except for moving windows around. When I move them it is very, very laggy. Any idea why? I have GTX 1070 and use 396.54.09 driver.

v-tin commented on 2018-10-14 14:09 (UTC)

@Saren After you did disabled the patch, it worked now. I mean, you really do see the difference in smoothness, responses.. nice work, much appreciated. :D

Saren commented on 2018-10-14 06:48 (UTC) (edited on 2018-10-14 06:48 (UTC) by Saren)

@jc-aur Done, thanks for suggesting that.

@glorious-yellow I will see what I can do at next package update.

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