Package Details: gnome-shell-performance 1:48.1-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
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: 34
Popularity: 0.008816
First Submitted: 2018-08-04 18:21 (UTC)
Last Updated: 2025-04-18 22:49 (UTC)

Dependencies (65)

Required by (450)

Sources (3)

Pinned Comments

<deleted-account> commented on 2023-05-02 11:12 (UTC)

gnome-44 diffs: https://gist.github.com/FiestaLake/aaf26db49292840aef43210001b4e080

For people using [staging] & [gnome-unstable] branch (or [testing] branch in the near future).

Apply the patch with git am {patchname}.patch

<deleted-account> commented on 2022-10-27 15:51 (UTC)

gnome-43 diffs: https://gist.github.com/FiestaLake/d6d9e597fe693b3f55d92890880e463c

For people using [testing] branch.

Apply the patch with git am {patchname}.patch

<deleted-account> commented on 2021-11-18 14:16 (UTC)

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 .. 9 10 11 12 13 14 15 16 17 18 19 20 Next › Last »

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.

chrisjbillington commented on 2019-08-02 16:53 (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

truongan commented on 2019-08-02 16:45 (UTC)

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

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!

Terence commented on 2019-08-02 16:28 (UTC)

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.

chrisjbillington commented on 2019-08-02 16:02 (UTC)

@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.

chrisjbillington commented on 2019-08-02 15:59 (UTC)

@Terence thanks for your efforts, here is the log file:

https://pastebin.com/BY599H6W

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.

Terence commented on 2019-08-02 15:25 (UTC) (edited on 2019-08-02 15:28 (UTC) by Terence)

@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"