Package updated with cleanups and synced with master.
Search Criteria
Package Details: mutter-performance 1:47.4-1
Package Actions
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.077814 |
First Submitted: | 2019-07-09 09:35 (UTC) |
Last Updated: | 2025-01-15 11:01 (UTC) |
Dependencies (66)
- at-spi2-core (at-spi2-core-gitAUR)
- cairo (cairo-gitAUR)
- colord (colord-gitAUR)
- dconf
- fontconfig (fontconfig-gitAUR, fontconfig-ubuntuAUR)
- fribidi (fribidi-gitAUR)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-snapshotAUR)
- gdk-pixbuf2 (gdk-pixbuf2-gitAUR)
- glib2 (glib2-gitAUR, glib2-selinuxAUR, glib2-patched-thumbnailerAUR)
- glibc (glibc-gitAUR, glibc-linux4AUR, glibc-eacAUR, glibc-eac-binAUR)
- gnome-desktop-4 (gnome-desktop-4-gitAUR)
- gnome-settings-daemon (gnome-settings-daemon-mobileAUR, gnome-settings-daemon-gitAUR)
- graphene (graphene-gitAUR)
- gsettings-desktop-schemas (gsettings-desktop-schemas-nofontAUR, gsettings-desktop-schemas-gitAUR)
- gtk4 (gtk4-customizableAUR, gtk4-paper-planeAUR, gtk4-gitAUR)
- harfbuzz (harfbuzz-gitAUR)
- iio-sensor-proxy (iio-sensor-proxy-gitAUR, iio-sensor-proxy-tuxedoAUR, iio-sensor-proxy-tuxedo-gitAUR)
- lcms2 (lcms2-ff-gitAUR, lcms2-gitAUR, lcms2-ffAUR)
- libcanberra
- libcolord (libcolord-gitAUR)
- Show 46 more dependencies...
Required by (16)
- gnome-kiosk (requires mutter)
- gnome-monitor-config-git (requires mutter)
- gnome-shell-beta-performance (requires libmutter-15.so)
- gnome-shell-beta-performance (requires mutter)
- gnome-shell-performance (requires libmutter-15.so)
- gnome-shell-performance (requires mutter)
- gnome-shell-performance-unstable (requires libmutter-15.so)
- gnome-shell-performance-unstable (requires mutter)
- gnome-shell-screencast-vaapi (requires mutter)
- magpie-wm-git (requires mutter)
- phoc-git (requires mutter) (check)
- power-profile-selector-git (requires mutter) (optional)
- regolith-i3 (requires mutter)
- wingpanel-git (requires mutter)
- xwayland-run-git (requires mutter) (optional)
- xwayland-run-mutter (requires mutter) (optional)
Sources (4)
Latest Comments
« First ‹ Previous 1 .. 18 19 20 21 22 23 24 25 26 27 28 .. 64 Next › Last »
Terence commented on 2020-03-15 17:29 (UTC)
arun321 commented on 2020-03-01 17:25 (UTC)
Cannot even pass prepare stage when using --- "_merge_requests_to_use=('!493' '!575' '!579' '!719' '!724' '!762' '!983' '!1000') # Saren's pick"
Saren commented on 2020-02-12 10:30 (UTC) (edited on 2020-02-12 10:33 (UTC) by Saren)
Oops, it seems like I pushed my pick which is not safe for everyone. If you are experiencing crashes or weird stuff because you are using Wayland/multiple monitors/keyboard layouts, use _merge_requests_to_use=('!575' '!983' '!1000')
instead.
ciupenhauer commented on 2020-02-11 20:04 (UTC)
@glitsj16 sorry, meant the 3 !7xx MRs, bug doesn't happen with !719 & !762, without !724. All 3 need to be there at same time. Also noticed it only happens when you have external monitor plugged in
glitsj16 commented on 2020-02-11 19:24 (UTC)
@ciupenhauer Usually I'm on Wayland using mesa. I can reproduce the crash there. Never noticed it before because I have 'blank screen' set to 'Never' in the power saving settings. So thanks for mentioning it here. Not sure about the third MR involved you mention in your post, as I read !762 twice :) But I'm willing to experiment if you can throw that out here.
ciupenhauer commented on 2020-02-11 16:19 (UTC)
@glitsj16 are you on X or wayland? I get a crash on wayland when waking up the display from blank screen on Wayland with !719 and !762 and !762. Either !762 alone or the other 2 don't give this bug. Also no issue on X with all 3
glitsj16 commented on 2020-02-07 01:48 (UTC)
@ciupenhauer Glad to help. I only put those pieces together for !724 a few days ago. Actual credit (and sainthood perks) should go to https://aur.archlinux.org/account/glorious-yellow for finding a way to easily incorporate MR patches (see https://aur.archlinux.org/packages/gnome-shell-performance/#comment-726303). Getting truly amazing performance here too now. I also use a GS extension from https://github.com/adee/gnome-shell-aggressive-gc and I rarely see gnome-shell go over 4% CPU usage. Just putting this out here for who wants to give it a try.
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 installmutter
&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/