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

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

Benjamin Tissoires authored Nov 02, 2017 and Carlos Garnacho committed Jan 15, 2018

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 <benjamin.tissoires@redhat.com>

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

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

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

Jonathan Kang authored Aug 30, 2017 and Rui Matos committed Aug 30, 2017

fixes commit 9fddecc4.

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

Without that the notifications are displayed untranslated
https://bugzilla.gnome.org/show_bug.cgi?id=786978

Emmanuele Bassi authored Aug 21, 2017 and Bastien Nocera committed Aug 23, 2017

Commit 476154fe and commit 867b2039 broke the build.

Full Continuous log:

http://build.gnome.org/continuous/buildmaster/builds/2017/08/21/49/build/log-gnome-settings-daemon.txt

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

This is the equivalent of "undefined" for the accelerometer
orientation. Don't use it to prime our nice ambient light
readings curve.

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

backlight_enable() does 2 things, fiddle with the DPMS as well
as attempt to claim the light sensor. But the light sensor
claim attempt will always fail as the "session_is_active" variable
has not been initialised yet. So just try a tad later for it
to work as soon as you've logged into the session.

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

We need to both watch for the signal and setup inhibitors
to be informed about suspend attempts, so move the comment
above both calls.

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

We definitely do want to be able to disable light sensor
monitoring even if we're not in an active session any more.

The only case this conditional was supposed to prevent is
trying to claim the light sensor when the session is inactive.
Anything else should be allowed.

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

Carlos Garnacho authored Jul 21, 2017 and Rui Matos committed Jul 22, 2017

GsdDeviceMapper has no business with non system/display-attached
devices. Make it really sure those are untouched.

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

Florian Müllner authored Jul 08, 2017 and Rui Matos committed Jul 22, 2017

If a key is not actually grabbed when we try to ungrab it, we register
the request and ungrab the key after the grab operation has completed.
This avoids leaking bindings when a shortcut is disabled while a grab
operation is in progress, however it means that any grab operation done
after trying to ungrab an unset shortcut will be immediately undone.
This is the currently the case when a shortcut settings changes, which
we handle as a simple combination of ungrab and grab - we need to make
sure to only request a later ungrab if there's a pending grab.

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

Florian Müllner authored Jul 10, 2017 and Rui Matos committed Jul 22, 2017

We keep track of ongoing and requested grab operations by registering
a key in a corresponding hash table. However currently we use the
key's current binding as hash table key, which is subject to changes.
To not mess up the tracking when a setting changes at the wrong time,
base the hash table keys on immutable properties that uniquely identify
the key.

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

Laurent Bigonville authored Jul 07, 2017 and Rui Matos committed Jul 22, 2017

Currently, the "us" keyboard layout is always added the first time the
user is login in, this should only be necessary if the system configured
layout cannot be determined.

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

Carlos Garnacho authored Jun 07, 2017 and Rui Matos committed Jul 22, 2017

The peripherals settings moved to gsettings-desktop-schemas, but the
convert script wasn't updated to it.

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

If the device has no ID_VENDOR_ID/ID_MODEL_ID udev properties, resort
to reading those from sysfs attributes.

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

This would yield the wrong size, specially harmful for touchscreens as
there's no other backing heuristic here. This may result in touchscreens
being assigned the wrong output if there's several of them.

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

The interpolation function expects factor values between 0. and 1.,
so we need to either pass the difference between current time and
transition start, or between transition end and current time - not
the difference between transition start and current time, which is
always negative.

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

Alan Coopersmith authored Jun 10, 2017 and Rui Matos committed Jun 12, 2017

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



Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>

Iain Lane authored May 19, 2017 and Jeremy Bicha committed May 19, 2017

Distributions might want to be able to run their tests during package
builds, for example.

Compile the schema and set GSETTINGS_SCHEMA_DIR to the build dir.

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

Hans de Goede authored May 08, 2017 and Rui Matos committed May 09, 2017

On laptops with hybrid graphics the LCD panel may be connected to
a mux so that it can be driven by either GPU. In this case both
GPU drivers will register a raw backlight interface for their
LCD panel connector and g-s-d needs to pick the one for the enabled
connector rather then just picking the first one.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683445
https://bugzilla.gnome.org/show_bug.cgi?id=782211

If we handle rfkill input keys without telling rfkill, we end up
handling those keys in gnome-settings-daemon, as well as in the kernel's
rfkill-input driver. As handling all the different keys would require
more work than possible in a stable release, we'll let rfkill-input
handle this, and lose the OSD for now.

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

Bizarrely, since 2011, gnome-settings-daemon was documented as using
org.gnome.SettingsDaemon.MediaKeys D-Bus name, but everybody ended up
using the org.gnome.SettingsDaemon owned by the daemon instead, and
never reported the discrepancy.

This fixes the code to match the 6-year old API as documented by owning
the org.gnome.SettingsDaemon.MediaKeys as well as the
org.gnome.SettingsDaemon D-Bus name to give 3rd-party users time to
adapt their code.

The portion of this patch adding the org.gnome.SettingsDaemon.MediaKeys
name owning will need to be backported as far as reasonably possible by
distributions, and all users of the API changed before GNOME 3.26. This
would obviously have been easier if the problem was reported when
detected, committer of this fix included.

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

Ray Strode authored Apr 18, 2017 and Bastien Nocera committed Apr 21, 2017

The plugin names don't have a gsd- prefix, so the login screen
is currently getting started with no plugins!

This commit fixes that, and as a consequence, fixes hidpi scaling
for the login screen.

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

Antoine Jacoutot authored Apr 18, 2017 and Bastien Nocera committed Apr 21, 2017

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