Last commit made on 2019-05-21
Get this branch:
git clone -b upstream/3.28.x https://git.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell
Only Marco Trevisan (Treviño) can upload to this branch. If you are Marco Trevisan (Treviño) please log in for upload directions.

Branch merges

Branch information


Recent commits

c04b315... by Marco Trevisan (Treviño)

New upstream version 3.28.4

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

Bump version to 3.28.4

Update NEWS.

8702d66... by Carlos Garnacho

st-adjustment: Mark all properties as EXPLICIT_NOTIFY

All adjustment setter functions take good care of avoiding emission of
notify:: when it's not needed. The set_property() implementation already
calls into the setter functions, so mark the properties as EXPLICITY_NOTIFY
in order to optimize notify:: emission away through g_object_set (rather
common from JS code).

(cherry picked from commit b1b455ff1a0e856149142747e77fb1c98df34c03)

Closes: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1270

5703a25... by Marco Trevisan (Treviño)

dialog: Really set ellipsize mode in subtitle and body

Dialog's subtitle or body could not be properly wrapped, while it's ellipsized
when the text's width doesn't exceed the container size.

Clutter text has an `ellipsize` property, however in dialog's subtitle and body
we have been setting the `ellipsize-mode` property to Pango.EllipsizeMode.NONE
that is not present in the underlying GObject.

Not being an error in javascript, gjs didn't warn us about this, while at the
same time the St.Label's default Pango.EllipsizeMode.END was used.

Fixes https://gitlab.gnome.org/GNOME/gnome-shell/issues/922


(cherry picked from commit 3121c9aa29406ad85e949b697e90092f1fa6fc2e)

09fbb4a... by Carlos Garnacho

windowManager: listen actively to windows being destroyed during WS switch

Prevents gjs from dealing with already dispose()d objects.

Closes: https://gitlab.gnome.org/GNOME/gnome-shell/issues/539

(cherry-picked from b087752b5539a8cbb1d61979cb069aef8a3475be)

4c7b20e... by Andrea Azzarone

dnd: Only handle touch events in wayland

There are serveral issues around touch passive grab and touch/pointer doubly
handling to use these on X11, so we stick to single-touch/pointer there.

Cherry picked from commit 60ccdc2deb746c0d96b0268ee5034b65478ce779

Closes: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1015

9a2b2a5... by Marco Trevisan (Treviño)

New upstream version 3.28.3+git20190124

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

closeDialog: Untrack chrome when window loses focus

On X11, reactive chrome must be added to the input region in order
to work as expected. However that region works independently from
any window stacking, with the result that the unresponsive-app dialog
currently blocks all input in the "covered" area, even in windows
stacked above the unresponsive window.

The correct fix would be to track the unobscured parts of the dialog
and set the input region from that, but that's quite cumbersome. So
instead, only track chrome when the corresponding window is focused
(or the dialog itself of course).


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

messageTray: Fix sloppy backport

Commit 8111286463b8 was cherry-picked without accounting for the
screen/display API difference between 3-30 and 3-28.

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

closeDialog: Periodically check for window to become responsive again

The close dialog for non-responding windows is closed automatically
when we detect that the window is responding again. However as we
currently only ping the window in response to certain user actions
(like focusing the window or opening the window menu), this can
easily go undetected.

Address this by periodically pinging the window while the close
dialog is shown.