@alex4401 I see the same problem. I commented out the various cherry-picks a few at a time and determined that !575 seems to be the issue. Reported upstream here:
https://gitlab.gnome.org/GNOME/mutter/merge_requests/575#note_550478
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 .. 26 27 28 29 30 31 32 33 34 35 36 .. 64 Next › Last »
@alex4401 I see the same problem. I commented out the various cherry-picks a few at a time and determined that !575 seems to be the issue. Reported upstream here:
https://gitlab.gnome.org/GNOME/mutter/merge_requests/575#note_550478
Great. How did it work?
Minimized windows (by window control buttons) are now returning to their normal state improperly. For me, they visually open mostly in the second half of the screen (or with 3/4 of the window below Dash to Panel taskbar) but technically they're are back at their original position as I am able to interact with the affected windows by clicking where anywhere where they should be. Alt+tabing to another application and alt+tabbing back to the affected application restores it to the correct state.
Also, Coverflow alt-tab extension (most notably, Timeline setting) is not compatible with the latest updates - while the main functionality works as expected, the wallpaper isn't redrawn when going through the window list (and the remains of windows scrolled by appear until the alt-tab is finished).
fatal: bad revision '3ca3194f^..1be20af0'
- MR600 has had its range changed to b60aa2c4^..4b639866
@Terence I am okay with the package rename. Can we get an AUR admin to help us with this matter?
Also in the PKGBUILD of mutter-performance I think it's good to use add mutter-781835-workaround
to provides
and conflicts
, or replaces
.
@alex4401 Glad it works now :)
@deezid That's weird, maybe try to provide more info and/or find what MR produces it.
@chrisjbillington Your issue was reported and is being tracked here: https://gitlab.gnome.org/GNOME/mutter/merge_requests/493#note_549833
@Saren I've created https://aur.archlinux.org/packages/mutter-performance and I am also writing a forum post where all the discussions unrelated to packaging will go. Can I have your review of the package and approval? I'll then proceed to ask to move this one to the other.
Thank you, @Terence. As far as I am able to tell, it does work flawlessly now.
@Terence: noticing some weird stuff too. Some applications won't open anymore or open as black windows.
More Info: Nautilus opens as a black window. The applications not starting issue was caused by a Bzip2 update.
@chrisjbillington: seems to be Wayland related. No issues here @Terence: huge boost in activities - especially with mouse interaction. Very smooth now
After updating from the version from yesterday (3.32.2+32+g947da2c5d-2) to today (3.32.2+40+gccab0f470-1), I now get a segfault upon showing the activities overview.
Culprit seems to be an interaction between !677 and !493, see comment threads of those two MRs for discussion.
Edit: Yes, as mentioned by @deezid, the segfault is only on Wayland
Edit: Commenting out the !493 cherry pick resolves the issue for me.
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/