Package Base Details: mutter-performance

Git Clone URL: https://aur.archlinux.org/mutter-performance.git (read-only, click to copy)
Submitter: Terence
Maintainer: Terence (Saren, saltyming)
Last Packager: saltyming
Votes: 76
Popularity: 1.43
First Submitted: 2019-07-09 09:35 (UTC)
Last Updated: 2024-05-05 05:39 (UTC)

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 2 3 4 5 6 7 .. 59 Next › Last »

NGStaph commented on 2024-01-15 05:19 (UTC)

consider adding #3304 https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3304

saltyming commented on 2024-01-11 13:25 (UTC)

@ewout not available in stable branch (45) yet. Tho I will try cherry-picking it later.

ewout commented on 2023-12-13 13:02 (UTC)

Consider including MR !3448 if possible.

m_perf commented on 2023-12-05 09:16 (UTC) (edited on 2023-12-05 09:17 (UTC) by m_perf)

@willov There's already such option: you need to add '579' to _merge_requests_to_use, it will revert the offending commit.

If you use an AUR helper, I suggest you to do so by adding a new line containing: _merge_requests_to_use+=('579'). (Because if you edit the line directly you'll end up with merge conflict upon updates)

willov commented on 2023-11-24 05:50 (UTC) (edited on 2023-11-24 05:51 (UTC) by willov)

I recently discovered the source of my stuttering problem when using an multibutton/MMO mouse. In short, pressing keys on two different keyboards triggers a reload, which introduces lag. The solution is proposed here: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1858#note_818548

Essentially, remove the line case XkbNewKeyboardNotify: from ./src/backends/x11/meta-backend-x11.c. I edited the PKGBUILD to contain sed -i '/case XkbNewKeyboardNotify:/d' src/backends/x11/meta-backend-x11.c at the end of the prepare phase, and it immediately removed the stuttering.

Perhaps this can be included optionally (e.g. with an environment variable)? It might be detrimental to people using multiple keyboards with different layouts, bit it is a massive improvement for people with MMO-mice.

« First ‹ Previous 1 2 3 4 5 6 7 .. 59 Next › Last »