I recently discovered the source of my stuttering problem when using an multibutton/MMO mouse. In short, pressing keys on two different keyboards triggers a reload, which introduces lag. The solution is proposed here: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1858#note_818548
Essentially, remove the line case XkbNewKeyboardNotify: from ./src/backends/x11/meta-backend-x11.c. I edited the PKGBUILD to contain sed -i '/case XkbNewKeyboardNotify:/d' src/backends/x11/meta-backend-x11.c at the end of the prepare phase, and it immediately removed the stuttering.
Perhaps this can be included optionally (e.g. with an environment variable)? It might be detrimental to people using multiple keyboards with different layouts, bit it is a massive improvement for people with MMO-mice.
Pinned Comments
saltyming commented on 2022-03-22 09:37 (UTC) (edited on 2023-09-02 03:43 (UTC) by saltyming)
Please note that a
debugoption is disabled in this package.To disable building the docs package, set an env:
_disable_docs=yTo enable the
check()process, set an env:_enable_check=yIf the building process is getting failed on
check()like83/114 mutter:core+mutter/backends/native / native-unit TIMEOUT 180.01s killed by signal 15 SIGTERMthen you might want to do one of these:
0) Unset an env:
_enable_check=y1) Kill your pipewire session manager;
killall $(pacman -Qq pipewire-session-manager).2) Reboot the machine.
3) Pass a variable
--nochecktomakepkg(which can be passed along with--mflagsfirst if you are usingparu) to temporarily disable acheck()process.4) Add a line
options=(!check)to the package's PKGBUILD file to disable acheck()process.And try again.
Terence commented on 2020-08-31 16:26 (UTC) (edited on 2020-08-31 16:26 (UTC) by Terence)
@NettoHikari or anyone unable to compile with the following error:
lto1: internal compiler error: bytecode stream: expected tag identifier_node instead of LTO_UNKNOWNYou need to rebuild sysprof and then try again.
Reference: https://bugs.archlinux.org/task/67686.
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/