summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* power: Remove backlight helperbenzea/brightnessBenjamin Berg2022-03-234-377/+3
| | | | Lets just assume that everyone has systemd-logind or elogind these days.
* power: Switch brightness test to use the logind interfaceBenjamin Berg2022-03-234-63/+31
|
* power: Wait for systemd SetBrightness call to completeBenjamin Berg2022-03-231-1/+25
| | | | | This isn't really needed, but allows the test-suite to run without races and needing explicit sleeps.
* power: Fix mutter version check in test codeBenjamin Berg2022-03-231-8/+35
|
* tests: Enable dconf service for new dbusmock compatibilityBenjamin Berg2022-03-231-0/+4
| | | | | | | | | | | | | python-dbusmock will also stop importing all session services that are installed on the host system by default (as is already the case for system services). With this change, the dconf service cannot be activated anymore unless we explicitly enable the service in the environment. Add the appropriate call to enable the service, guarded by a check that the method exists to be compatible with older dbusmock versions. See: https://github.com/martinpitt/python-dbusmock/pull/108
* Release 42.142.1Carlos Garnacho2022-03-202-1/+6
|
* Release 42.042.0Carlos Garnacho2022-03-191-0/+8
|
* 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.
* Update Italian translationMilo Casagrande2022-03-171-662/+967
|
* Updated Czech translationMarek Černocký2022-03-141-2/+2
|
* Update Basque translationAsier Sarasua Garmendia2022-03-091-1/+1
|
* Update Basque translationAsier Sarasua Garmendia2022-03-091-325/+291
|
* Release 42.rc42.rcCarlos Garnacho2022-03-062-1/+9
|
* 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.
* Release 42.beta42.betaCarlos Garnacho2022-02-142-1/+21
|
* 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
* Update POTFILES.inPiotr Drąg2022-02-131-1/+0
|
* media-keys: Remove screencast key handlingIvan Molodetskikh2022-02-124-136/+0
| | | | gnome-shell itself now handles the screencast key too.
* media-keys: Remove screenshot key handlingIvan Molodetskikh2022-02-127-410/+0
| | | | | gnome-shell itself now handles the screenshot keys. This is required to easily provide same-frame response to pressing a screenshot key.
* tests/output_checker: Don't close FD from threadBenjamin Berg2022-02-101-6/+3
| | | | | | Otherwise there is a race condition that can cause the FD to be closed twice. Avoid this by signalling EOF through a separate variable and always closing the FD from the main thread.
* 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
|
* .gitlab-ci.yml: Install libgweather4Javier Jardón2022-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-102-3/+4
| | | | | | 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.
* tests: Initialize unused daemon_death_expectedBenjamin Berg2022-02-101-0/+3
|
* 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.
* ci: Only run on "crun" tagged runners for nowBenjamin Berg2022-02-101-6/+10
| | | | | | The others are not erroring out correctly for close_range syscalls, causing issues when spawning. So use the "crun" runners and disable "asan" as there is no overlap.
* .gitlab-ci.yml: Try to use fedora 36Javier Jardón2022-02-101-2/+2
|
* Update Japanese translationsicklylife2022-02-101-377/+143
| | | | (cherry picked from commit d058db6a091326962562a816169e345a50034217)
* Update Japanese translationsicklylife2022-02-101-475/+995
| | | | (cherry picked from commit 6868a4a102902834f6c193b3a321053e2b82afb0)
* Update Swedish translationAnders Jonsson2022-02-081-7/+10
|
* Release 42.alpha42.alphaCarlos Garnacho2022-01-102-2/+20
|
* 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.
* Update Hebrew translationYosef Or Boczko2021-12-291-11/+8
|
* Update Hebrew translationYosef Or Boczko2021-12-291-227/+761
|
* Update Indonesian translationKukuh Syafaat2021-12-231-11/+8
|
* Update French translationClaude Paroz2021-12-111-44/+47
| | | | (cherry picked from commit 53d843683a2b255d8c554e8eacff19503c3a3401)
* 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`
* Update Occitan translationQuentin PAGÈS2021-11-211-277/+116
|
* Update Occitan translationQuentin PAGÈS2021-11-181-47/+25
|
* Updated Spanish translationDaniel Mustieles2021-11-161-3/+3
|
* Update Friulian translationFabio Tomat2021-11-071-116/+51
|
View Lorry Controller Status