clutter/evdev: Don't ignore CAPS lock as modifier
Mark CAPS lock as a modifier (as it should) so that when using XKB
options to change the default behaviour of CAPS lock, the new assigned
key can by used as a sticky key as well.
(cherry picked from commit
6df2b7af556bf01f8d564b86c66c293678ab6b90)
Bug: https://gitlab.gnome.org/GNOME/mutter/issues/112
Origin: upstream, 3.28.3, commit:
2dd9fc17c17cbc9b09f8a364682c5759d6539a8d
Gbp-Pq: Name clutter-evdev-Don-t-ignore-CAPS-lock-as-modifier.patch
clutter/evdev: ignore injected events from IM
Input method can inject key events, which leads to multiple reported key
press/release events for a single user action.
Ignore those events as this confuses keyboard accessibility.
(cherry picked from commit
c01b099dbdfee4b2a98864bc76bfa1b96a55c8fb)
Origin: upstream, 3.28.3, commit:
c7a38c31398871d2461b66963756816d268f524e
Gbp-Pq: Name clutter-evdev-ignore-injected-events-from-IM.patch
wayland: Use cursor position in logical monitor
When using two monitors size by side with different scales, once the
cursor moves from one output to another one, its size changes based on
the scale of the given output.
Changing the size of the cursor can cause the cursor area to change
output again if the hotspot is not exactly at the top left corner of the
area, causing the texture of the cursor to change, which will trigger
another output change, so on and so forth causing continuous surface
enter/leave event which flood the clients and eventually kill them.
Change the logic to use only the actual cursor position to determine if
its on the given logical monitor, so that it remains immune to scale
changes induced by output scale differences.
(cherry picked from commit
67917db45f96befb777e5f331a775ea3c2b53012)
Bug: https://gitlab.gnome.org/GNOME/mutter/issues/83
Origin: upstream, 3.28.3, commit:
7d52be02290bd92589fbea756ca3431af8e71a94
Gbp-Pq: Name wayland-Use-cursor-position-in-logical-monitor.patch
projects / mutter.git / log