delta/mutter.git/src, branch document-button-values

Document button values in the RemoteDesktop api

2021-05-01T00:40:21+00:00

I spent some time trying to pass X11 button values
and was a bit miffed that it didn't work. So lets
document the expected values to minimize future
frustation.

xwayland: Check permissions on /tmp/.X11-unix

2021-03-18T16:43:02+00:00

For Xwayland, mutter creates the sockets in the standard /tmp/.X11-unix
directory.

Yet, if that directory already exists, it may have been created by
another user with full control over the created socket.

To avoid that issue, if the directory /tmp/.X11-unix already exists,
check that the permissions are as we expect, i.e. the directory belongs
to either root or the user herself, is writable and has the sticky bit.

Thanks to fabian@ritter-vogt.de for reporting that issue.

https://gitlab.gnome.org/GNOME/mutter/-/issues/1708

Part-of:

xwayland: Use defines for X11 directory and path

2021-03-18T16:43:02+00:00

Rather than repeating the same strings for X11 directory and path all
around the code, use a define.

No functional change.

Part-of:

wayland/surface: Do not free placement ops of cached state

2021-03-15T12:49:45+00:00

The list gets freed in `meta_wayland_surface_state_clear()`
if the pointer is still set.

Fixes ba8499f9ec0ca017f11bcc8e50e66302b2f73aa7

Part-of:

wayland/subsurface: Move placement ops to the parents pending state

2021-03-13T23:38:18+00:00

Unlike other subsurface state, placement operations need to get
applied in order. As per spec:

```
Requests are handled in order and applied immediately to a pending
state. The final pending state is copied to the active state the
next time the state of the parent surface is applied.
```

Having placement operations being part of the subsurface state
makes it difficult to support arbitrary orderings. Make them
part of the parents surface pending state instead.

Closes https://gitlab.gnome.org/GNOME/mutter/-/issues/1691

Part-of:

main: Expose hooks to manage context with more granularity

2021-03-13T18:56:21+00:00

This is to allow gnome-shell to tear down more gracefully. It's a stop
gap solution until there is a better context handling system, but will
have to do for now.

Part-of:

backend: Destroy stage when destroying backend

2021-03-13T18:56:21+00:00

Otherwise we leak it.

Part-of:

backend: Destroy backend explicitly

2021-03-13T18:56:21+00:00

This now ensures that calling meta_release_backend() destroys the
backend.

Part-of:

backend: Destroy clutter backend explicitly

2021-03-13T18:56:21+00:00

Instead of relying on reference counting, destroy it with a destroy
function that calls run_dispose() on before removing a reference.

Part-of:

backend: Destroy seat explicitly

2021-03-13T18:56:21+00:00

Don't let any dangling pointer keeping it alive.

Part-of: