Package Details: mutter-performance 1:46.2+r14+g485fa00f1a-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: 77
Popularity: 1.33
First Submitted: 2019-07-09 09:35 (UTC)
Last Updated: 2024-06-23 12:07 (UTC)

Required by (13)

Sources (5)

Pinned Comments

saltyming commented on 2022-03-22 09:37 (UTC) (edited on 2024-05-26 07:35 (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. Note that it can be problematic in some versions/setups.


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 may 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 the check() process.

4) Add a line options=(!check) to the package's PKGBUILD file to disable the 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 .. 39 40 41 42 43 44 45 46 47 48 49 .. 60 Next › Last »

deezid commented on 2019-01-30 13:40 (UTC)

Ugh, should I update or not? It has been running so well over the past few days. :D

calindan2013 commented on 2019-01-29 10:17 (UTC) (edited on 2019-01-29 10:18 (UTC) by calindan2013)

sad to conclude this didnt resolve my issue, everything still laggy af. performance simply degrades fast after reboot.

deezid commented on 2019-01-28 18:34 (UTC)

@calindan2013 just tried latest kwin and it's indeed slower on my NVIDIA hardware. Even the overview animation as well as dragging windows isn't as smooth. Scrolling in Chrome is quite ok but can't keep up either. But 4K 60P playback in Chrome isn't smooth at all while with patched Mutter it's perfect - even 8K playback works flawlessly up to 30p.

Btw. using kwin my systemmonitor shows some CPU spikes while scrolling, with mutter there are basically none. 2D acceleration works fine with NVIDIA - if supported, when using my internal HD620 GPU everything feels slower in comparison.

calindan2013 commented on 2019-01-28 18:17 (UTC)

deezid never had any performance or animation or smoothness problem at all on KDE on any distro. as for app perfmance,last I checked 3D app and game benchmarks on Phoronix it was as good as on any of the other DEs. I don't know if that scrolling fix is possible on NVIDIA.

deezid commented on 2019-01-28 15:40 (UTC) (edited on 2019-01-28 16:01 (UTC) by deezid)

@Calindan2013 using these mutter patches (and evdev for mouse input) scrolling actually feels smoother in Chrome/Linux than it does in Chrome on Windows 10 (system-monitor indicates it's GPU accelerated). In KDE it's terrible though, regardless of the driver - even though every animation is smooth.

It doesn't really matter that much when app performance suffers and I can't even resize a window without constant repaintings - have to figure out if it's a QT or kwin problem though.

Still need to test this version of mutter using my Intel HD620.

deezid commented on 2019-01-28 15:38 (UTC) (edited on 2019-01-28 15:41 (UTC) by deezid)

@calindan2013 priority should be app performance I think which in KDE just sucks at the moment with both NVIDIA (1080ti) and Intel (HD620) drivers. At least on Intel there's no tearing. It's almost impossible to edit in Resolve using Kwin, it's not possible to watch 4K content in a browser either. Scrolling is also as slow as with stock mutter. Really hoping they can find a way out of it.

The only lag in Gnome I can still notice is by using the workspace switcher for zooming in by mouse and if I lower my CPU frequencies. Max/Min into Dash rather feels like a hack in Gnome as I don't think Gnome developers want that feature at all. lol

calindan2013 commented on 2019-01-28 15:32 (UTC) (edited on 2019-01-28 15:39 (UTC) by calindan2013)

Sorry, I understand your point but I am a casual desktop user interested in just seeing smooth performance in 90% of situations, like animations and moving windows around. While it is faster now, frames are being dropped and lag is still visible in overview/minimize/maximize etc.

Scrolling in the browser is a lagfest as it is in all browsers , with or without any videos playing. This is because there is no GPU acceleration on NVIDIA in Linux. Only Windows has a smooth browsing experience.

KDE has no such visible lag in any of the basic desktop and window animations. Thanks for your work though, much appreciated. Hope the GNOME and NVIDIA guys will be able to make this DE work properly, it's 2019 already and making a GTX 1080 and Ryzen CPU perform like a 32MB video and Pentium 3 is no fun for anyone wanting a reliable and enjoyable desktop experience.

My admiration and respect for attempting to fix what the big guys cant or dont want.

deezid commented on 2019-01-28 13:12 (UTC)

@calindan2013 try watching 4K60p on YouTube using this optimized version of mutter and compare to KDE. Try the same with resizing windows and scrolling in a browser. Video editing in KDE (using Resolve) is a lagfest as well.

calindan2013 commented on 2019-01-28 11:07 (UTC) (edited on 2019-01-28 11:08 (UTC) by calindan2013)

Reporting back. Definitely not as bad as before, but there are still ocassional frame drops here and there in the overview when switching windows. So slight visual lag. I think this is a consequence of the fact that there is still performance degradation over time in the GNOME code, even with all those patches applied.

calindan2013 commented on 2019-01-28 10:32 (UTC)

One more issue would be the displacement of the virtual desktop column in the Overview each time i use the hot corner to access it. As soon as i move the mouse around the column goes back in place.