Package Details: mutter-performance 48.2-1

Git Clone URL: https://aur.archlinux.org/mutter-performance.git (read-only, click to copy)
Package Base: mutter-performance
Description: Window manager and compositor for GNOME
Upstream URL: https://gitlab.gnome.org/GNOME/mutter
Licenses: GPL-2.0-or-later
Groups: gnome
Conflicts: mutter
Provides: libmutter-16.so, mutter
Submitter: Terence
Maintainer: glorious-yellow
Last Packager: glorious-yellow
Votes: 76
Popularity: 0.013505
First Submitted: 2019-07-09 09:35 (UTC)
Last Updated: 2025-04-14 05:13 (UTC)

Dependencies (68)

Required by (16)

Sources (3)

Pinned Comments

<deleted-account> commented on 2023-05-02 11:11 (UTC)

gnome-44 diffs: https://gist.github.com/FiestaLake/aaf26db49292840aef43210001b4e080

For people using [staging] & [gnome-unstable] branch (or [testing] branch in the near future).

Apply the patch with git am {patchname}.patch

<deleted-account> commented on 2023-02-13 04:41 (UTC)

Hi, I'm the co-maintainer of the package.

Unfortunately, my laptop's gpu died a few days ago. So I cannot bring lots of changes to the package. The only thing I can do right now is upgrading the package along with mr1441 only.

Sorry for the situation and I hope you understand it. If you want to be a co-maintainer of this package, please contact fiestalake@disroot.org and/or the other maintainers. Thanks.

<deleted-account> commented on 2022-10-27 15:54 (UTC)

gnome-43 diffs: https://gist.github.com/FiestaLake/d6d9e597fe693b3f55d92890880e463c

For people using [testing] branch.

Apply the patch with git am {patchname}.patch

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 .. 48 49 50 51 52 53 54 55 56 57 58 .. 65 Next › Last »

deezid commented on 2019-01-15 13:57 (UTC) (edited on 2019-01-15 18:37 (UTC) by deezid)

Was able to install this patched version after updating the commit numbers in the pkgfile.

What I noticed is that apps like Chrome or Davinci Resolve are now insanely smooth but mutter or at least dragging windows itself is now terribly slow. I think it is locked to 30fps. The cursor itself is running at 60fps all the time. Animations aren't affected either - in fact they are smoother than ever, just dragging windows around while no 60p video or animation is running.

Interestingly enough if there's a video with 60fps playing behind and the foreground window is being dragged around, everything is smooth until I stop playback. If the video only has up to 30fps dragging windows is locked at 30fps again. Moving video players like MPC or VLC is also smooth while playing lower framerate video files.

Will take a look at the individual applied patches and hopefully figure out which one is causing it.

EDIT: The 60p video can even be running on another activity. Will maybe use this as a workaround lol - just kidding. Also noticed that even 8K60p runs perfectly smooth inside Chrome now while before even 4K60p wasn't possible - amazing!

Fixed it by uncommenting the actual NVIDIA fix. Am using the official 415.25 driver here using a 1080TI

beano commented on 2019-01-09 11:40 (UTC) (edited on 2019-01-09 11:41 (UTC) by beano)

build fails with fatal: bad revision for commits 8234efc0 and d2fbb9ff. commenting them out as stated by Saren enables you to build the package.

m110s commented on 2018-12-24 17:51 (UTC)

@Terence Works now without reverting merge.tool. Thanks a lot mate!

Terence commented on 2018-12-24 15:58 (UTC) (edited on 2018-12-24 15:59 (UTC) by Terence)

@m110s updated once more, please report if it works. My instruction with mergetool was a mistake because not everyone has this merge tool... You can revert it with git config --global --unset merge.tool although it shoudn't have much of an impact at this point.

m110s commented on 2018-12-24 11:53 (UTC) (edited on 2018-12-24 11:55 (UTC) by m110s)

New error:

error: could not apply 81952da6f... clutter: Fix offscreen-effect painting of clones
hint: after resolving the conflicts, mark the corrected paths
hint: with 'git add <paths>' or 'git rm <paths>'
hint: and commit the result with 'git commit'
Merging:
clutter/clutter/clutter-paint-volume.c
clutter/tests/conform/meson.build

Normal merge conflict for 'clutter/clutter/clutter-paint-volume.c':
  {local}: modified file
  {remote}: modified file
The merge tool p4merge is not available as 'p4merge'

earlier I followed you instruction:

git config --global merge.tool p4merge

Terence commented on 2018-12-24 10:06 (UTC)

@m110s updated, please try again.

m110s commented on 2018-12-23 22:09 (UTC) (edited on 2018-12-23 22:10 (UTC) by m110s)

Just tried to build and got: fatal: bad revision '5c123a76'