~vcs-imports/gnome-settings-daemon/+git/gnome-settings-daemon:overlay-scrolling-setting

Last commit made on 2019-07-29
Get this branch:
git clone -b overlay-scrolling-setting https://git.launchpad.net/~vcs-imports/gnome-settings-daemon/+git/gnome-settings-daemon

Branch merges

Branch information

Name:
overlay-scrolling-setting
Repository:
lp:~vcs-imports/gnome-settings-daemon/+git/gnome-settings-daemon

Recent commits

6e79096... by Matthias Clasen <email address hidden>

xsettings: Add an entry for the overlay scrolling setting

This will be used by GTK.

26a4e44... by Carlos Garnacho

media-keys: Fetch device node from AcceleratorActivated arguments

Gnome-shell now passes the additional device-node parameter in the variant
we can use to directly look up the right stream for the key event, so
pass it all the way through.

In order to add some wiggle room, still handle the device-id argument as
a fallback, so it works in combination with older gnome-shell. Only do it
on X11 sessions though, as the device ID is only meaningful there.

Related: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/618

25c7cc7... by Yifan J <email address hidden>

xsettings: Round the Xft.dpi setting to an integer

When using gnome-tweaks to set a text scale factor that is not a
multiple of 0.25 (e.g. 1.1), Xft.dpi would be calculated as a
floating point number, which breaks the fdo spec:

https://www.freedesktop.org/wiki/Specifications/XSettingsRegistry/

Although GNOME could handle the floating point Xft.dpi, graphical
programs restrictively followed the above-mentioned spec would be
influenced negatively. For example, QT applications (running on
GNOME desktop) may ignore text scaling factor when Xft.dpi was
calculated as a floating point number:

https://bugreports.qt.io/browse/QTBUG-64738

The patch at the same time has few impact to GNOME itself.

65f6de3... by =?utf-8?q?Jonas_Dre=C3=9Fler?= <email address hidden>

shell-helper: Use doubles for shell OSD dbus calls

Allow for more precise values to be sent to the shell to fix a bug
where the volume icon in the shells OSD is not the "muted" icon while
the volume bar shows a value of 0.

This happened because casting the volume to an integer value might
return 0 while the value actually is near 0. Since we also generate the
icon name inside media-keys and use the non-casted value for that, the
icon and the volume we show in the shell would be different.

1e01959... by gogo

Update Croatian translation

a808390... by Kukuh Syafaat

Update Indonesian translation

8c0ace5... by Asier Sarasua Garmendia

Update Basque translation

c9d2650... by Fabio Tomat <email address hidden>

Update Friulian translation

c6b8fe1... by Mohammed Sadiq <email address hidden>

rfkill: add a space after the connection type string

otherwise, the debug messages will have them joined with the next word.

This was an oversight introduced in 45cc86c410dac7c051c123934dfc2a6a49414e0b

45cc86c... by Mohammed Sadiq <email address hidden>

rfkill: Handle Airplane mode for Wireless WAN

This commit allows handling airplane mode for WWAN interfaces
which will be handled via rfkill and Modem Manager.

The following boolean DBUS properties are added:

* WwanAirplaneMode: read/write
* WwanHardwareAirplaneMode: read
* WwanHasAirplaneMode: read

https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/414