mutter:gnome-3-22

Last commit made on 2017-08-12
Get this branch:
git clone -b gnome-3-22 https://git.launchpad.net/mutter

Branch merges

Branch information

Name:
gnome-3-22
Repository:
lp:mutter

Recent commits

9cd8d54... by Andika Triwidada

Update Indonesian translation

8fe24c1... by Ikey Doherty <email address hidden>

backends/x11: Ensure reply is initialised to NULL

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

19f08fb... by Carlos Garnacho

xwayland: Use the right atom type for further selection requests to X11

If we translate between text/plain;charset-utf-8 from the wayland side to
UTF8_STRING on the X11 side, we want to continue all further X11 selection
requests using the same translated UTF8_STRING atom than we use in the
first XConvertSelection call.

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

40a3d67... by Olivier Fourdan <email address hidden>

wayland: Apply size hints regardless of geometry

Previously we would bail out early in xdg_toplevel_role_commit() if no
geometry change was set, ignoring the possible min/max size hints
changes.

But setting a min/max size hint without changing the geometry is
perfectly valid, so we ought to apply the min/max changes regardless of
a geometry change.

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

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

wayland: Make sure we have a pending geometry

If the client doesn't set a geometry using xdg_shell, we'll compute its
geometry based on its surface and subsurfaces.

Yet, we translate that as a window (re)size only when there is a pending
geometry, that we don't have when we computed the geometry by ourself.

Make sure we set the pending new geometry flag when computing the
geometry when it actually changed.

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

f688851... by Nigel Taylor <email address hidden>

clutter: conform/actor-graph: Add missing null-termination

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

ba317dc... by Jonas Ã…dahl

wayland/subsurface: Handle clients committing on destroyed subsurface

A client can still commit state to a destroyed subsurface. It wont
update anything on the screen, since the subsurface will not be
visible, but mutter should still handle it and not crash.

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

a8b06af... by =?utf-8?q?Florian_M=C3=BCllner?= <email address hidden>

Bump version to 3.22.4

Update NEWS.

5b232a8... by Daniel Stone <email address hidden>

xwayland: Fix lockfile size confusion

Similarly to Weston (where this code originated), there were two errors
in the X11 lockfile handling.

Firstly, after reading 11 characters from the lock file (which could
have been placed by any process), there was no guarantee of
NUL-termination, meaning strtol could've theoretically run off the end
of the string.

Secondly, whilst writing the new lock, the trailing NUL byte was not
correctly accounted for. The size passed as an input to snprintf takes
the maximum size of the string including the trailing NUL, whilst the
return (and the input to write) gives the actual size of the string
without the trailing NUL.

The code did attempt to check the return value, however snprintf returns
the size of the _potential_ string written, before snprintf culls it, so
this was off by one, and the LF was not being written.

Signed-off-by: Daniel Stone <email address hidden>

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

50c8ee9... by Shantanu Goel

frames: use correct variable in for loop assignment

update_context_styles is using the wrong variable when advancing
to the next key in the hash table which can cause an infinite
loop if # of variants is ever greater than 1.

This problem was originally reported here:

https://github.com/linuxmint/Cinnamon/issues/5254

The following patch was commited in Mint:

https://github.com/linuxmint/muffin/commit/6120bdde

This patch is just a shorter version of the Mint patch
and they deserve all the credit for the idea.

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