gnome-shell:wip/fmuellner/duplicate-favs

Last commit made on 2018-10-08
Get this branch:
git clone -b wip/fmuellner/duplicate-favs https://git.launchpad.net/gnome-shell

Branch merges

Branch information

Name:
wip/fmuellner/duplicate-favs
Repository:
lp:gnome-shell

Recent commits

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

appFavorites: Don't add app explicitly

When adding a favorite, we add the ID to the list of favorites, save the
setting and add the new app to the favorites map. However as writing the
settings value already results in reload() to update the favorites map,
the new app is usually already in the map when we add it.

The only exception is when the ID was found in the RENAMED_DESKTOP_IDS map,
in which case we end up adding both the renamed app and the original one.
Fix this by simply relying on reload() to properly update the map, just like
we already do in _removeFavorite().

https://gitlab.gnome.org/GNOME/gnome-shell/issues/471

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

layout: Don't update input region on wayland

We already see all events on wayland, so we can save us the work
of computing the XFixes region there.

https://gitlab.gnome.org/GNOME/gnome-shell/issues/273

7190666... 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).

https://gitlab.gnome.org/GNOME/gnome-shell/issues/273

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

automountManager: Explicitly track active operations

As a mount operation's UI may be reused (for example after mistyping
the password), we only close the operation once the mount has finished
(successfully or with error).

We therefore need to track ongoing operations, which we currently do
by monkey-patching the corresponding volume object. However while the
underlying GVolume object indeed remains the same through-out the
operation, the JS wrapper object isn't referenced anywhere and may
thus be garbage collected, resulting in a stuck dialog.

Fix this issue by tracking active operations explicitly, so that all
involved objects are referenced until the end of the operation.

https://gitlab.gnome.org/GNOME/gnome-shell/issues/565

669582d... by Cheng-Chia Tseng

Update Chinese (Taiwan) translation

d9ad834... by Marv-CZ

Updated Czech translation

fffe58f... by Andrea Azzarone

viewSelector: Don't unfocus other modals on reset

Don't drop the key focus on Clutter's side if anything but the overview has
pushed a modal (e.g. system modals when activated using the overview).

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

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

inputMethod: Fix setting surrounding text

The underlying ibus method expects an object of type IBusText rather
than a plain string.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/228

361955d... by Bastien Nocera

appFavorites: Add evince to rename list

Evince 3.30 changed the desktop filename. Without this patch,
evince will disappear from the dock.

873c26f... by Yuras

Update Belarusian translation