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
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.009367 |
First Submitted: | 2018-08-04 18:21 (UTC) |
Last Updated: | 2025-04-18 22:49 (UTC) |
« First ‹ Previous 1 2 3 4 5 6 7 8 .. 20 Next › Last »
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
Interesting, I had tried running with --nocheck
, but I guess that doesn't disable the dependency check for the tests.
@saghm @phush0 Fixed it via disabling check()
and tests
meson setup option by default.
I had the same issue with libmutter-test-11, but seeing that it build fine for Chaotic AUR made me think the issue might be from having mutter-performance installed rather than mutter from the main repos. Replacing mutter-performance with just plain mutter did let me build gnome-performance, after which I reinstalled mutter-performance again. I suspect the solution here might be for mutter-performance to indicate that it provides libmutter-test-11.
@phush0 Seems like it builds fine here.
gnome-shell/src/st/meson.build:195:2: ERROR: Dependency "libmutter-test-11" not found, tried pkgconfig and cmake
please fix this
When trying to build this, MR 2519 fails to apply cleanly. Since the comment above the patch indicates that it was added when it was still in review, I imagine it can just be disabled now.
@glorious-yellow We have no difference with 43.1. Check the commit and the patch I added.
gnome-43 diffs: https://gist.github.com/FiestaLake/d6d9e597fe693b3f55d92890880e463c
For people using [testing] branch.
Apply the patch with git am {patchname}.patch
@glitsj16 I will change it in 43.0-1
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 installmutter
&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!