Package Details: mutter-781835-workaround 3.32.1-1

Git Clone URL: (read-only)
Package Base: mutter-781835-workaround
Description: A window manager for GNOME. This package reverts a commit which may causes performance problems for nvidia driver users. Some performance patches also included.
Upstream URL:
Licenses: GPL
Groups: gnome
Conflicts: mutter
Provides: mutter
Submitter: Saren
Maintainer: Saren (Terence)
Last Packager: Saren
Votes: 36
Popularity: 2.554144
First Submitted: 2017-10-06 15:19
Last Updated: 2019-04-20 04:12

Dependencies (22)

Required by (12)

Sources (4)

Pinned Comments

Terence commented on 2019-03-16 15:59

With the new patches, to get realtime scheduling for gnome-shell, do the following:

sudo setcap CAP_SYS_NICE=+ep /usr/bin/gnome-shell 
gsettings set org.gnome.mutter experimental-features "['rt-scheduler']"

Saren commented on 2018-08-30 14:52

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.

The patch indicated by is the one Ubuntu 18.04 currently using.

A package for gnome-shell performance patches:

Latest Comments

1 2 3 4 5 6 ... Next › Last »

kode54 commented on 2019-04-11 06:42

Replace revision f5a1ec1c with 34fae0f5. This is only going to keep hurting more and more, as all of @vanvugt's PRs keep getting rebased constantly instead of getting accepted.

kerframil commented on 2019-04-05 12:01

Currently, f5a1ec1c is reported as a bad revision. Also, the rt-scheduler option doesn't appear to have any effect. As shown below, neither the main process nor any of its threads are using the RR scheduling class.

$ ps -C gnome-shell -Lo pid,cls,comm,command
  816  TS gnome-shell     /usr/bin/gnome-shell
  816  TS gmain           /usr/bin/gnome-shell
  816  TS gdbus           /usr/bin/gnome-shell
  816  TS dconf worker    /usr/bin/gnome-shell
  816 IDL gnome-s:disk$0  /usr/bin/gnome-shell
  816  TS JS Helper       /usr/bin/gnome-shell
  816  TS JS Helper       /usr/bin/gnome-shell
  816  TS JS Helper       /usr/bin/gnome-shell
  816  TS JS Helper       /usr/bin/gnome-shell
 7364  TS gnome-shell     /usr/bin/gnome-shell
 7364  TS gmain           /usr/bin/gnome-shell
 7364  TS gdbus           /usr/bin/gnome-shell
 7364  TS dconf worker    /usr/bin/gnome-shell
 7364 IDL gnome-s:disk$0  /usr/bin/gnome-shell
 7364  TS JS Helper       /usr/bin/gnome-shell
 7364  TS JS Helper       /usr/bin/gnome-shell
 7364  TS JS Helper       /usr/bin/gnome-shell
 7364  TS JS Helper       /usr/bin/gnome-shell

flomax commented on 2019-04-04 03:29

@Terence Cheers, and I now see where I went wrong too.

Terence commented on 2019-04-04 02:38

@flomax Thanks for reporting, it should be fixed.

flomax commented on 2019-04-03 23:07

Getting fatal: bad revision '14a27e87^..a40d7927'

Replacing a40d7927 with 6474593e or 966e062d did not fix, but build completes once whole line is commented out.

Terence commented on 2019-03-31 01:19

@Saren oups my bad! Updated so it doesn't apply by default.

Saren commented on 2019-03-30 14:09

@Terence Did you mean without _revert=0? _revert=0 still applies the patch I guess.

Terence commented on 2019-03-30 11:03

Thanks @ciupenhauer and @deezid for the heads-up, updated. @Saren this should render the commit revert useless. Can you try again with _revert=0 and report back?

deezid commented on 2019-03-28 20:08

@clupenhauer. That's what I thought. Skip the first !281 commit.

  # clutter-stage-cogl: Reduce output latency and reduce missed frames too [performance]
  # first commit replaced by !363
  git cherry-pick -n 186f16f8

  # Consolidate all frame throttling into clutter-stage-cogl [performance]
  git cherry-pick -n 577084a4^..c71e6523

ciupenhauer commented on 2019-03-28 20:05

According to Daniel van Vugt: "Also note the second commit of provides a fix for this bug too. It replaces the first commit of"

Does that mean we can safely switch off patch 281 and use only 363?