| 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.062336 |
| First Submitted: | 2018-08-04 18:21 (UTC) |
| Last Updated: | 2025-01-16 06:35 (UTC) |
Cherry-picking 30a25112 for !925 throws "fatal: bad revision '30a25112'". I could only get !925 work by applying this patch: https://gist.github.com/glitsj16/ea360b4c24ed33fe4bf752033249d799. Also, !936 yields better performance impact when combined with !948. The latter works fine when using git_cp_by_msg '!948' "overviewControls: Use ClutterActor's translation-x".
HTH
!936 appears to make the activities overview animation a bit smoother.
It maintains a higher framerate with 15 windows open.
I am currently testing
https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/936
Sorry, I'm aware of the issue but don't have time to do a proper fix... @Saren would you mind taking over a little bit please?
I am reporting it as occurring with amdgpu. May or may not be related to using mesa-tkg-git from chaotic-aur.
Same issue as @rori and @kode54 reported. Seems like issue exactly in gnome-shell-performance 1:3.34.3-2 and not in mutter-performance package. Rollback to gnome-shell-performance 1:3.34.3-1 solved issue for me. I also use a nvidia-390xx-dkms package. Probably this happens with nvidia blobs only, i have not tested with nouveau or other related drivers.
I'm experiencing the same problems as kode54. Also somehow the screen lock seems to turn on randomly, and much faster than set.
I don't know if this is related, but with current-as-of-this-post gnome-shell-performance (1:3.34.3-2) and mutter-performance (3.34.3+1+g78a45e181-1), both acquired from chaotic-aur package repository, there seems to be an issue with unlocking the desktop after the screen is locked and goes into DPMS sleep, or locks on its own due to the screen saver.
It will present the lock screen, and I can type my password, but when I press enter on the password, it doesn't dismiss the lock screen. The lock screen stays, and won't go away unless I either press Escape or click the Cancel button. This effectively locks me out of my existing session.
I am not having this problem with the stable gnome-shell and mutter packages. I am also not using any extensions, other than stock ones, and the default Adwaita theme.
Also getting:
fatal: bad revision '30a25112'
on 1:3.34.3-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 installmutter&gnome-shellpackages 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!