Commits on Source (25)
-
Jürgen Benvenuti authored
-
Carlos Garnacho authored
This gives greater control to the callers on the place where a grab is being activated, this may make a difference in the handling of crossing events triggered through it, e.g. by having callers rely on having already obtained a ClutterGrab prior to handling the resulting effects. The "input only" grab has also been turned inactive by default, in order to to have the ClutterGrab pointer available for checks at the MetaWaylandEventHandler focus changing methods triggered through grab activation. (cherry-picked from commit 8e5f3a1f) Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3874>
-
Carlos Garnacho authored
Add the _inactive suffix, so that the state of these objects is clear. (cherry-picked from commit 01444e80) Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3874>
-
Chao-Hsiung Liao authored
-
Jeremy Bícha authored
-
Jeremy Bícha authored
-
Jeremy Bícha authored
also override_dh_auto_test automatically respects nocheck since dh compat 13
-
Jeremy Bícha authored
-
Daniel van Vugt authored
And move the remaining one to workarounds.
-
Robert Mader authored
And stop pre-computing values, making errors like this harder to spot. The values 0.0625 (16/256) and 0.5 (128/256) were slightly off, resulting e.g. in "black" not being #000000 but #010001 RGB instead. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3906> (cherry picked from commit dfa5238b)
-
Jeremy Bícha authored
The test failures make it appear that GNOME Shell/Mutter is broken there Gbp-Dch: Full
-
Jeremy Bícha authored
-
Jonas Ådahl authored
This means that for X11 sessions we'll do it before any windows are mapped, and before any plugin implementation is started. Doing it before a plugin is started is important, because things that the plugin does during startup can have consequences on how compositing on Xorg works. For the Xwayland case, we'll do it relatively in the setup phase. It appears to have been harmless to do it later in the post-opened signal, but there is no harm in doing it as one of the earlier steps. Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/3089 Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3329>
-
Jonas Ådahl authored
It's X11 specific, so put it in the X11 display manager object. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3329>
-
Jonas Ådahl authored
The test never noticed that the second instance never actually managed to load; it was looping a multi second retry session trying to redirect windows, meaning it failed to catch https://gitlab.gnome.org/GNOME/mutter/-/issues/3089. Fix the test so that it always waits for mutter to finish loading successfully, just like it waits fro the first. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3329>
-
Jonas Ådahl authored
Simply to make it clear that the renamed function is specific to a particular X11 initialization mode (mandatory Xwayland), put that in the name, so that it's easier to understand when this function is relevant. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3329>
-
Florian Müllner authored
Update NEWS.
-
Jeremy Bícha authored
-
Jeremy Bícha authored
Update to upstream version '46.4' with Debian dir 08d12e4080b248197b283c53b07a3e66a1b6c0a2
-
Jeremy Bícha authored
-
Jeremy Bícha authored
-
Jeremy Bícha authored
-
Jeremy Bícha authored
tagging package mutter version debian/46.4-1 * tag 'debian/46.4-1': releasing package mutter version 46.4-1 debian/libmutter-14-0.symbols: Update New upstream release Bump version to 46.4 display: Rename mandatory X11 initialization function tests/x11: Fix replace test to catch the second instance failing display: Move X11 initial focus handling to MetaX11Display x11-display: Make subwindow redirection call mode specific releasing package mutter version 46.3.1-7 Stop ignoring build test failures on Debian ports multi-texture-format: Fix limited range quantization Delete patches that aren't needed for LP#2073009 releasing package mutter version 46.3.1-6 fix logic error releasing package mutter version 46.3.1-5 Run dh_auto_test everywhere even if results are skipped on some architectures Update Chinese (Taiwan) translation clutter: Specify that input-only grabs are started inactive in API clutter: Add API to create inactive ClutterGrabs, and activate them explicitly Update German translation
-
Jeremy Bícha authored
Ubuntu isn't natively supported by Salsa CI currently so this would need something like: variables: RELEASE: 'unstable' But even the Debian autopkgtest usually fails so this isn't really worth the noise or used resources
-
Jeremy Bícha authored
File moved
debian/salsa-ci.yml
deleted
100644 → 0
This diff is collapsed.