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.186852
First Submitted: 2019-07-09 09:35 (UTC)
Last Updated: 2024-10-22 08:26 (UTC)

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

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]

Saren commented on 2019-03-24 07:04 (UTC)

@Terence We could detect whether gnome-shell-performance is installed and apply patches or not, just like what gnome-shell-performance is currently detecting mutter-781835-workaround to decide applying MR276 or not.

However it would be a catch 22 as they will be detecting each other...

Terence commented on 2019-03-23 21:52 (UTC) (edited on 2019-03-23 21:52 (UTC) by Terence)

@Saren ValentinRO pointed out an important issue we need to think about...

@ValentinRO yeah.

v-tin commented on 2019-03-23 20:52 (UTC) (edited on 2019-03-23 21:25 (UTC) by v-tin)

@Terence, Well, I was planning to install it too, only wasn't sure if it was included in mutter-workaround or not, it brought me to confusion when I read:

The optional performance patches are by default enabled.
The patch indicated by https://gitlab.gnome.org/GNOME/mutter/merge_requests/70/commits is the one Ubuntu 18.04 currently using.
A package for gnome-shell performance patches: https://aur.archlinux.org/packages/gnome-shell-performance/

I guess you get more benefit with gnome-shell-performance installed than without?

Terence commented on 2019-03-23 19:55 (UTC)

@ValentinRO I'm trying to figure out what is the best approach but in the meantime, if you do not want to install gnome-shell-performance, you need to disable the cherry-pick below # clutter-actor: Add detail to captured-event signal [performance]

v-tin commented on 2019-03-23 17:41 (UTC)

@Terence, no without it, should I install it after mutter-workaround before reboot?

Terence commented on 2019-03-23 17:13 (UTC)

@ValentinRO do you use gnome-shell-performance package as well?

v-tin commented on 2019-03-23 17:08 (UTC) (edited on 2019-03-23 17:09 (UTC) by v-tin)

I have deleted my comment by accident.

Here is my install log. After reboot, I get a blank screen with a keyring unlock screen. After that, it's still blank with a cross cursor.

With ctrl-alt-f3, I managed to put back the default mutter. Any idea what it could be?

https://pastebin.com/3xhMmX3N

Terence commented on 2019-03-23 16:08 (UTC)

@emaxoda @tannisroot I pushed a fix for the version problem, please try again.

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