| 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.011501 |
| First Submitted: | 2018-08-04 18:21 (UTC) |
| Last Updated: | 2025-04-02 04:27 (UTC) |
@Terence latest update does not resolve the issue for me unfortunately.
Also, just in case I misled with my last comment - the app grid is not actually blank: if I click the 'show applications' button on the dash I do see the app grid. What I don't see are app search results upon typing into the search box in the overview. So just clarifying in case the wrong bug is being hunted.
@chrisjbillington Thanks, can you try the updated version?
As one datapoint, I am once again seeing a blank app grid now that !110 has been re-enabled, despite the potential fix.
@TheAifam5 I updated this package with the problematic MR re-enabled but with a potential fix. Would you mind testing it and report back if it fixed it?
I posted a possible bug report to the mutter-performance comment listing, not sure if it applies to this particular package instead.
@deezid If you disable extensions, does it still happen? In addition to that, please try the gnome-shell-git and mutter-git packages, disable foreign extensions and tell me if you still encounter those problems.
@Terence: Had lots of glitches on the dock and top panel after suspend with these two patches: !505 and !595
Uncommenting these fixed everything for me. Seems they cause more harm than they help. Latest Nvidia driver/1080Ti
Edit: Just activated both again. Without any of these the app menu is slow as hell. With just 505 it's fast again but the glitches never disappear. With 505 and 595 it's fast but has glitches for a few seconds after suspend...
Hey again @Terence. The gnome-shell from ArchLinux repository does not have that issue. Please read the following thread about that issue here: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1456
Hey @Terence. Sorry for missleading information. The issue appears to be in the application grid, which i reported here: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1456#note_560248 But first, I need to check if the issue is present on the original gnome-shell package. The issue which I wrote previously, was looking like my issue where the application grid was empty but was related to the dash (left side dash) and not to the grid where the applications icon shows up.
Hey @TheAifam5, thank you very much for your report, I added the related MR. Please try again and tell me if it works for you.
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!