~vcs-imports/gnome-control-center/+git/gnome-control-center:arnaudb/429-master-Disable-touchpad-only-if-mouse

Last commit made on 2019-03-27
Get this branch:
git clone -b arnaudb/429-master-Disable-touchpad-only-if-mouse https://git.launchpad.net/~vcs-imports/gnome-control-center/+git/gnome-control-center

Branch merges

Branch information

Name:
arnaudb/429-master-Disable-touchpad-only-if-mouse
Repository:
lp:~vcs-imports/gnome-control-center/+git/gnome-control-center

Recent commits

47aab3c... by Ping Pong

Always allow touchpad if no other pointer device.

It was possible to completely disable
touchpad even when there was no other
pointer device. And worse, this panel
being no keyboard-browsable, the only
practical solution was then to find a
mouse and connect it to the computer.

Closes #429.

e85816f... by Robert Ancell

common: Fix crash in language chooser

A report in Red Hat bugzilla [1] shows for some reason the country is set to
NULL and this causes a crash when comparing against search terms. The solution
is to handle the NULL without crashing.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1685251

ecb809b... by gogo

Update Croatian translation

a3b2725... by Robert Ancell

online-accounts: Fix widgets added by GOA being invisible

Fixes #362

3565216... by Robert Ancell

applications: Make async file operations cancellable

The previous operations could crash if the panel was changed during an operation.

a3db60a... by Robert Ancell

applications: Rename functions as portal permssions are not Flatpak specific

a856740... by Robert Ancell

applications: Fix wrong IDs being passed to portal permission store

There were two cases of the app ID being used instead of the Flatpak ID.

b26a8bd... by Benjamin Berg <email address hidden>

display: Ensure configuration has the expected type

In almost all cases, the configuration will be "valid" in the sense that
g-c-c can represent it in the UI. However, there are cases like
mirroring setups with three monitors that we do not allow.

In case that the user has such a configuration, ensure that the
configuration we represent is actually valid according to our
expectations. This should not affect normal use cases, but allows users
to recover again if the configuration is broken for some reason.

Fixes #383

f45dcff... by Benjamin Berg <email address hidden>

display: Ensure at least one display is enabled

When the user has more than two monitors, then they can disable each
monitor separately. If the user creates an invalid configuration because
they disabled the last monitor, then enable a different one immediately.

defbceb... by Benjamin Berg <email address hidden>

display: Simplify configuration type and UI selection logic

The new logic selects a single configuration type rather than detecting
which types can be considered valid. This simplifies the UI rebuilding
somewhat, but also changes some internal behaviour. We will now always
be in the correct mode internally, even if the UI may not represent this
change (i.e. with more than two monitors it always looks the same).