commit 96b9b48792ec8b0cbb41f37e9025e1ae232cebcb
Author: Alessandro Astone <alessandro.astone@canonical.com>
Date: Tue Jan 13 14:19:10 2026 +0100
d/control: Add new Build-Depends for the test suite
commit 74393db1360b1f9001b1cbe0417ed60e2859fd08
Author: Alessandro Astone <alessandro.astone@canonical.com>
Date: Tue Jan 13 13:39:29 2026 +0100
d/control: Drop unused Build-Depends xserver-xorg-input-wacom
commit a147b641679aa06045a3c7bdc8ae3c2e0c5269f7
Author: Alessandro Astone <alessandro.astone@canonical.com>
Date: Thu Jan 15 17:57:12 2026 +0100
New upstream release
commit 73b1c50b30d9bf4a46b36ace133a23fb4668498e
Merge: 596d67ce 8040ff25
Author: Alessandro Astone <alessandro.astone@canonical.com>
Date: Thu Jan 15 17:56:58 2026 +0100
Merge tag 'upstream/50_alpha' into debian/latest
Upstream version 50~alpha
commit 8040ff252209f96e84865731b8ea673ebdfab505
Merge: 7a4a3918 b2390215
Author: Alessandro Astone <alessandro.astone@canonical.com>
Date: Tue Jan 13 13:57:40 2026 +0100
New upstream version 50~alpha
commit b23902159336f36ce5d3854fde05bf85f3264943
Author: Carlos Garnacho <carlosg@gnome.org>
Date: Mon Jan 5 12:32:43 2026 +0100
Release 50.alpha
commit 5af04e7742701849e4f1ac04b340a3acf3a3345f
Author: Carlos Garnacho <carlosg@gnome.org>
Date: Mon Nov 24 17:19:45 2025 +0100
power: Trigger re-normalization on out-of-band brightness changes
When brightness is auto-managed by ALS, we still have two situations
where the brightness changes do not come from it:
- User changes to the display brightness, either through keybindings,
or the sliders in the shell menu being changed.
- Dimming requests on user inactivity.
The response to both should be similar, the abrupt brightness change
can alter ALS readings, so the brightness resulting of the change must
be used as a new baseline for normalization.
Tracking of user-triggered changes is done through a new BrightnessChanged
signal in the org.gnome.Shell.Brightness D-Bus interface. This will do
nothing on older versions of GNOME Shell without the signal, so effectively
brightness changes would not trigger a re-normalization there, as before.
If the signal exists and is emitted, then it will be used.
commit 44e1cc564b02349adab38e691770f13c0e09951b
Author: Roman Yepishev <ryepishev@google.com>
Date: Sat Dec 27 16:27:15 2025 -0500
plugins/power: do not unidle for inactive session
NVIDIA drivers change the virtual terminal before suspend and restore it
upon resume.
Upon resume, there is a period of time when systemd reports that our
session is not active (we are on a different virtual terminal). On
resume, `idle_set_mode` would ignore that state change (keeping it as
"sleep"), and if `WakeUpScreen` signal from screensaver arrives at that
time, we will store "sleep" as `previous_idle_mode`, and set up a
callback to restore to that state. That causes the machine to suspend
15 seconds after resume.
This change refactors the unidle calls, refactoring common checks into
a separate function.
Up until https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3481,
mutter was resetting the idle timer on AC events and gsd-power did not
have to do anything. Once mutter starts resetting the idle timer again,
we can remove the code handling AC events.
Closes #903
commit c806b911104a32e180653545146302a25283fcda
Author: Roman Yepishev <ryepishev@google.com>
Date: Fri Jan 2 14:08:27 2026 -0500
plugins/power: Add unidle tests
This moves the existing test into a new test suite and adds coverage
for sequential AC events and WakeUpScreen handler.
Related to https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/903
commit 418fef7b74fb35a1c17c7e3f4ee2a94e2fc0d40e
Author: Roman Yepishev <ryepishev@google.com>
Date: Sat Jan 3 15:02:17 2026 -0500
plugins/power: logind does not emit OnExternalPower
Per https://www.freedesktop.org/software/systemd/man/latest/org.freedesktop.login1.html,
logind does not notify of OnExternalPower changes:
@org.freedesktop.DBus.Property.EmitsChangedSignal("false")
readonly b OnExternalPower = ...;
So we can't use Set(). We would still like to simulate the behavior,
so update the property silently via a mock interface call.
commit 02e2827763b879c16167f3fa9147fd4fd29891e5
Author: Roman Yepishev <ryepishev@google.com>
Date: Fri Jan 2 16:35:09 2026 -0500
plugins/power: don't set NULL icon_name hint
`show_sleep_warning` does not set the icon_name so gsd-power emits a
GLib-Critical message when the notification is shown:
g_variant_new_string: assertion 'string != NULL' failed.
commit 71e9574d0327b6e8721601eeac00ca5b8cc3fa44
Author: Roman Yepishev <ryepishev@google.com>
Date: Tue Dec 16 19:32:16 2025 -0500
tests: write env vars in a single statement
On a busy system, there's a delay between two echo statements, that
can make our test read only the first line. This change writes both
variables together, thus removing the delay.
commit 97f67a2c7135572d7afce03e65919ac47b639c2c
Author: Roman Yepishev <ryepishev@google.com>
Date: Mon Dec 15 19:12:44 2025 -0500
plugins/power: add sleep before blanking checks
Previously we expected all handlers to complete running before we
check for our debug messages indicating blanking/unblanking. This
introduces a small delay to allow external processes to react to our
DBus messages for two tests that were failing on busy systems.
Also remove an obsolete FIXME message.
commit 7eb7889679edfb4961ad046712bf97925d98551b
Author: Bilal Elmoussaoui <belmouss@redhat.com>
Date: Tue May 27 10:12:45 2025 +0200
power: Use logind to get LidIsClosed and OnBattery states
As the LidIsClosed property got deprecated in UPower.
Also replaced the OnBattery state usage to the one from UPower as that
is what Mutter is also using nowadays.
Co-authored-by: Bastien Nocera
Co-authored-by: Benjamin Berg
Closes: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/859
commit 7043fe8659e1f1e03c169786e9d401d4dfafb409
Author: Roman Yepishev <ryepishev@google.com>
Date: Mon Dec 22 21:56:22 2025 -0500
plugins/power: use logind LidClosed in the lid tests
mutter uses logind LidClosed property for idle detection, so our tests
should update that. When gsd-power is updated to use logind, the UPower
calls should be removed.
Also remove the mutter version check. Mutter 42.0 was released in 2021.
Related to: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/859
set_lid_state() is based on
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/merge_requests/238
by Bastien Nocera.
commit 854010e88365cdfb87b9247cf64ac07f4203271d
Author: Roman Yepishev <ryepishev@google.com>
Date: Fri Dec 5 22:23:11 2025 -0500
plugins/power: correct BatteryLevels forced logout tests
The debug messages have changed, so we need to scan for modified
strings.
commit 2300eac7dcdae47f531ab460b3119c76dbb06f7b
Author: Roman Yepishev <ryepishev@google.com>
Date: Thu Dec 4 20:29:15 2025 -0500
plugins/power: make test.py run under new image
* Swap gnome-session with gnome-session-service as that's where
org.gnome.SessionManager lives now. Drop systemd dependency check,
as this is now a hard depenedency.
* Use gnome-session-ctl to notify SessionManager that it has completed
initialization. In the real system, gnome-session-service is notified
by systemd (through gnome-session-ctl) that the session is now fully
running, so we are now doing the same.
* Use Kiosk mode in the session, otherwise gnome-session-service
autostarts applications.
commit c20ed4b5cfc05033d8b996c4c6b079a257c91ece
Author: Roman Yepishev <ryepishev@google.com>
Date: Sat Dec 6 21:07:29 2025 -0500
ci: update image to Fedora 43
This change:
* Switches to mutter from Fedora repos (reverts
9fb2a49020d0f6cee6f867c59b2df73b704bfe5b which pinned glib and
pipewire versions and built mutter from main.
* Switches to the main branch of gsettings-desktop-schemas.
* Trims build dependencies.
commit 690f9d1e93b7b6b32f4dc7de7298bb8994d764f4
Author: Qiu Wenbo <qiuwenbo@gnome.org>
Date: Thu Nov 20 17:16:12 2025 +0800
build: Remove X11 session option
commit 01159c74a6109ceec8461ef1ba3dcbd6c5b87f03
Author: Joan Torres Lopez <joantolo@redhat.com>
Date: Tue Dec 16 14:10:58 2025 +0100
sharing: Drop support for .desktop services
sharing daemon starts assigned services either in user sessions or in greeter
sessions.
Starting services was different depending on user type:
1. user session: by systemd
2. greeter session: by .desktop file
Since GNOME 49, both sessions are handled by systemd, so we can drop the
.desktop files support and always start services by systemd.
commit 65b257b6cb337db471196c7711d25ad231a79966
Author: Joan Torres Lopez <joantolo@redhat.com>
Date: Wed Oct 22 12:31:03 2025 +0200
sharing: Start assigned services without depending on network
The assigned services start depending if specific system services are running.
They were implicitly depending if network is available, but they can operate
even without network.
This fixes an issue where gnome-remote-desktop-handover would not start
when no network is detected because the system network is managed by
other service than NetworkManager. So there's room for improvement in
gsd sharing manager to detect network availability in a more generic way
instead of relying solely on NetworkManager.
Closes: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/822
commit f37ed3295850d8a8bd6ea6108b7c21e0ef88a29a
Author: Joan Torres Lopez <joantolo@redhat.com>
Date: Wed Oct 22 12:11:05 2025 +0200
sharing: Reduce unnecessary HAVE_SYSTEMD_LIB guards
commit 4cc8891b43ffacd378155b6d838dcd279e85144f
Author: Christian Hergert <chergert@redhat.com>
Date: Fri Nov 21 13:40:53 2025 -0800
plugins/housekeeping: check user-data-dir fs::id once
We don't, as a platform, really support changing out your entire file
system out from underneath a running session. So only check the
file-system identifier for the user trash directory once at startup.
commit cfe8049a6de68a988c5fd6cefa837d11807f4846
Author: Christian Hergert <chergert@redhat.com>
Date: Fri Nov 21 12:53:56 2025 -0800
plugins/housekeeping: track changes to ignored mounts in glib
This mirrors the changes in GNOME/glib!4916 which adds the following
system mounts:
* binfmt_misc
* bpf
* efivarfs
* tracefs
commit a66871d63abc68fc4f9a9880a33d4cc35b665877
Author: Christian Hergert <chergert@redhat.com>
Date: Fri Nov 21 12:49:25 2025 -0800
plugins/housekeeping: only make has_trash() call once
We don't need to call this twice, it is only called in these two places
so just pass in the value from the previous call.
commit ead2e435081505564a0d7e5e2d903b90682692d7
Author: Roman Yepishev <ryepishev@google.com>
Date: Sat Dec 13 14:08:19 2025 -0500
ci: fix Run Tests command syntax error
Sanitizer tests could not start because mkdir received meson arguments.
commit bd777338af72c33e1e532fa86fcc91ea20be251a
Author: Roman Yepishev <ryepishev@google.com>
Date: Fri Dec 12 22:10:59 2025 -0500
color: correct leaks in the test flagged by asan
Not all of the instances of datetime_override were finalized.
commit 36e544534dfb4a8927cb0056f0fc5daa69dbe1f9
Author: Sebastian Wick <sebastian.wick@redhat.com>
Date: Wed Oct 15 20:44:11 2025 +0200
power: Throttle target brightness updates to shell
This limits the auto brightness updates to shell to 10 times per second.
In the future, shell should be able to smoothly animate between targets
which should allow us to decrease the value.
commit 18e8f6832d456798eb35dbdcfda7bed22e1badb1
Author: Sebastian Wick <sebastian.wick@redhat.com>
Date: Wed Oct 15 20:43:45 2025 +0200
power: Rework ambient light sensor normalization
This reworks the normalization and fixes two things in particular:
The percentage `pc` is an int so if we want values different
from `0` and `1` we need to use floating point division.
When gsd-power controlled the backlight it would init that value from
the backlight on startup but we don't have that available anymore so
can only pick an arbitrary value.
Co-authored-by: Guido Günther <agx@sigxcpu.org>
Fixes: 08ae6461 ("power: Switch from direct mutter backlight handling to Shell.Brightness")
commit 4f24cade467a876eb39c9e076779c5bf3af150e8
Author: Sebastian Wick <sebastian.wick@redhat.com>
Date: Wed Oct 15 20:41:22 2025 +0200
power: Rename ambient_last_time to ambient_update_last_time
We will track another last_time later, so rename it in advance.
commit 6492a7e4ee4da3c38bdf91809a1022bd5f04b274
Author: Sebastian Wick <sebastian.wick@redhat.com>
Date: Wed Oct 15 20:37:03 2025 +0200
power: Use autoptrs in iio_proxy_changed
commit eb6ee4f98031fbf438506e1abe374a3748d90869
Author: Sebastian Wick <sebastian.wick@redhat.com>
Date: Wed Oct 15 20:35:17 2025 +0200
power: Take double in set_auto_target because we send a double
commit f34138e8d26f9ea128b2616333b20abfbcd705ce
Author: Sebastian Wick <sebastian.wick@redhat.com>
Date: Wed Oct 15 19:40:19 2025 +0200
power: Disable auto brightness when we release the light sensor
commit b39840dee58c28bb4558d2adaf2b84a05bbde3d2
Author: Sebastian Keller <skeller@gnome.org>
Date: Sat Nov 22 12:36:56 2025 +0100
housekeeping: Don't mark donation reminder notification as transient
When the notification was still marked as critical prior to 54b5d05e,
setting the transient hint would ensure that it was not showing up in
the calendar menu, which made sense because it was shown on screen until
manually closed or interacted with. However now that it is not critical
anymore, this means the notification disappears after being hovered and
unhovered, without any other user interaction.
Fixes: 54b5d05e ("housekeeping: Downgrade donation reminder urgency to "normal"")
commit dd70b230c74e01c2109e6cc8e73449215096e0a7
Author: Efstathios Iosifidis <eiosifidis@gnome.org>
Date: Wed Oct 29 20:45:03 2025 +0000
Update Greek translation
(cherry picked from commit 72c71561cdb5a769adde60168a036b1eb86795f4)
commit ec6e3b3916a34cfbae797ac99da68a6f1dddbb0e
Author: Aefgh Threenine <aefgh39622@gmail.com>
Date: Sat Oct 18 09:34:37 2025 +0000
Update Thai translation
commit eed183a9bf158e2da00d48ecd7b11abe083f8d47
Author: Fabio Tomat <f.t.public@gmail.com>
Date: Tue Oct 14 15:42:55 2025 +0000
Update Friulian translation
commit 54b5d05e89873158b20fe83a1f7f7bd44bc10e72
Author: Felipe Borges <felipeborges@gnome.org>
Date: Tue Oct 14 10:23:03 2025 +0200
housekeeping: Downgrade donation reminder urgency to "normal"
Critical notifications can bypass the do-not-disturbe settings and
interrupt fullscreen video/presentations.
We don't want our donation campaigns to disturb users in focus moments.
Reported in https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/896#note_2575412
Automatic checks made by the Debian l10n team found some issues with the translations contained in this package. You should check the l10n status report for more information.
Issues can be things such as missing translations, problematic translated strings, outdated PO files, unknown languages, etc.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/g/gnome-settings-daemon.png){kind=link}