sungmg/mutter-performance-source
1
0
Fork 0
Code Activity
A repository that has original source for patches used in the Arch User Repository package called "mutter-performance". https://aur.archlinux.org/packages/mutter-performance
30744 commits 14 branches 4 tags 92 MiB
C 98.7%
Meson 0.8%
Python 0.4%
Find a file
Pascal Nowack 483601844b backends/eis-client: Do not add device before adding EIS regions 
When a device is added, libei does not allow adding additional regions
for that particular device, as it is already advertised to the EI
client.
As a result, mutter currently effectively only adds the first region to
a device, but not the others.
This makes input in multi monitor sessions only possible on one monitor,
as the EI client cannot look up the other regions, since they were not
advertised to it.

Fix this situation by not adding and resuming the device, when a shared
device is used.
Instead, for shared devices, always add all regions first, and then
after that, add and resume the device.

Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3273>
2023-09-16 22:13:05 +02:00
.gitlab/issue_templates gitlab: Add missing < in markdown comment tag 2020-02-14 03:10:28 +00:00
.gitlab-ci ci: Look for matching ref in user remote for branch pipeline 2023-08-08 04:11:13 +02:00
clutter clutter/frame-clock: Fix unused variable warning 2023-09-14 12:50:23 +00:00
cogl cogl/pixel-format: Add G16 and RG1616 pixel formats 2023-09-13 14:11:27 +02:00
data remote-desktop/session: Limit device type access when using libei 2023-09-01 10:43:26 +00:00
doc docs: Update url maps 2023-09-02 10:50:47 +00:00
meson build: Replace custom post-install script 2022-11-19 02:21:05 +01:00
mtk mtk: Include config.h in C files 2023-09-02 09:52:54 +00:00
po Updated Danish translation 2023-09-11 21:12:37 +02:00
src backends/eis-client: Do not add device before adding EIS regions 2023-09-16 22:13:05 +02:00
subprojects build: Update sysprof build options 2022-12-17 19:58:00 +00:00
tools tools/get-state: Round refresh rates to three decimal places 2022-08-19 15:28:56 +00:00
.gitignore Add .buildconfig to .gitignore 2023-02-17 21:44:29 +00:00
.gitlab-ci.yml build: Enable libdisplay-info for the default builds 2023-09-12 17:53:58 +02:00
check-style.py check-style: Allow deciding on individual suggestions with --rewrite 2023-02-20 22:21:01 +00:00
config.h.meson edid: Integrate libdisplay-info for edid parsing 2023-05-02 17:37:01 +00:00
COPYING Updated obsolete FSF postal address in COPYING 2014-01-12 08:44:30 +07:00
HACKING.md docs: Update coding style link 2021-11-09 19:52:14 +01:00
meson.build Bump version to 45.rc 2023-09-06 13:58:21 +02:00
meson_options.txt edid: Integrate libdisplay-info for edid parsing 2023-05-02 17:37:01 +00:00
mutter.doap DOAP: Remove defunct mailing list; add Discourse 2023-09-15 03:19:22 +02:00
NEWS Bump version to 45.rc 2023-09-06 13:58:21 +02:00
README.md readme: Add Mtk docs link 2023-09-02 10:50:47 +00:00

README.md

Mutter

Mutter is a Wayland display server and X11 window manager and compositor library.

When used as a Wayland display server, it runs on top of KMS and libinput. It implements the compositor side of the Wayland core protocol as well as various protocol extensions. It also has functionality related to running X11 applications using Xwayland.

When used on top of Xorg it acts as a X11 window manager and compositing manager.

It contains functionality related to, among other things, window management, window compositing, focus tracking, workspace management, keybindings and monitor configuration.

Internally it uses a fork of Cogl, a hardware acceleration abstraction library used to simplify usage of OpenGL pipelines, as well as a fork of Clutter, a scene graph and user interface toolkit.

Mutter is used by, for example, GNOME Shell, the GNOME core user interface, and by Gala, elementary OS's window manager. It can also be run standalone, using the command "mutter", but just running plain mutter is only intended for debugging purposes.

Contributing

To contribute, open merge requests at https://gitlab.gnome.org/GNOME/mutter.

It can be useful to look at the documentation available at the Wiki.

The API documentation is available at:

Coding style and conventions

See HACKING.md.

Git messages

Commit messages should follow the GNOME commit message guidelines. We require an URL to either an issue or a merge request in each commit. Try to always prefix commit subjects with a relevant topic, such as compositor: or clutter/actor:, and it's always better to write too much in the commit message body than too little.

If a commit fixes an issue and that issue should be closed, add URL to it in the bottom of the commit message and prefix with Closes:.

Do not add any Part-of: line, as that will be handled automatically when merging.

The Fixes tag

If a commit fixes a regression caused by a particular commit, it can be marked with the Fixes: tag. To produce such a tag, use

git show -s --pretty='format:Fixes: %h (\"%s\")' <COMMIT>

or create an alias

git config --global alias.fixes "show -s --pretty='format:Fixes: %h (\"%s\")'"

and then use

git fixes <COMMIT>

Example

compositor: Also consider dark matter when calculating paint volume

Ignoring dark matter when calculating the paint volume missed the case where
compositing happens in complete vacuum.

Fixes: 123abc123ab ("compositor: Calculate paint volume ourselves")
Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/1234

Default branch

The default development branch is main. If you still have a local checkout under the old name, use:

git checkout master
git branch -m master main
git fetch
git branch --unset-upstream
git branch -u origin/main
git symbolic-ref refs/remotes/origin/HEAD refs/remotes/origin/main

License

Mutter is distributed under the terms of the GNU General Public License, version 2 or later. See the COPYING file for detalis.