It does not build for me even when starting from a fresh snapshot:
Program catchsegv found: NO
mutter-performance/meson.build:308:2: ERROR: Program 'catchsegv' not found or not executable
Git Clone URL: | https://aur.archlinux.org/mutter-performance.git (read-only, click to copy) |
---|---|
Package Base: | mutter-performance |
Description: | A window manager for GNOME | Attempts to improve performances with non-upstreamed merge-requests and frequent stable branch resync |
Upstream URL: | https://gitlab.gnome.org/GNOME/mutter |
Licenses: | GPL-2.0-or-later |
Groups: | gnome |
Conflicts: | mutter |
Provides: | libmutter-15.so, mutter |
Submitter: | Terence |
Maintainer: | Terence (Saren, saltyming) |
Last Packager: | saltyming |
Votes: | 78 |
Popularity: | 0.37 |
First Submitted: | 2019-07-09 09:35 (UTC) |
Last Updated: | 2024-10-22 08:26 (UTC) |
« First ‹ Previous 1 .. 10 11 12 13 14 15 16 17 18 19 20 .. 64 Next › Last »
It does not build for me even when starting from a fresh snapshot:
Program catchsegv found: NO
mutter-performance/meson.build:308:2: ERROR: Program 'catchsegv' not found or not executable
@adryd @ewout I did the same way of what the original mutter package did. Doesn't it build now?
Please include MR 2294 to work around catchsegv no longer being packaged by glibc.
You'll need to remove the catchsegv meson dependency, this won't build anymore. mutter-git has a patch already
@JordanViknar I also made !2265 here, which is a diff for the package repo itself: https://gist.github.com/FiestaLake/a5ed51c1595bb0ca5427d75a8e3fba34
@Saren can you test this too?
@JordanViknar
I have tested adding !2265 with mr1441.patch unchanged. I am dropped to X11 only.
!1441 seems to be synced to mutter 42 now, backport to 41 is unlikely trivial.
mr2265.patch that builds: https://gist.github.com/Saren-Arterius/1ee7486acda25134836501c117defde6
I think the !1441 patch included in this package should be updated. According to a comment in https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_1265504,MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
will no longer be necessary to prevent the Wayland Multi-display freezing issue, thanks to https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2265.
This has been an issue some of us have been encountering in the past before I reposted the workaround here. Problem is that, since this was a workaround, it had to be manually done by the user and technically didn't fix the problem. Plus, I suspect that this workaround had a negative impact on performance, ironically.
@afader Does commit 0cb76e589752 build fine there? i really can't test wayland.
Can't build this package with wayland running but it works fine on Xorg with same options. On linux-hardened
(mutter-persistent-virtual-monitor:28293): mutter-ERROR **: 14:54:57.711: Failed to start X Wayland: Failed to open Xauthority file: Permission denied
Pinned Comments
saltyming commented on 2022-03-22 09:37 (UTC) (edited on 2024-10-22 08:27 (UTC) by saltyming)
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 mutter-performance-unstable
The default patch list includes "Dynamic triple buffering(!1441)", "text-input-v1(!3751)".
Latest Dynamic triple buffering patch has several included MRs from the main development branch to achieve maximum performance.
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.)
You can see some patches' git history here: https://git.saltyming.net/sungmg/mutter-performance-source/
Saren commented on 2018-08-30 14:52 (UTC) (edited on 2020-10-06 05:50 (UTC) by Saren)
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 performance patches are by default enabled.
A package for gnome-shell performance patches: https://aur.archlinux.org/packages/gnome-shell-performance/