| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
This mainly means free'ing the world when done and stopping to use the
now deprecated API (even though it would be acceptable in our case).
|
|
|
|
| |
Some OS (e.g. BSD) install false as /usr/bin/false.
|
| |
|
|
|
|
|
| |
The mouse schema went deprecated and renamed locally. We shouldn't reference
the old child anymore.
|
|
|
|
|
| |
These come from different schemas now, so plugin_callback() is not
the right place to look for changes anymore.
|
|
|
|
|
|
|
|
| |
This was missed porting drag-threshold/double-click to g-d-s, this
was handled "elegantly" in testing/CI (the new settings were just
ineffective) because the schema was still around in the environment
coming from the system install, but will likely trigger GSetting
asserts if it wasn't there as a fallback.
|
|
|
|
|
| |
The service was split out of the main gnome-shell process for
security reasons, and no longer runs unconditionally.
|
|
|
|
| |
(cherry picked from commit 6018dd49c6c3dc76cbc32498f498ba68af56d0d3)
|
| |
|
|
|
|
|
|
| |
gsettings-desktop-schemas
These settings are more universal than gnome-settings-daemon.
|
|
|
|
|
|
| |
gsettings-desktop-schemas
Move these settings there, as they are more universal than gnome-settings-daemon.
|
|
|
|
|
|
|
|
|
|
|
| |
When DUT is active (i.e. night light is effectively off), we should
still report the correct active state depending on whether we have
detected night-time or not.
So always run the code to update the active state, and instead only skip
the color temperature calculation that happens later.
Closes: #570
|
|
|
|
|
|
|
|
|
|
|
|
| |
When the window system supports color transform matrices, use libcolord to
compute an adaptation matrix to convert from an sRGB reference profile to the
measured profile for each display. Use gnome_rr_output_set_color_transform from
libgnome-desktop to apply that matrix to the window system.
Modify the code that sets the _ICC_PROFILE root window property to hard-code a
standard sRGB reference profile when a color transform is in use; color-aware
applications should not try to apply their own correction if the window system
is already doing it.
|
|
|
|
|
|
| |
The environment variables were not correctly cleared. Fix this and also
make sure that we don't have the GNOME_SETUP_DISPLAY environment
variable leaking in from the outside.
|
|
|
|
|
|
|
|
| |
We need the database only quite irregularly (i.e. when the location
change). Just load the database on the fly when we need it, and discard
it afterwards to free up the memory again.
See also: !168
|
|
|
|
|
|
|
|
|
| |
We need the database only quite irregularly (i.e. when the location
change). Just grab the required information from GWeather on the fly and
destroy it immediately after. Also, use the API to only grab the cities
of one country instead of filtering them later.
See also: !168
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A lot of wireless input devices, such as Logitech mice and touchpads, or
Bluetooth LE input devices, will disconnect and reconnect frequently
from the computer when unused.
This causes a problem when the battery on the device is low because
a new notification will be generated each time the device reconnects, as
if it was the first time it connected.
Saving the last warning-level for every external peripheral ensures that
we only emit one low battery notification for each warning-level, when
the threshold is crossed, rather than at every reconnect.
The last warning-level is not stored, so a new session, or a reboot will
cause devices to warn again once.
Helps: #108
|
|
|
|
|
|
| |
The new FDO templates do not need privileged runners anymore. Also,
those do not exist and the asan should be run on the asan runner
instead.
|
| |
|
| |
|
|
|
|
|
|
|
| |
It is expected for USBGuard to not be installed on many systems. We
should not warn about that DBus error, as it does not indicate an issue.
Closes: #567
|
| |
|
|
|
|
|
|
|
|
|
|
| |
We already suppress logout actions in GDM (10aa1714b05b, power: Avoid
automatic logout in GDM/greeter). However, while this prevents the
action, we may still warn.
Change it so that the corresponding timeouts will never be registered.
Leave the guard in gnome_session_logout but add a warning as we should
never be hitting that code path.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
In GDM sessions (greeter, initial-setup), it does not make sense to
automatically logout. This can happen if the system wide default is
changed to default to the "logout" action.
Note that we already use the RUNNING_UNDER_GDM environment variable in
the keyboard plugin currently. So doing this is likely sane, even if we
probably want a more elegant strategy to detect whether we are in a
"login" session.
|
|
|
|
|
|
| |
Recent changes to gio omit the atime instead of setting it to an out of range value.
Fixes #556, but note this doesn't fix the fact that gio omitted atime on a system where atime should have been available.
|
| |
|
| |
|
|
|
|
|
| |
Don't throw warnings when we can't find a default source or sink and the
PulseAudio daemon is restarting.
|
|
|
|
|
|
|
| |
This update is necessary to add support for recent UCM related changes
in ALSA and PulseAudio.
See https://gitlab.gnome.org/GNOME/libgnome-volume-control/-/merge_requests/10
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|