Package Details: mutter-performance-devkit 49.0-1

Git Clone URL: https://aur.archlinux.org/mutter-performance.git (read-only, click to copy)
Package Base: mutter-performance
Description: GNOME Mutter Development Kit
Upstream URL: https://gitlab.gnome.org/GNOME/mutter
Licenses: GPL-2.0-or-later
Submitter: Terence
Maintainer: glorious-yellow
Last Packager: glorious-yellow
Votes: 74
Popularity: 0.000005
First Submitted: 2019-07-09 09:35 (UTC)
Last Updated: 2025-09-26 01:43 (UTC)

Pinned Comments

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 .. 22 23 24 25 26 27 28 29 30 31 32 .. 65 Next › Last »

ciupenhauer commented on 2019-10-28 22:19 (UTC)

Ah, yes, very nice with the array!

Terence commented on 2019-10-28 16:28 (UTC)

@TheAifam5 @gedgon @ciupenhaue I added!719 and !762 which fixes one issue of !719. You need to add them to the _merge_requests_to_use array.

Terence commented on 2019-10-27 23:13 (UTC)

Alright tomorrow I'll add !719 as an optional MR.

theaifam5 commented on 2019-10-27 21:48 (UTC)

!719 is missing in PKGBUILD.

Terence commented on 2019-10-27 16:23 (UTC)

@Saren I introduced a new way of choosing what MR you want to use: Just add the proposed ones you want into the _merge_requests_to_use array.

gedgon commented on 2019-10-26 16:54 (UTC)

@ciupenhauer, Dan van Vugt mentioned here 1, that !719 revisit or rewrite is one of the goals for the 3.36. Till then, just try !719 as it is, and check if you are affected by the regressions that it triggers or causes.

ciupenhauer commented on 2019-10-25 14:52 (UTC)

any more news in !719?

gedgon commented on 2019-10-22 14:33 (UTC) (edited on 2019-10-22 14:34 (UTC) by gedgon)

@Terence Personalty, I haven't encountered any crashes caused by !719, these are probably limited to rare certain scenarios, and the performance difference is huge, so it's probably worth adding it on condition, just like !493. Some numbers on polaris @4k w/ GPU clock limited to 300/214/387/625MHz. FPS for an overview animation w/ 5 windows

mutter-3.34.1+27+g85f5db7e7 w/o !719 

*** FPS for MetaStage: 31 ***
*** FPS for MetaStage: 36 ***
*** FPS for MetaStage: 31 ***
*** FPS for MetaStage: 31 ***
*** FPS for MetaStage: 35 ***
*** FPS for MetaStage: 31 ***
*** FPS for MetaStage: 31 ***
*** FPS for MetaStage: 34 ***

mutter-3.34.1+27+g85f5db7e7 w/ !719 

*** FPS for MetaStage: 60 ***
*** FPS for MetaStage: 60 ***
*** FPS for MetaStage: 61 ***
*** FPS for MetaStage: 60 ***
*** FPS for MetaStage: 61 ***
*** FPS for MetaStage: 60 ***
*** FPS for MetaStage: 61 ***
*** FPS for MetaStage: 61 ***

Terence commented on 2019-10-20 23:06 (UTC)

@glitsj16 the updated version should contain the fix.

@gedgon Thanks, it seems like it was causing different problems that aren't all addressed at the time so I'm not applying it.

glitsj16 commented on 2019-10-09 03:00 (UTC) (edited on 2019-10-09 03:03 (UTC) by glitsj16)

[FYI] Latest version broke GNOME's Night Light functionality. On a daily/nightly basis I actually use https://aur.archlinux.org/packages/redshift-gnomerr-git, but when that broke, I tried the native Night Light, which was broken too. See https://gitlab.gnome.org/GNOME/mutter/issues/851 for my bug report. When I build mutter-performance from latest git master and revert the relevant MR, both work again.

« First ‹ Previous 1 .. 22 23 24 25 26 27 28 29 30 31 32 .. 65 Next › Last »