| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
|
| |
Splitting strings won't work right in many languages, and makes
the life of translators harder.
See https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/merge_requests/174#note_890827, #548
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
| |
We are now generate all of these from one template, rather than having a
per-plugin template.
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
This prevents logout to hang if one of the g-s-d processes refuses to
quit. That should never happen, but it does not hurt to configure
systemd to kill the process already after 5 seconds rather than waiting
up to 1 minute 30 seconds.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Using the facility added in the previous commit, we can add systemd user
service files for all plugins and know when they have started up.
This is roughly based on the work previously done by Iain Lane
<iain@orangesquash.org.uk> and Bastien Nocera hadess@hadess.net>.
For each g-s-d process we have a service and a target file. This
separation only exists to contain dependency failures which would cause
an OnFailure action to trigger and is needed so that we can use
OnFailure for the gnome-session fail-whale
(gnome-session-failed.target).
In general, the approach taken is that we start g-s-d processes after
gnome-session-initialized.target and before gnome-session.target.
We want to be able to selectively start the services only when one or
more dependencies are there, or even mask out services under some
conditions. The approach taken is the following:
* To mask a service, use a Conflicts entry. This is e.g. used to not
start certain services in GDM using
Conflicts=gnome-session@gnome-login.target
* To depend on multiple targets to be up and running to start, we set
each of these targets in Requisite/After/PartOf/WantedBy. We always
do this for gnome-session-initialized.target but this method is
extensible to any number of further targets (e.g. bluetooth.target)
|
|
|
Heavily based on code from nm-applet.
Follow-Ups:
- Allow to store SIM in keyring
- Handle PUKs? (or do that in g-c-c)
|
