delta/mutter.git, branch wip/carlosg/keymap-updates

backends/native: Update keymap state on latched modifier updates

2021-01-21T14:35:06+00:00

The input thread refactors missed to update the MetaKeymapNative state when
the keys that trigger the latched modifiers are being pressed. Let that happen
here.

Part-of:

xwayland: Do not rely on X-lock files

2021-01-21T11:57:07+00:00

Some X11 servers may not always create a lock file, yet mutter uses the
lock file to find a possible display number and then tries to bind to
the socket corresponding to that display number.

If it fails to bind, it will simply bail out. As a result, if an X11
server is already listening on that display but hadn't created a lock
file, mutter won't be able to start Xwayland.

To avoid that possible issue, make mutter retry with another display
for a given number of tries when binding fails even though the display
was supposed to be available based on the lock file presence.

Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/1604
Part-of:

xwayland: Check for X11 unix directory only once

2021-01-21T07:48:39+00:00

The function choose_xdisplay() calls open_display_sockets() which calls
ensure_x11_unix_dir().

We don't need to do that from within the loop though, as the directory
/tmp/.X11-unix is the same regardless of the display number.

Move the call to ensure_x11_unix_dir() from open_display_sockets() to
choose_xdisplay() prior to enter the display loop.

Part-of:

xwayland: Propagate error if display sockets failed

2021-01-21T07:48:39+00:00

In case of failure to open the display sockets, we would not propagatre
the error which can cause a crash when trying to show the error message.

Properly propagate the error to avoid the crash.

Part-of:

xwayland: Start Xwayland on connection to either public X11 socket

2021-01-21T07:48:39+00:00

Fixes: https://gitlab.gnome.org/GNOME/mutter/-/issues/1454
(cherry picked from commit 7b2815077fa1053069e00c0a21b2c3038f4b0d1c)

Part-of:

Revert "wayland: Drop Xwayland abstract socket"

2021-01-21T07:48:39+00:00

This reverts commit e2123768f635ee892702c8c515cf987261ba5518.  Various
container/chroot (e.g. Snaps, pressure-vessel) systems still depend on
the presence of the abstract X11 socket.

Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/1613
(cherry picked from commit ea2192c4899ac7897efca31e8e85c157895950ac)

Part-of:

wayland: Handle forced Xwayland shutdown elegantly

2021-01-20T15:55:08+00:00

In the shutdown paths we check with the X11 display whether there's
remaining clients. However this happens in paths that happen after
the MetaX11Display vanished in the case of Xwayland crash.

Since in that situation the clients are forcibly vanishing too,
skip the client check.

Part-of:

Update Portuguese translation

2021-01-20T11:50:55+00:00

backend/native: Destroy logind helper after seat

2021-01-19T21:54:32+00:00

Otherwise we don't actually close input devices using it, since that
would happen after meta_launcher_free() was called.

Part-of:

backend: Tear down in dispose() instead of finalize()

2021-01-19T21:54:32+00:00

This means backend implementations can have more control of the order of
how things are destroyed. To be precise, this will, in the next commit,
allow us to destroy the logind integration after the clutter backend
thus the libinput owning seat, that uses the logind integration to
release input devices.

Part-of: