| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
| |
This uses cc-wwan-device.c copied from gnome-control-center without
any modification.
The following features/fixes are also implemented:
* Handle multiple devices
* Handle PUK unlocking
* Close prompt if the device got removed
* Fix showing the wrong unlock count
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The symlinks need to be installed into DESTDIR, use a shell to do this
correctly. Also, doing this on debug builds is not very helpful,
instead, do it by testing whether we are installing into the same prefix
that systemd is coming from.
This assumes that we will run using the same systemd instance as we are
picking up the pkgconfig file from, but that seems like a reasonable
assumption (i.e. it is unlikely anyone has systemd in their prefix and
doesn't bother to set things up correctly).
|
| |
|
|
| |
This shouldn't be enabled on distro builds which should use plain buildtype
|
| |
|
|
|
| |
Try to conform to the systemd convention as defined in
https://systemd.io/DESKTOP_ENVIRONMENTS
|
| |
|
|
|
|
|
| |
We need to both reliably shutdown and notify gnome-shell that we are
ready. The gnome-session-x11-services.target does the first (we order
ourselves After= to ensure this works) and the -ready.target is our flag
to tell gnome-shell it may release the X11 socket for clients.
|
| |
|
|
|
|
| |
This means we cannot accidentally start the old targets in case they
exist on the host system. It is solely useful when using jhbuild to run
a test session and is disabled on release builds for that reason.
|
| |
|
|
|
| |
This means the .desktop and the systemd unit files are named
consistently.
|
| | |
|
| |
|
|
|
| |
We are now generate all of these from one template, rather than having a
per-plugin template.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rather than having per-plugin units, generate them from the meson build
file using a common template.
The unit layout is changed somewhat. The .target file now is solely a
flag on whether the service is requested for the session type. The
variosu requirements are all moved into the .service file.
Instead of using an OnFailure and trying to contain the dependency
errors in a separate unit, we now use ExecStopPost. It seems that the
current approach has never worked anyway.
The Conflict entries on certain session types are gone now. This is
instead handled outside of gnome-settings-daemon.
|
| |
|
|
|
| |
Note that it is still complaining, but just for an optional argument
that we only ever set to the default value.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The idea is to generate a gsd-X-gate.target intermediate unit which
has a requisite on all units listed in plugin_gate_units.
i.e. for most services we are going to have:
* gsd-X.target: marker on whether services should run in the session
* gsd-X.service: actual service that is started
This changes for units that should only run under certain conditions
(e.g. X11 or smartcard). In that case we add
+ gsd-X-gate.target
which has a proper requisite on all required units and ensures that the
servie will only start if all dependencies are met. This gate unit is
primarily needed so that we can still have an OnFailure target in the
.service file without issues.
|
| |
|
|
|
| |
Some indentation was wrong, and 4 space indentation is overall more
readable.
|
| |
|
|
|
|
| |
It seems sensible to use a more human readable description for the
.desktop file rather than just the plugin name. Hopefully this is more
useful to anyone expecting the file.
|
| |
|
|
|
| |
These can be consumed by the build system to generate nicer
.desktop/.service/.target files.
|
| |
|
|
|
|
|
|
|
|
|
| |
Currently we have no plugin that uses special flags or similar to start
only under certain conditions. So just generate all of them from two
template files rather than shipping seperate templates for each plugin.
The idea here is to handle any possible future difference also during
generation. This might e.g. be that we again start certain services only
if a GSettings key is set, which would likely need to be mirrored e.g.
in the systemd path.
|
| |
|
|
|
|
|
|
|
|
| |
There is no need to have two places for desktop file generation for
services that can be disabled. Instead, integrate the logic into the
main plugin loop and simply use a different template file as the input.
To implement this, create a list of disabled modules that can be tested
to skip the generation of the systemd units and inclusion of the plugin
directory.
|
| |
|
|
|
| |
These files were never actually used. They purely existed as an example,
but even that use case is questionable.
|
| |
|
|
|
|
| |
The binary was only needed for the stub gsd daemons that may not be
installed. The generated autostart files are not referencing gsd-dummy
anymore. As such, we can remove the binary completely.
|
| |
|
|
|
|
|
|
|
|
| |
We install stub desktop files so that session can pull these in as
required components. However, for gnome-session to be happy, we do not
actually need to start a process. It is sufficient to install the
.desktop file and then disable the service using Hidden=true.
This means we can replace the Exec line with e.g. /bin/false, removing
the need for the gsd-dummy binary.
|
| |
|
|
|
|
| |
It is not really worth it to use a loop just to set the log domain using
the cflags. Explicitly name the common subdirectory rather than
including it in the plugin loop.
|
| |
|
|
|
|
| |
With GNOME 3.36 we are going to move the definition about the systemd
services that should be running to be per-session type. This means we
need to stop installing those wants entries in g-s-d.
|
| |
|
|
|
|
|
|
| |
If we require version 243 we can rely on special targets like
smartcard.target working. Also, from 242 onwards the sytemduserunitdir
path resolving using systemd.pc works fine.
Closes: #444
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The sleep warning notification was never dismissed, even when the user
became active.
A callback to clear the notification was being installed only when
transitioning away from "normal" (for example, just before going to
sleep).
This commit also installs said callback right after showing the sleep
warning notification. Now, if the user becomes active before sleep takes
effect, the notification will be dismissed automatically.
|
| | |
|
| |
|
|
|
|
|
|
| |
The readings from the ambient light sensor were being filtered using an
exponential moving average (equivalently, a first-order low pass
filter), but the average did not account for the time since the previous
reading. Now the power manager records the time of the last reading,
making the brightness adjustments more even.
|
| |
|
|
|
|
|
|
|
|
| |
A mode change to normal causes iio_proxy_claim_light() to be called with
active set to TRUE. This connects iio_proxy_changed_cb() even if the
previous mode was dim and the callback was already connected. This
caused the callback to be triggered multiple times on each change of the
ambient light sensor. With this patch, calls to iio_proxy_claim_light()
always remove the callback first, and if active is TRUE they add it
back.
|
| |
|
|
|
| |
Hopefully this can catch issues again where we accidentally start to
depend on a newer GLib version than we intended to.
|
| |
|
|
|
| |
It is only available with GLib 2.64 and newer. That is quite recent, so
simply avoid it.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The gsd-xsettings-manager.c code uses gnome_settings_is_wayland() which
is declared in gnome-settings-bus.h, add this to the includes.
This fixes the following build-error for me:
../plugins/xsettings/gsd-xsettings-manager.c: In function ‘gsd_xsettings_manager_start’:
../plugins/xsettings/gsd-xsettings-manager.c:1396:13: error: implicit declaration of function ‘gnome_settings_is_wayland’ [-Werror=implicit-function-declaratio]
1396 | if (gnome_settings_is_wayland ())
| ^~~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
|
| |
|
|
|
|
| |
Instead of holding on to an MPRIS client for its entire lifetime, switch
to another client when it starts playing or when it first appears on the
bus, but only if the current client is not itself playing.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
