summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* smartcard: Fix parent instance of GsdMartCardService classbenzea/fix-brightness-roundingBenjamin Berg2019-08-262-2/+2
|
* power: Fix rounding of brightness valueBenjamin Berg2019-08-231-1/+6
| | | | | | | | We rounded properly for percentage to absolute value, but we always floored the other way around. Also round when converting the absolute value to percentage, this should prevent issues where the percentage changes becaues the calculated absolute value will be resolved to a different percentage than it was calculated from.
* Update German translationTim Sabsch2019-08-221-403/+884
|
* Update Catalan translationJordi Mas2019-08-211-642/+1155
|
* Update Swedish translationAnders Jonsson2019-08-201-409/+868
|
* Updated Spanish translationDaniel Mustieles2019-08-201-19/+67
|
* Update Romanian translationDaniel Șerbănescu2019-08-191-402/+865
|
* Update Finnish translationJiri Grönroos2019-08-181-414/+1004
|
* Update Indonesian translationKukuh Syafaat2019-08-161-8/+63
|
* Update Icelandic translationSveinn í Felli2019-08-161-208/+177
| | | | (cherry picked from commit c8258744f4179b06b2ef44601e6a86540160e42f)
* Update Basque translationAsier Sarasua Garmendia2019-08-141-14/+66
|
* Update British English translationBruce Cowan2019-08-131-426/+947
|
* media-keys: Fix MprisController no longer workingHans de Goede2019-08-131-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | Since commit e4297f2ae ("media-keys: Use G_DECLARE_FINAL_TYPE for MprisController"), the MPRIS support in g-s-d no longer works. This is caused by the mpris_proxy_ready_cb changes, after the troublesome commit, the MprisController self pointer is retreived by the mpris_proxy_ready_cb like this: MprisController *self = MPRIS_CONTROLLER (object); But the object parameter to the GAsyncReadyCallback is the source object, which in this case is the just created GDBusProxy, not our MprisController object, leading to these warnings: gsd-media-keys[x]: invalid cast from 'GDBusProxy' to 'MprisController' Our MprisController is passed through the user_data pointer, so this commit fixes the code to use this instead. This fixes the warning and more importantly also makes the MPRIS support work again, since it now will now properly set self->mpris_client_proxy again. Fixes: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/437
* Updated Lithuanian translationAurimas Černius2019-08-091-403/+939
|
* Release 3.33.90GNOME_SETTINGS_DAEMON_3_33_90Carlos Garnacho2019-08-062-1/+31
|
* power: Do not require X11 GDK backendCarlos Garnacho2019-08-051-1/+0
|
* media-keys: Do not require X11 GDK backendCarlos Garnacho2019-08-051-1/+0
|
* keyboard: Do not require X11 GDK backendCarlos Garnacho2019-08-051-1/+0
|
* color: Do not require X11 GDK backendCarlos Garnacho2019-08-051-1/+0
|
* keyboard: Apply bell settings only on X11Carlos Garnacho2019-08-051-0/+3
| | | | | | Those settings don't apply on wayland, we could care really hard to emulate volume/pitch/duration there but this is essentially an easter egg. Just avoid these on Wayland sessions.
* power: Make X screensaver watchdog X11 specificCarlos Garnacho2019-08-051-1/+2
| | | | | There's no way X11 clients will be able to mess with screensaver state on wayland, so this is useless there.
* plugins: Add systemd user service files for all the pluginsBenjamin Berg2019-08-0557-88/+668
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Using the facility added in the previous commit, we can add systemd user service files for all plugins and know when they have started up. This is roughly based on the work previously done by Iain Lane <iain@orangesquash.org.uk> and Bastien Nocera hadess@hadess.net>. For each g-s-d process we have a service and a target file. This separation only exists to contain dependency failures which would cause an OnFailure action to trigger and is needed so that we can use OnFailure for the gnome-session fail-whale (gnome-session-failed.target). In general, the approach taken is that we start g-s-d processes after gnome-session-initialized.target and before gnome-session.target. We want to be able to selectively start the services only when one or more dependencies are there, or even mask out services under some conditions. The approach taken is the following: * To mask a service, use a Conflicts entry. This is e.g. used to not start certain services in GDM using Conflicts=gnome-session@gnome-login.target * To depend on multiple targets to be up and running to start, we set each of these targets in Requisite/After/PartOf/WantedBy. We always do this for gnome-session-initialized.target but this method is extensible to any number of further targets (e.g. bluetooth.target)
* common: Have plugins claim a name on the bus when they are readyIain Lane2019-08-053-0/+78
| | | | | | | The plugins are about to switch to being activated by systemd. We need a way for them to signal to systemd when they are ready. We'd like to avoid linking to libsystemd, so sd_notify() is out - let's have the plugins claim a name on the bus and then we can create Type=dbus units.
* Update POTFILES.inPiotr Drąg2019-08-031-1/+1
|
* Initial wwan pluginGuido Günther2019-08-0214-0/+1087
| | | | | | | | Heavily based on code from nm-applet. Follow-Ups: - Allow to store SIM in keyring - Handle PUKs? (or do that in g-c-c)
* color: Switch to better black body color calculationBenjamin Berg2019-07-302-3/+3
| | | | | | | | | | The planckian calculation is much better, but it also means we need to change the default from 4000K to 2700K to get a similar effect. 2700K is actually a good value as it is similar to commonly found "warm-white" artificial lights. Note that the defaults and range in g-c-c will also need to be adjusted for this change.
* color: Always use old blackbody calculationBenjamin Berg2019-07-301-2/+4
| | | | | | | | | | We tried to switch to a better way of calculating the blackbody color, but unfortunately the switch was only partial and not used in most cases. Revert this to the old calculation for stable so that we can update the default values and configuration panel when moving to the better blackbody color calculation. Fixes #403
* color: Remove compatibility ifdef's for old colord versionsBenjamin Berg2019-07-302-36/+0
| | | | | We already have a dependency on 1.3.5 which removes the need for the switches.
* clibpoard: Drop clipboard managerCarlos Garnacho2019-07-2910-1494/+0
| | | | | | This responsibility was taken over by mutter, where it can be made to work both on Wayland and X11. This clipboard manager implementation becomes superfluous then.
* mouse: Remove mouse pluginOlivier Fourdan2019-07-296-292/+0
| | | | | | | | | | | There is nothing left in the mouse plugin but the settings migration, which occurred more than 3 years ago in GNOME 3.14. Remove that plugin altogether. Note, we keep the schemas as this is still used by the XSettings plugin. https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/115
* build: Bump upower dependency to 0.99.8Carlos Garnacho2019-07-291-1/+1
| | | | | | As pointed out in !118 https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/118
* xsettings: Add an entry for the overlay scrolling settingoverlay-scrolling-settingMatthias Clasen2019-07-291-0/+1
| | | | This will be used by GTK.
* media-keys: Fetch device node from AcceleratorActivated argumentsCarlos Garnacho2019-07-291-37/+39
| | | | | | | | | | | | 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
* xsettings: Round the Xft.dpi setting to an integerYifan J2019-07-291-2/+2
| | | | | | | | | | | | | | | | | | 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.
* shell-helper: Use doubles for shell OSD dbus callsJonas Dreßler2019-07-273-27/+26
| | | | | | | | | | | 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.
* Update Croatian translationGoran Vidović2019-07-191-61/+59
|
* Update Indonesian translationKukuh Syafaat2019-07-091-388/+797
|
* Update Basque translationAsier Sarasua Garmendia2019-07-071-889/+1111
|
* Update Friulian translationFabio Tomat2019-07-061-61/+59
|
* rfkill: add a space after the connection type stringMohammed Sadiq2019-07-051-2/+2
| | | | | | otherwise, the debug messages will have them joined with the next word. This was an oversight introduced in 45cc86c410dac7c051c123934dfc2a6a49414e0b
* rfkill: Handle Airplane mode for Wireless WANMohammed Sadiq2019-07-051-6/+138
| | | | | | | | | | | | | 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
* Updated Spanish translationDaniel Mustieles2019-06-261-149/+67
|
* Release 3.33.0GNOME_SETTINGS_DAEMON_3_33_0Carlos Garnacho2019-06-252-1/+24
|
* build: Bump gsettings-desktop-schemas dependencyCarlos Garnacho2019-06-251-1/+1
| | | | We now rely on new settings there, even if for migration purposes.
* keyboard: Drop numlock state persistenceCarlos Garnacho2019-06-242-175/+10
| | | | | | This moved to mutter, and the setting to gsettings-desktop-schemas. We migrate the remember-numlock-state setting, but not the numlock state itself.
* Change "in in" to "in"scootergrisen2019-06-241-2/+2
|
* Update Croatian translationGoran Vidović2019-06-211-323/+749
|
* Update Dutch translationNathan Follens2019-06-181-383/+795
|
* mouse: Remove mousetweaks supportOlivier Fourdan2019-06-111-93/+0
| | | | | | | | | | | The pointer accessibility features handled by "mousetweaks" cannot work on Wayland, so they need to migrate in the Wayland compositor instead. Remove support for "mousetweaks" from gnome-settings daemon. https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/95 https://gitlab.gnome.org/GNOME/mutter/merge_requests/512 https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/474
* Update Friulian translationFabio Tomat2019-06-111-311/+716
|
View Lorry Controller Status