Package Details: mutter-performance 1:47.1.r2.g74cf8ac0f-2

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-2.0-or-later
Groups: gnome
Conflicts: mutter
Provides: libmutter-15.so, mutter
Submitter: Terence
Maintainer: Terence (Saren, saltyming)
Last Packager: saltyming
Votes: 78
Popularity: 0.36
First Submitted: 2019-07-09 09:35 (UTC)
Last Updated: 2024-10-22 08:26 (UTC)

Dependencies (66)

Required by (16)

Sources (4)

Pinned Comments

saltyming commented on 2022-03-22 09:37 (UTC) (edited on 2024-10-22 08:27 (UTC) by saltyming)

If you have a problem during any system update with mutter-performance & gnome-shell-performance, please install mutter & gnome-shell packages from the main repository and do full upgrade first, then build the performance packages later.

If you are using [gnome-unstable] and [extra-testing] repositories, use mutter-performance-unstable

The default patch list includes "Dynamic triple buffering(!1441)", "text-input-v1(!3751)".

Latest Dynamic triple buffering patch has several included MRs from the main development branch to achieve maximum performance.

To enable a specific MR in the Merge Requests List, add an line "_merge_requests_to_use+=('<MR number>')" at the end of PKGBUILD. (Because if you edit the line directly you can be able to end up with merge conflict upon updates.)

You can see some patches' git history here: https://git.saltyming.net/sungmg/mutter-performance-source/

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 .. 35 36 37 38 39 40 41 42 43 44 45 .. 64 Next › Last »

Terence commented on 2019-04-04 02:38 (UTC)

@flomax Thanks for reporting, it should be fixed.

flomax commented on 2019-04-03 23:07 (UTC) (edited on 2019-04-03 23:08 (UTC) by flomax)

Getting fatal: bad revision '14a27e87^..a40d7927'

Replacing a40d7927 with 6474593e or 966e062d did not fix, but build completes once whole line is commented out.

Terence commented on 2019-03-31 01:19 (UTC)

@Saren oups my bad! Updated so it doesn't apply by default.

Saren commented on 2019-03-30 14:09 (UTC)

@Terence Did you mean without _revert=0? _revert=0 still applies the patch I guess.

Terence commented on 2019-03-30 11:03 (UTC)

Thanks @ciupenhauer and @deezid for the heads-up, updated. @Saren this should render the commit revert useless. Can you try again with _revert=0 and report back?

deezid commented on 2019-03-28 20:08 (UTC)

@clupenhauer. That's what I thought. Skip the first !281 commit. https://bugzilla.gnome.org/show_bug.cgi?id=789186#c18

  # clutter-stage-cogl: Reduce output latency and reduce missed frames too [performance]
  # first commit replaced by !363
  # https://gitlab.gnome.org/GNOME/mutter/merge_requests/281
  git cherry-pick -n 186f16f8

  # Consolidate all frame throttling into clutter-stage-cogl [performance]
  # https://gitlab.gnome.org/GNOME/mutter/merge_requests/363
  git cherry-pick -n 577084a4^..c71e6523

ciupenhauer commented on 2019-03-28 20:05 (UTC)

According to Daniel van Vugt: "Also note the second commit of https://gitlab.gnome.org/GNOME/mutter/merge_requests/363 provides a fix for this bug too. It replaces the first commit of https://gitlab.gnome.org/GNOME/mutter/merge_requests/281"

Does that mean we can safely switch off patch 281 and use only 363?

v-tin commented on 2019-03-25 06:18 (UTC)

@Saren, Aha, thank you for the info.

Saren commented on 2019-03-24 18:23 (UTC)

@ValentinRO It is 3.32 that broke the extensions. The patches we added change low-level things that is very very unlikely related to shell extensions. Many of your extensions should have update for 3.32, if not look into github or even issues, most of the time you can change some files to get your extensions working again.

v-tin commented on 2019-03-24 09:50 (UTC)

@Terence, this time I managed to install both mutter-workaround & shell-performance with clean os install (without touching settings in nvidia app).

See install log, you will see that I have manually updated the gsettings-desktop-schemas too: https://pastebin.com/gPJThqkD

Unfortunately, this broke some gnome extensions, I'm not sure if it is related to shell-performance.

This are the list which broke the extensions: https://extensions.gnome.org/extension/1362/custom-hot-corners/ https://extensions.gnome.org/extension/307/dash-to-dock/ https://extensions.gnome.org/extension/7/removable-drive-menu/

Furthermore, I got also update notification on the extension (which it won't update even if it says so): https://extensions.gnome.org/extension/19/user-themes/ https://extensions.gnome.org/extension/307/dash-to-dock/ https://extensions.gnome.org/extension/7/removable-drive-menu/

If this is related to shell-performance and to avoid headache, I will try this time only with mutter-workaround, with cherry-pick disabled # clutter-actor: Add detail to captured-event signal [performance]

« First ‹ Previous 1 .. 35 36 37 38 39 40 41 42 43 44 45 .. 64 Next › Last »