| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
gdm-pin was an experimental feature that was going to get added to
gnome-shell many years ago. It never happened and these days it
would probably be implemented a little different anyway.
(It would probably use a gdm pam extension)
There's no point keeping this service file around that we aren't
using, so this commit drops it.
Closes: https://gitlab.gnome.org/GNOME/gdm/-/issues/731
|
| |
|
|
|
| |
These files haven't been used since multistack became
a hard requirement.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
If the user has an encrypted disk then systemd will cache the password
they type into the keyring. It makes sense to try to use this password
for automatic login purposes first, since on single user machines,
the sole user password is likely to match the disk password.
Of course if it doesn't work we'll fall back to the old way of doing
automatic login without a password (and then the user will have to
manualy enter if they need to for gnome-keyring or whatever)
https://bugzilla.gnome.org/show_bug.cgi?id=769950
|
| |
|
|
| |
This prevents it from breakings setups building using --without-systemd
|
| |
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=706975
|
| |
|
|
|
|
|
| |
Without this fix, GDM refuses to start up saying that pam_systemd.so
isn't initialised.
https://bugzilla.gnome.org/show_bug.cgi?id=696577
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Originally, the idea was to have pam-pin as an optional module in gdm-password,
but since the PIN can easily get misconfigured, what we want here is
to give the user a choice at the login screen, so we want two different
conversations at the same time.
The pin module is marked requisite, so if it fails we stop before touching
the other modules and immediately report to the greeter (which then goes
on with gdm-password)
https://bugzilla.gnome.org/show_bug.cgi?id=693968
|
| |
|
|
|
|
|
|
|
|
| |
From https://bugzilla.redhat.com/show_bug.cgi?id=882385:
"The loginuid is for actual logins by people. Its not intended for
system use. All daemons should have loginuid set to -1, meaning that its
a system process and not related to activity by a person."
https://bugzilla.gnome.org/show_bug.cgi?id=693152
|
|
|
I misapplied the previous patch and broke the build for everyone
but me.
This commit fixes that.
https://bugzilla.gnome.org/show_bug.cgi?id=683283
|
