summaryrefslogtreecommitdiff
path: root/data
Commit message (Collapse)AuthorAgeFilesLines
* power: default to sleep after 15 minutes rather than 20 minutesMichael Catanzaro2023-02-221-2/+2
| | | | | | | | | | | | | | | | | | | | | | Beginning with GNOME 3.28, we began defaulting to sleep after 20 minutes in order to comply with some European regulations: https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32013R0801&from=EN See commit 2fdb48fa3333638cee889b8bb80dc1d2b65aaa4a for details. Anyway, there is a flaw in our plan: even if we tune the setting to 20 minutes, this doesn't actually work in practice for manufacturers affected by these regulations because the system might only *begin* to suspend after 20 minutes have passed, but they are actually required to *finish* suspending before this time. Additionally, the timeout won't begin until the system has fully booted into GNOME, which adds additional uncertainty. Solution: sleep after 15 minutes. This is reportedly what Ubuntu is doing for OEM installs. And it's closer to the Windows default of 10 minutes. https://pagure.io/fedora-workstation/issue/360
* media-keys: Remove screencast key handlingIvan Molodetskikh2022-02-121-16/+0
| | | | gnome-shell itself now handles the screencast key too.
* media-keys: Remove screenshot key handlingIvan Molodetskikh2022-02-121-60/+0
| | | | | gnome-shell itself now handles the screenshot keys. This is required to easily provide same-frame response to pressing a screenshot key.
* power: Enable power-saver profile when low on batteryBastien Nocera2021-07-221-0/+5
| | | | | When low on battery, and if the feature is enabled, hold the power profile to "power-saver" until the battery is sufficiently recharged.
* build: Bump required meson versionBastien Nocera2021-07-161-1/+0
| | | | | | | | And remove the "install" arg in configure_file() to quiet the warnings WARNING: Project specifies a minimum meson_version '>= 0.47.0' but uses features which were added in newer versions: * 0.49.0: {'/ with string arguments'} * 0.50.0: {'install arg in configure_file'}
* data: Drop reference to non-existing schemaCarlos Garnacho2021-01-151-1/+0
| | | | | The mouse schema went deprecated and renamed locally. We shouldn't reference the old child anymore.
* xsettings: Adopt drag-threshold/double-click settings from ↵wip/carlosg/shuffle-font-mouse-settingsCarlos Garnacho2021-01-121-12/+10
| | | | | | gsettings-desktop-schemas These settings are more universal than gnome-settings-daemon.
* xsettings: Use font aa/hinting/rgba-order settings from ↵Carlos Garnacho2021-01-121-15/+17
| | | | | | gsettings-desktop-schemas Move these settings there, as they are more universal than gnome-settings-daemon.
* media-keys: Add static mapping for XF86RotationLockToggleHans de Goede2020-07-061-1/+1
| | | | | | | | | | Some tablets have a dedicated button for toggling accelerometer based rotation on/off. A while ago the XF86RotationLockToggle keysym was added for this and this has been hooked up through all the plumbing layers (xkeyboard-config, libxkb-common) now. Add a static mapping for this, to make these buttons work ootb. This has been tested with such a button on a Lenovo Thinkpad 10 tablet.
* Change "GNOME settings" to "GNOME Settings"scootergrisen2019-08-261-3/+3
|
* media-keys: Add volume step keyHaxk202019-08-261-0/+6
| | | | This adds new key so that it the value of the key can be edited with dconf.
* Initial wwan pluginGuido Günther2019-08-022-0/+14
| | | | | | | | 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-301-1/+1
| | | | | | | | | | 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.
* keyboard: Drop numlock state persistenceCarlos Garnacho2019-06-241-10/+5
| | | | | | 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
|
* mouse: remove locate-pointerOlivier Fourdan2019-06-052-5/+0
| | | | | | | | | | | | | | | | | The current implementation in gnome-settings-daemon relies on X11 and cannot work on Wayland. Remove the locate-pointer functionality and the relevant helper from gnome-settings-daemon to move to the Wayland compositor instead, i.e. mutter/gnome-shell. Also, move the gsettings key for "locate-pointer" to "org.gnome.desktop. interface". https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/86 https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/merge_requests/19 https://gitlab.gnome.org/GNOME/mutter/merge_requests/453 https://gitlab.gnome.org/GNOME/gnome-shell/issues/981
* media-keys: Move all keyboard bindings into settingsBenjamin Berg2019-05-271-23/+399
| | | | | | | This creates new "X-static" binding entries in the configuration store which store all the previously hard-coded keys. The effect is that it is possible for users to override the behaviour, with the caveat that newly added keybindings will not be picked up for that key.
* media-keys: Make internal keybindings to be listsBenjamin Berg2019-05-271-6/+184
| | | | | | | | | | | | | | | | | | | This will allow us moving all the keybindings into gsettings and also allows users to override keybindings when desired. If a keybinding is for a "hardware" key, then we add a dummy first entry. This allows users to define a further keybinding in g-c-c while keeping the hardware key functional. Note that we are not allowing multiple keybindings for custom keybindings for now. When migrating, any overriden keybinding is inserted into the first slot of the default value. This means that for e.g. the audio keys we are re-adding the hardware button. This could potentially create collisions if the user changed the default binding *and* assigned the hardware button to another purpose. Unfortunately, users will need to correct this manually.
* wacom: Migrate 'display' setting to 'output' for opaque tabletsCarlos Garnacho2018-12-061-0/+5
| | | | | | Display mapping is user-settable on opaque tablets, thus it makes sense to migrate this setting to the new one. For other tablets, heuristics should apply, which is the behavior expected from the unset key.
* data: Fix typo in night light description in schemabenzea/nightlight-fixesAnders Jonsson2018-06-201-1/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=779336
* data: Compile gschema files at build time and copy into testsBenjamin Berg2018-04-101-3/+13
| | | | Without this we need to install the GSchema files for testing purposes.
* media-keys: Move microphone mute button to gsettingsBenjamin Berg2018-03-161-0/+5
| | | | | | | | Allow users to configure the microphone mute key. Many laptops do not have a microphone mute key, so it can make sense for users to map it to another key (e.g. Shift+Mute). https://bugzilla.gnome.org/show_bug.cgi?id=793596
* media-keys: Improve volume keybinding descriptionsBenjamin Berg2018-03-161-4/+4
| | | | | | | | This changes the volume related strings clarifying that the mute key toggles the state and changing "system volume" to "volume" as the "system" part is not very meaningful. https://bugzilla.gnome.org/show_bug.cgi?id=793596
* build: Remove autotoolsIñigo Martínez2018-02-052-56/+0
| | | | | | | To avoid the burden of maintaining multiple build systems, this patch removes autotools support. https://bugzilla.gnome.org/show_bug.cgi?id=793087
* build: Migrate from Intltool to GettextIñigo Martínez2018-02-0517-514/+516
| | | | | | | | | | | | | Recent versions of Gettext are able to translate several formats that are used in GNOME applications. This patch migrates from Intltool to Gettext by using meson's i18n features. Explicit encoding has also been added to the gschema files due to an issue in gettext[0] with default encoding in XML files. https://bugzilla.gnome.org/show_bug.cgi?id=793087 [0] https://savannah.gnu.org/bugs/?52932
* build: Port to meson build systemIñigo Martínez2018-02-051-0/+66
| | | | | | | | meson is a build system focused on speed an ease of use, which helps speeding up the software development. This patch adds meson support along autotools. https://bugzilla.gnome.org/show_bug.cgi?id=793087
* power: Default to suspend after 20 minutes of inactivityBastien Nocera2018-01-161-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | According to the EU Commission Regulation No 801/2013, amending Regulation (EC) No 1275/2008: " The default period of time after which the power management function, or a similar function, switches the equipment automatically into a condition providing networked standby shall not exceed 20 minutes. " (Full text at: http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32013R0801&from=EN ) Though this addition only seems to be applicable to "networked equipment", the original directive and its 2008 "ecodesign" regulation mentions that computers are covered (as "Information technology equipment intended primarily for use in the domestic environment"), and that: " When equipment is not providing the main function, or when other energy-using product(s) are not dependent on its functions, equipment shall, unless inappropriate for the intended use, offer a power management function, or a similar function, that switches equipment after the shortest possible period of time appropriate for the intended use of the equipment, automatically into [standby mode]. " (Full text at: http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32008R1275&from=EN) Furthermore, the EnergyStar standard that allows shipping into the USA mentions that, for most computers types: " Sleep Mode shall be set to activate after no more than 30 minutes of user inactivity. " (Full text at: http://docketpublic.energy.ca.gov/PublicDocuments/16-AAER-02/TN213577_20160909T143121_ENERGY_STAR_Product_Specification_for_Computers_Eligibility_Cri.pdf) https://bugzilla.gnome.org/show_bug.cgi?id=681869
* media-keys: Restore interactive option for power buttonJeremy Bicha2017-08-071-2/+3
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=781108
* xrandr: Remove pluginRui Matos2017-07-145-27/+0
| | | | | | | This functionality is moving to mutter and the DBus API is no longer used. https://bugzilla.gnome.org/show_bug.cgi?id=782231
* data: Fix GConf->GSettings convert scriptCarlos Garnacho2017-07-121-12/+0
| | | | | | | 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
* data: Mark forgotten strings in gschema files for translationPiotr Drąg2017-05-244-59/+59
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=710649
* data: use Unicode in schemas translatable stringsPiotr Drąg2017-02-141-1/+1
| | | | | | See https://developer.gnome.org/hig/stable/typography.html https://bugzilla.gnome.org/show_bug.cgi?id=772488
* color: Adjust Night Light default manual timeJeremy Bicha2017-02-131-2/+2
| | | | | | 8 pm to 6 am https://bugzilla.gnome.org/show_bug.cgi?id=778459
* color: Fix a typo in key summaryPiotr Drąg2017-02-121-1/+1
|
* wacom: use Unicode in translatable stringsPiotr Drąg2017-02-111-1/+1
| | | | | | See https://developer.gnome.org/hig/stable/typography.html https://bugzilla.gnome.org/show_bug.cgi?id=772488
* xsettings: use Unicode in translatable stringsPiotr Drąg2017-02-111-3/+3
| | | | | | See https://developer.gnome.org/hig/stable/typography.html https://bugzilla.gnome.org/show_bug.cgi?id=772488
* xrandr: use Unicode in translatable stringsPiotr Drąg2017-02-111-2/+2
| | | | | | See https://developer.gnome.org/hig/stable/typography.html https://bugzilla.gnome.org/show_bug.cgi?id=772488
* schemas: use Unicode in translatable stringsPiotr Drąg2017-02-111-5/+5
| | | | See https://developer.gnome.org/hig/stable/typography.html
* wacom: Implement minimal data migrationCarlos Garnacho2017-02-101-6/+6
| | | | | | | Unfortunately we can't properly lookup the schemas for styli and button paths (that is, without a stylus or button path to construct settings paths from). However, support the tablet-wide settings on device hotplug.
* color: Rename 'Natural Light Filter' to 'Night Light'Richard Hughes2017-02-101-11/+11
|
* color: Valid latitude range is between -90 and +90Richard Hughes2017-02-091-1/+1
|
* Revert "color: Valid latitude range is between -90 and +90"Richard Hughes2017-02-091-1/+1
| | | | This reverts commit d1e0b294c9aa701d0ec704630333893f2a1a1e8f.
* color: Valid latitude range is between -90 and +90Richard Hughes2017-02-091-1/+1
|
* color: Add natural light functionalityRichard Hughes2017-02-091-0/+30
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=778039
* data: Adapt pkg-config file for API removalBastien Nocera2016-10-112-19/+1
| | | | | | | We don't have an API anymore, plugins are now stand-alone daemons, but we still need to install enumeration headers. https://bugzilla.gnome.org/show_bug.cgi?id=772370
* main: Remove gnome-settings-daemon binaryBastien Nocera2016-10-112-20/+0
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=772370
* main: Remove GSettings override for plugin priorityBastien Nocera2016-10-1115-179/+0
| | | | | | There's a default value already available in the plugin file itself. https://bugzilla.gnome.org/show_bug.cgi?id=772370
* main: Remove ability to start/stop individual pluginsBastien Nocera2016-10-1114-112/+0
| | | | | | | All the plugins are now enabled by default, until we use another way to start them individually. https://bugzilla.gnome.org/show_bug.cgi?id=772370
* main: Remove localeexec wrapperBastien Nocera2016-09-281-1/+1
| | | | | | | | | Now that gnome-session handles exporting locale information, we don't need to do this ourselves anymore. See https://bugzilla.gnome.org/show_bug.cgi?id=756324 https://bugzilla.gnome.org/show_bug.cgi?id=766180
* common: Remove "hotplug-command" helperBastien Nocera2016-01-041-8/+0
| | | | | | | | | As we're not responsible for configuring input devices (mutter/gnome-shell is), the custom command to run when devices appear doesn't make sense any more, as it won't ever block the configuration of input devices. https://bugzilla.gnome.org/show_bug.cgi?id=759599
View Lorry Controller Status