Package Details: gnome-shell-performance 1:48.1-1

Git Clone URL: https://aur.archlinux.org/gnome-shell-performance.git (read-only, click to copy)
Package Base: gnome-shell-performance
Description: Next generation desktop shell
Upstream URL: https://gitlab.gnome.org/GNOME/gnome-shell
Licenses: GPL-3.0-or-later
Groups: gnome
Conflicts: gnome-shell
Provides: gnome-shell
Submitter: Saren
Maintainer: glorious-yellow
Last Packager: glorious-yellow
Votes: 35
Popularity: 0.010174
First Submitted: 2018-08-04 18:21 (UTC)
Last Updated: 2025-04-18 22:49 (UTC)

Dependencies (65)

Required by (450)

Sources (3)

Pinned Comments

<deleted-account> commented on 2023-05-02 11:12 (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 2022-10-27 15:51 (UTC)

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

For people using [testing] branch.

Apply the patch with git am {patchname}.patch

<deleted-account> commented on 2021-11-18 14:16 (UTC)

If you have a problem during any system update with mutter-performance & gnome-shell-performance, please install mutter & 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 gnome-shell-performance-unstable

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.)

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 patches for performance and fixes are by default enabled.

A package for mutter(compositor) performance patches: https://aur.archlinux.org/packages/mutter-performance/

Terence commented on 2019-08-02 16:35 (UTC) (edited on 2019-08-02 19:09 (UTC) by Terence)

Warning: Before making a report of something broken, make sure it is not caused by an extension or a custom theme!

Latest Comments

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 18 .. 20 Next › Last »

Saren commented on 2019-10-04 03:44 (UTC)

Revert added hopefully to workaround https://bugzilla.redhat.com/show_bug.cgi?id=1754630#c12

Saren commented on 2019-09-25 01:55 (UTC)

It's recommended to use extra/gnome-shell instead of this package for now, as this package contains no performance patch now compared to extra/gnome-shell, and extra/gnome-shell is more updated as of now.

NettoHikari commented on 2019-09-20 01:55 (UTC)

Breaks GNOME right now (also GDM), because 3.34 hit stable today.

<deleted-account> commented on 2019-09-12 07:27 (UTC)

Error during building. fatal: bad revision '39f10eaa^..6e704ee1'

Terence commented on 2019-09-04 13:37 (UTC)

@predictably @ndttt @glorious-yellow Updated.

predictably commented on 2019-09-04 12:09 (UTC)

I also encounter this message while building:

fatal: bad revision '1a3c98bd' ==> ERROR

No solution yet.

chrisjbillington commented on 2019-08-30 03:07 (UTC) (edited on 2019-08-30 15:33 (UTC) by chrisjbillington)

I notice !110 was disabled. Was this because of people using the Yaru gnome shell theme? Yaru used to be buggy with !110, but has updated to accommodate !110, and in fact now is buggy without !110:

https://github.com/ubuntu/yaru/issues/1466

So if disabling !110 by default was only for the sake of Yaru users, it should now be re-enabled. The Yaru release requiring !110 is 19.10.1, released 11 days ago.

Edit: Actually, the Yaru AUR package maintainer has decided to hold back Yaru to 19.04.3 and not package the newer upstream version for now, presumably until gnome shell 3.34 is in Arch. So probably leave !110 disabled for now after all.

ndttt commented on 2019-08-29 07:48 (UTC)

Hi, I'm getting the error

fatal: bad revision '1a3c98bd' ==> ERROR: A failure occurred in prepare(). Aborting... checking dependencies...

when updating to the latest package. Any insight? I've tried clean building already.

glorious-yellow commented on 2019-08-27 19:01 (UTC)

MR #689 hash changed to 46602fd6

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 18 .. 20 Next › Last »