Package Details: gnome-shell-performance 1:47.1.r1.gf0fe25db6-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 | Attempts to improve performances with non-upstreamed merge-requests and frequent stable branch resync
Upstream URL: https://wiki.gnome.org/Projects/GnomeShell
Licenses: GPL
Groups: gnome
Conflicts: gnome-shell
Provides: gnome-shell
Submitter: Saren
Maintainer: Saren (Terence, saltyming)
Last Packager: saltyming
Votes: 35
Popularity: 0.24
First Submitted: 2018-08-04 18:21 (UTC)
Last Updated: 2024-10-19 14:00 (UTC)

Required by (453)

Sources (2)

Pinned Comments

saltyming commented on 2021-11-18 14:16 (UTC) (edited on 2024-09-20 11:58 (UTC) by saltyming)

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 19 Next › Last »

<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

glorious-yellow commented on 2019-08-24 14:37 (UTC) (edited on 2019-08-27 18:55 (UTC) by glorious-yellow)

I'm currently testing MR 22, 136, and 666.

Will report results after testing is complete.

Edit: currently results in broken animations

kode54 commented on 2019-08-03 01:59 (UTC)

@Terence @chrisjbillington That sounds surprisingly like the issue I was having a few releases ago, where "frequent" apps page, the icons would vanish as I moused over them. I was not running any custom themes or sessions, and this was before I had installed any third party Gnome Shell extensions. Fresh Arch install, in fact.

Of course, I have since wiped that drive and replaced it with BitLocker encrypted NTFS storage for my Windows installation, so I won't be much use at future bug testing.

Terence commented on 2019-08-02 17:35 (UTC)

@chrisjbillington it's fine, you were not the only one with the problem and you managed to find the solution yourself ;) The bug you are experiencing should be unrelated to this, I suggest both of you to try to disable !711 in mutter and report back there if it was indeed the issue.

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