~vcs-imports/gnome-settings-daemon/+git/gnome-settings-daemon:gnome-3-24

Last commit made on 2018-03-21
Get this branch:
git clone -b gnome-3-24 https://git.launchpad.net/~vcs-imports/gnome-settings-daemon/+git/gnome-settings-daemon

Branch merges

Branch information

Recent commits

da782b1... by Debarshi Ray <email address hidden>

3.24.4

a86bef4... by Sebastien Bacher

housekeeping: own the dbus name so the service can be contacted

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

134a405... by Carlos Garnacho

common: Check for wayland before building GsdUdevDeviceManager

Udev is rather common, so this check doesn't suffice if anyone wants
to build with no wayland support whatsoever.

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

e6c6956... by Benjamin Tissoires <email address hidden>

Fix screen mapping for Cintiqs and others

Size-based input/output matching doesn't raise the "found" flag, which
would result on input_info_guess_candidates() still trying to assign the
builtin output to the input device if that is the only match found.

For screen integrated devices (i.e. not on the builtin output) this is
and undesirable possibility, setting the "found" flag to TRUE results on
the correct output being assigned.

Signed-off-by: Benjamin Tissoires <email address hidden>

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

276c063... by Carlos Garnacho

common: Ensure screen integrated devices get remapped on hotplug

GsdDeviceMapper used to refrain from remapping devices that already had
a configured output. This however results on wrong mapping when the input
device is plugged before the output, since the heuristics will attempt
really hard to find an output for the device before the real one is
available, and not remapped again when the output is plugged.

Fix this by forcing remapping on all screen-integrated devices on every
hotplug event, so the input device will get remapped to the right screen
(hopefully!) when it is plugged. This is not applied to devices mapped
to the builtin output, or those with no attached output at all, as in both
of these cases the configured output should be left static.

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

4c539ca... by Bastien Nocera

power: Don't react to light changes if not at console

As iio-sensor-proxy isn't yet clever enough to only send property
changes signals to clients that have claimed a sensor, disconnect
the properties-changed signal so we don't attempt to make brightness
changes when we're not on the active seat.

See https://github.com/hadess/iio-sensor-proxy/issues/210
See https://bugzilla.gnome.org/show_bug.cgi?id=756539
See https://bugzilla.gnome.org/show_bug.cgi?id=773685
See https://bugzilla.gnome.org/show_bug.cgi?id=764896
See https://bugzilla.redhat.com/show_bug.cgi?id=1322588

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

ba9bb01... by Hannie Dumoleyn

Update Dutch translation

c8d14bf... by Tong Hui <email address hidden>

Update zh_CN translation

7f5cc5c... by Matej Urbančič

Updated Slovenian translation

6e719ad... by Jonathan

common: include missing header files for LC_ALL

fixes commit 9fddecc4641709308dec0300a778a32a2b17aafd.

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