| 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) |
@truongan I am seeing this too. Since 3.32.2+10+g2483b6038-6 was just about trying to fix the invisible-search-results bug, it can probably be reverted.
@Terence apologies for wasting your time. I have reported the bug to Yaru here: https://github.com/ubuntu/yaru/issues/1434
There could be regression in '3.32.2+10+g2483b6038-6', when multiple window overlap, shell may fail to register a click on which the mouser was hovering, and register a click on the active window instead. Revert to 3.32.2+10+g2483b6038-5 helped
Ah that explains it @crisjbillington, I'll add a pin comment saying to be sure to have extensions disabled and use adwaita theme before reporting an issue. In the meanwhile, try to patch the theme or just disable this MR locally.
@Terence I have just realised, I am using a custom session: The "Yaru" session from Ubuntu, which applies the Yaru theming to gnome-shell. In a regular gnome session, I do not see the issue. Therefore this is possibly a bug with the Yaru gnome shell theming.
@Terence thanks for your efforts, here is the log file:
This is an X session with extensions disabled. I logged in, tapped super, typed the first few letters of "alacritty", and hit enter. Alacritty launched (though no search results were visible), and then I immediately ran the journalctl command from alacritty, so the log ends there.
@chrisjbillington Please replace the patch with this one: https://send.firefox.com/download/c106023fe6e5ca28/#gtwHpbGiLfxW6HFwIAplfA, run updpkgsums, build, install and reproduce the issue then send back the log file you will have generated using journalctl -b /usr/bin/gnome-shell > search.log"
@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.
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!