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 2 3 4 5 6 7 8 9 10 11 12 .. 19 Next › Last »

Terence commented on 2020-10-15 21:10 (UTC)

@glorious-yellow This package only or both this one and the one from [extra]? If the latter, consider opening a bug report upstream. Also make sure no extension is the cause of this.

glorious-yellow commented on 2020-10-15 03:58 (UTC)

I'm noticing severely worse performance especially with activities overview after updating to 3.38.

Saren commented on 2020-05-26 10:03 (UTC)

If you are experiencing shell coredump indicating st_theme_get_custom_stylesheets, try with !536.

I got crashes with wayland and adapta gtk+shell theme with this off.

Terence commented on 2020-05-08 14:18 (UTC)

@FuelFlo Great to hear, thanks for testing!

FuelFlo commented on 2020-05-08 13:02 (UTC)

@Terence thx!

Well it doesn't seem to happen anymore with the update you pushed, including 786, 923, 1126, 1164 and 1192.

...while it definitely also happened with the original arch mutter and gnome-shell package.

Terence commented on 2020-05-07 13:30 (UTC)

@FuelFlo try the new update I just pushed just in case.

If you can reproduce with the official arch package as well (make sure you also revert to mutter and not mutter-performance), then it needs to be reported upstream.

FuelFlo commented on 2020-05-07 13:25 (UTC)

@Terence, I'm having the same problem as @hpstg, but on wayland. Even using std. gnome-shell and deactivating all extensions still leads to having frozen program windows, either after screen lock or sby, but also if a window has been in the background for some time.

Terence commented on 2020-04-30 21:25 (UTC) (edited on 2020-05-07 13:28 (UTC) by Terence)

@hpstg Thanks for your report and update, I synced to 3.32.2 which includes https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/d64b1e6efbedbb27b04e955af890ef12496d28cd which might fix what you describe.

hpstg commented on 2020-04-30 12:38 (UTC) (edited on 2020-04-30 13:57 (UTC) by hpstg)

When in an X.org session, locking the screen, or the screen going to sleep, will "lock" any sort of interaction with application windows, while the shell itself can be clicked.

Reverting back to gnome-shell fixed it.

EDIT: It didn't fix it, it seems to be a more general issue. I will try to isolate the moment it happens exactly and paste the journal.

chrisjbillington commented on 2020-04-29 17:32 (UTC)

@Terence Thanks :)

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 19 Next › Last »