summaryrefslogtreecommitdiff
path: root/plugins
Commit message (Collapse)AuthorAgeFilesLines
* housekeeping: clean up x-large and xx-large thumbnailsCalvin Walton2023-05-111-0/+12
| | | | | | | | | | | | | | | | Support for two new thumbnails directories named "x-large" and "xx-large" were added to the XDG thumbnail-spec in 2020 and to gnome-desktop in GNOME 40. They started to be used by nautilus in GNOME 43 to have larger/sharper thumbnails on HiDPI screens. But the housekeeper never got updated, so the thumbnail cache has unbounded growth. I realized this problem when I was trying to debug a low disk space condition, and realized that my thumbnail cache was 10GiB in size. Add the new directories. They're only added to the XDG cache path, since any application new enough to generate these thumbnail sizes would be using that path.
* xsettings: Don't force HighContrast icon themeFlorian Müllner2023-04-181-1/+1
| | | | | The theme is considered deprecated in favor of symbolic icons from the regular theme.
* rfkill: Monitor WwanEnabled property changes properlyMaxim Mikityanskiy2023-04-181-18/+11
| | | | | | | | | | | | | | | | | | | | | g-signal is not fired on property changes, so nm_signal is never called, and all changes of NetworkManager's WwanEnabled property are missed. That leads to an inability to disable the airplane mode on laptops with WWAN after the airplane mode was once enabled by button. Fix this by subscribing to g-properties-changed to actually listen to the updates of WwanEnabled. It also makes the code simpler. The bug was caused by a breaking change in NetworkManager [1] when it deprecated the custom signal in favor of the standard PropertiesChanged on org.freedesktop.DBus.Properties, and gnome-settings-daemon still used the old one. The standard one is supported since NetworkManager 1.2.0, as noted here [2]. [1]: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/853 [2]: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/6fb917178aa19c61e909957f5146aa4565e0cb2f Fixes: d74b6de142a2 ("rfkill: watch and set NetworkManager wwan-enabled")
* power: Initialize check for VM environment earlierFelipe Borges2023-04-181-3/+3
| | | | | | Otherwise it will be called uninitialized when auto suspending. Fixes #736
* gsd-power-manager: Connect to light sensor asyncGuido Günther2023-04-171-14/+47
| | | | | | | | | | | Claiming the light sensor can take a noticeable amount of time when the sensor is being polled constantly (e.g. via monitor-sensor). Due to the function being invoked in backlight_enable this can lead to a noticeable delay when unblanking via key press. Fix this by claiming the sensor async. Fixes: https://gitlab.gnome.org/World/Phosh/phosh/-/issues/915
* smartcard: check for the addition of new smartcard readersDavid Härdeman2023-04-131-1/+6
| | | | | | | | | | | | gsd-smartcard currently checks for the insertion/removal of smartcards in reader devices which where present at the time gsd-smartcard was started, but does not account for new smartcard readers appearing after gsd-smartcard was started. This patch adds support for checking for the addition of new slots (i.e. smartcard readers), which is necessary to support devices like the Yubikey (a "reader" and a smartcard) which may be inserted after gsd-smartcard was started.
* power: Drop unused variableCarlos Garnacho2023-02-141-4/+0
| | | | This variable went unused in commit daaa85d69757.
* power: Use distinct icons when showing battery notificationsCarlos Garnacho2023-02-091-16/+8
| | | | | | | | | | | | | | | UPower specifies the battery-caution-symbolic icon for all levels that gnome-settings-daemon considers notification-worthy. These notifications look too much alike, which may desensitize the user in the last actually urgent states. Decouple the icons names from those specified by UPower for our own notifications, so that design changes don't necessarily involve changes in system components. And use the additional new icons added to the Adwaita icon theme to convey a higher sense of urgency to each of the notifications spun until shutdown/suspend/hibernate. Closes: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/731
* power: Change low power notification textAllan Day2023-02-072-62/+26
| | | | | | | | | | | Improve the low power notification text, to reduce ambiguity and desensitization: * Deduplicate the headings for critical and action levels * Remove the time estimate which is often wrong * Remove ambiguous time periods where possible This is a partial fix for #686
* housekeeping: fix capitalization of systemd notificationsMichael Catanzaro2022-11-241-2/+2
|
* smartcard-manager: minor cleanupsIgnacio Casal Quinteiro2022-10-181-3/+3
|
* smartcard-manager: reduce variable scopeIgnacio Casal Quinteiro2022-10-181-1/+2
|
* xsettings: Always fallback to ibusCarlos Garnacho2022-09-301-69/+1
| | | | | | | | | | | | | | | | | Traditionally, we've used ibus strictly when necessary (i.e. there was an IM configured that required IBus to be enabled). A bit more recently, we added OSK checks so that environments with an OSK would also have IBus enabled so that GNOME Shell could track focus positions without pulling a11y. Nowadays, we simply want ibus always enabled, even if the underlying keymap wouldn't seemingly use its features. We anyways want it for the handling of emojis and dead keys. Always enable IBus for X11 clients, unless there is another IM configured in the global GSetting. Closes: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/705
* housekeeping: Add systemd OOM notification moduleBenjamin Berg2022-09-024-0/+299
| | | | | | Note that we only notify if a unit (scope/service) is actually stopped due to OOM. This will not catch certain other cases where e.g. a delegated cgroup receives an OOM event.
* color: Clean up dependenciesJonas Ådahl2022-09-011-2/+0
| | | | | We no longer need lcms2 or libgnome-desktop, as the functionality that depended on them now lives in mutter.
* color: Remove EDID parsing codeJonas Ådahl2022-09-014-586/+0
| | | | EDID parsing is done in mutter, no need to keep a copy here.
* color/state: Stop setting color transform matrixJonas Ådahl2022-09-012-616/+0
| | | | | | This is now done by mutter. This was, except for keeping track of color temperature, the last thing GsdColorState did, so it is now practically a container for the temperature only.
* color: Stop updating X11 window propertiesJonas Ådahl2022-09-011-163/+1
| | | | This is now handled by the mutter X11 backend.
* color: Stop setting brightness from profileJonas Ådahl2022-09-011-50/+0
| | | | This is now handled by mutter.
* color: Stop applying color profilesJonas Ådahl2022-09-011-256/+0
| | | | This is now handled by mutter.
* color: Stop managing color profilesJonas Ådahl2022-09-015-598/+1
| | | | This is now done by mutter too. We still apply them however.
* color: Remove colord device managementJonas Ådahl2022-09-011-295/+32
| | | | | | Adding and removing colord devices are now done in mutter. This also brings some changes in how device matching works, to continue being able to manage colors without being in control of device management itself.
* build: Use gcr4 by default, but have an option to use gcr3 tooMilan Crha2022-07-192-1/+5
| | | | | The gcr4 replaces gcr3, thus make it possible to use either of the two, while defaulting to gcr4, as it'll live for a longer time.
* plugins: Unset GDK_BACKEND envvar if a specific backend is neededMichel Dänzer2022-07-131-0/+3
| | | | | | | | | | | | | | This currently affects only the xsettings plugin, which needs GDK to use the x11 backend. It already calls gdk_set_allowed_backends ("x11") for this purpose; however, if GDK_BACKEND=wayland (or any other non-x11 backend possibly) happened to be in the environment, GDK would fail to initialize at all. This would prevent the xsettings plugin from starting up. Big thanks to Olivier Fourdan for figuring this out! Bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022283 Bug: https://bugs.debian.org/1008992
* xsettings: Simplify fetching string for an enum valueBastien Nocera2022-05-311-12/+1
|
* xsettings: Remove direct mapping from gtk-im-module to Gtk/IMModuleCarlos Garnacho2022-05-311-1/+0
| | | | | | | | | This is now handled dynamically since commit e2d268eb00, so we should not tie dconf setting and Xsetting automatically here. Doing so, we are clobbering the dynamic value on startup, making it only effective on later changes. Fixes: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/682
* a11y-settings: Enable toolkit-accessibility when using the magnifierSebastian Keller2022-05-311-10/+13
| | | | | | | | | The gnome-shell magnifier uses AT-SPI caret and focus events to follow keyboard navigation. While GTK emits those as long as it can connect to the a11y bus, other toolkits/applications such as Qt or Firefox check for the IsEnabled property which follows this GSettings key. Fixes: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/688
* plugins: Stop using GSliceFernando Monteiro2022-04-233-7/+6
|
* power: Fix mutter version check in test codeBenjamin Berg2022-03-231-8/+35
|
* tests: Update Mutter version dependencyCarlos Garnacho2022-03-191-1/+1
| | | | | This is broken comparing with stable release numbers, like 42.0. This version is also released, so it sounds better to simply depend on that.
* keyboard: "Migrate" gtk-im-context setting before giving control to userCarlos Garnacho2022-03-181-0/+35
| | | | | | | | | | | | | | | This setting used to be modified by gsd-keyboard at runtime, but it no longer does. We want to leave this setting in a pristine state before we lend control to the user in order to avoid setting leftovers make GTK and others use the unintended IM module. Since the setting is actually staying on the same schema/path, there is no nice mechanism that would help us in doing a one-time port, so rely on a file at ~/.cache to make this happen once. In the common case, it just adds one stat() more at startup. After this migration is done, the gtk-im-module setting can be considered in full control of the user.
* sharing: Don't manage gnome-remote-desktopJonas Ådahl2022-03-041-1/+0
| | | | | Settings now directly uses systemd for managing the gnome-remote-desktop service, thus we don't need to have gsd-sharing do it for us anymore.
* xsettings: Adopt code to look up GTK IM moduleCarlos Garnacho2022-02-142-147/+152
| | | | | | | | | | | | | | | Right now, gsd-keyboard and gsd-xsettings have a strange relation where the first sets the gtk-im-module dconf setting for the latter to read the setting and forward it through XSettings. Since this detection is highly X11 specific, make it happen in the Xsettings daemon itself, from the relevant setting and device presence. This makes users still able to shoot themselves in the foot by changing the setting, X11 clients able to be told to switch to ibus if it turns out necessary, and Wayland clients unaffected otherwise. Related: https://gitlab.gnome.org/GNOME/gtk/-/issues/4443
* media-keys: Remove screencast key handlingIvan Molodetskikh2022-02-123-120/+0
| | | | gnome-shell itself now handles the screencast key too.
* media-keys: Remove screenshot key handlingIvan Molodetskikh2022-02-126-350/+0
| | | | | gnome-shell itself now handles the screenshot keys. This is required to easily provide same-frame response to pressing a screenshot key.
* power: Make startup of lid tests more reliableBenjamin Berg2022-02-101-9/+10
| | | | | | | The lid-switch is inhibited at startup, and a number of tests rely on this inhibition to have been released again. Unfortunately, it seems that sometimes we were not clearing all messages properly. Either way, explicitly waiting for the uninhibit that happens at startup is sane.
* media-keys: Suppress OSD title on phones as wellGuido Günther2022-02-101-0/+2
| | | | | Those usually get port names from UCM. Add common port names from there.
* power: Improve battery warning debounce logicMarti Raudsepp2022-02-101-1/+1
| | | | | | | | | | | | Despite the debounce logic introduced in 60621b90bc3154dc905ed90780a7f19eb553ab26, GSD kept warning me of the battery level every time my Logitech K600 keyboard (via Unifying receiver) disconnects/reconnects. Added another condition: when battery level drops to `UP_DEVICE_LEVEL_NONE`, the previous entry in the hash table would not be overwritten. This avoids duplicated warnings when transitioning NONE->LOW->NONE->LOW.
* media-keys: fix gnome settings desktop fileMae Dartmann2022-02-101-1/+1
|
* plugins/datetime/weather-tz.c: Use g_object_ref() instead ↵Javier Jardón2022-02-101-1/+1
| | | | gweather_location_ref()
* Port to GWeather 4Emmanuele Bassi2022-02-101-2/+3
| | | | | | Use the new GWeather major version. The only change consists in replacing GWeatherTimezone with GTimeZone.
* meson: drop unused argument for i18n.merge_file()Marvin Schmidt2022-02-102-2/+0
| | | | Ignored in meson < 0.60.0, deprecated since 0.60.1 and fatal since 0.61.0.
* power: Skip unblank on lid open test for broken/old mutter versionsBenjamin Berg2022-02-101-0/+11
| | | | | | | Some versions of mutter were not setting the use as active when the lid was opened. Skip the test in case the current mutter version does not contain the (latest) fix. This will also disable the test for older versions that work, but that is fine.
* xsettings: Support new "high-contrast" settingFlorian Müllner2022-01-041-2/+36
| | | | | | | | | | We now have a boolean setting that determines whether the high-contrast theme should be used. Support it by automatically setting the existing `gtk-theme-name` and `gtk-icon-theme-name` properties when enabled. With that, it is no longer necessary to change the regular theme settings for high-contrast, so toggling between high-contrast and a non-default theme finally works reliably.
* color/night-light: Make sure to set target temperatureJonas Ådahl2021-12-071-6/+9
| | | | | | | | | | | When smoothing a temperature, we practically never ended up setting the target temperature, since the throttling dropped the last few changes. For example, after night light was disabled, the temperature tended to get stuck on 6494 instead of 6500. Fix this by making sure the target temperature is forced, ignoring the throttling. Also disable throttling when not smoothing, as it's likely we want the temperature that is actually asked for.
* color/manager: Fix temperature notify typeJonas Ådahl2021-12-071-1/+2
| | | | | | The org.gnome.SettingsDaemon.Color.Temperature property has the type 'u' which is a 32 bit unsigned integer. What we sent was a double (type 'd'). Make sure we send the right type in the notify signal.
* power: Do not print an error for failures from realpathBenjamin Berg2021-11-301-8/+4
| | | | | | | Doing so leaks information about whether a file/directory exists even if it is outside of the /sys/class/backlight directory. Closes: #634
* keyboard: deprecation warning fixNishal Kulkarni2021-11-251-14/+14
| | | | | | | | | `gdk_display_get_device_manager` is now deprecated, Use GdkSeat instead of GdkDeviceManager for connecting to device added and removed signals. Using `gdk_display_get_default_seat` instead of `gdk_display_get_display_manager`
* media-keys: Fix fast-forward and rewind keysBastien Nocera2021-10-271-4/+4
| | | | MPRIS's Seek method uses microseconds, not milliseconds.
* media-keys: Fix Repeat togglingBastien Nocera2021-10-272-2/+2
| | | | | | Repeat is the name of the key within gnome-settings-daemon, LoopStatus is the name of the MPRIS property. Make sure to use the correct one each time.
View Lorry Controller Status