mutter:wip/carlosg/fix-open-lid-flicker

Last commit made on 2019-09-04
Get this branch:
git clone -b wip/carlosg/fix-open-lid-flicker https://git.launchpad.net/mutter

Branch merges

Branch information

Name:
wip/carlosg/fix-open-lid-flicker
Repository:
lp:mutter

Recent commits

18c85c9... by Carlos Garnacho

backends: Compare gpu/crtc/output configurations before applying

This spares us from visible flickering whenever an unchanged configuration
is reapplied, eg. after lid open. The code in the X11 paths that did the
same comparisons has been removed in favor of the generic checks.

https://bugzilla.gnome.org/show_bug.cgi?id=791879

bcfac0d... by Marv-CZ

Updated Czech translation

682d43b... by gogo

Update Croatian translation

cd273e8... by Fabio Tomat <email address hidden>

Update Friulian translation

3c0067d... by Jonas Ådahl

x11: Trace XEvent processing

https://gitlab.gnome.org/GNOME/mutter/merge_requests/765

a957c2f... by Jonas Ådahl

wayland: Trace wl_surface.commit

https://gitlab.gnome.org/GNOME/mutter/merge_requests/765

908203c... by Jonas Ådahl

core: Trace various window management actions

https://gitlab.gnome.org/GNOME/mutter/merge_requests/765

2f072af... by Olivier Fourdan <email address hidden>

clutter/input-pointer-a11y: Restore pointer a11y on resume

When suspending, the devices are removed and the virtual device
associated with the corresponding core pointer is disposed.

Add the pointer accessibility virtual device to the core pointer
on resume to restore pointer accessibility on resume if enabled.

https://gitlab.gnome.org/GNOME/mutter/merge_requests/761

de98fb2... by Olivier Fourdan <email address hidden>

wayland/data-device: Restore keyboard focus on drag end

When starting a DnD operation, mutter would remove keyboard focus from
the client, only to restore it on the data offer destroy.

However, if the DnD fail, the keyboard focus is not restored, leaving
the user unable to type in the focused window, even after clicking in
the window.

That issue would show only on first attempt, as further DnD attempts
would destroy the previous data offer which would also restore the
keyboard focus.

Make sure we restore the keyboard focus on drag end as well.

https://gitlab.gnome.org/GNOME/mutter/issues/747

82c9217... by Olivier Fourdan <email address hidden>

wayland/data-device: Do not unset focus on drag start

On drag start, `data_device_start_drag()` issues a keyboard grab, which
in turn will unset the current input focus.

There is not need to unset the input focus in `data_device_start_drag()`
as this is redone in `meta_wayland_keyboard_start_grab()`

https://gitlab.gnome.org/GNOME/mutter/issues/747