| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
| |
We really just want a whitelist of applications to be started through
autostart. Use the new AutostartWhitelist key file to list application
IDs that may be autostarted (while all others are not considered for
autostart).
The main disadvantage is that all applications that potentially should
be autostarted need to be listed here (as part of distribution patches).
In the common case, spice-vdagent should be added to the list.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
configure: Use pkg-config to look for keyutils
See merge request GNOME/gdm!91
|
| |/
|
|
|
|
|
|
|
|
|
| |
Support for pkg-config was added to keyutils somewhat recently in
November 2018 [1], whereas the keyutils dependency was originally added
in August 2016 in commit 31ed6f2b3f1ab45ae07aad41c13a51ba91fd159d.
[1] Keyutils commit d4d758a04616b770
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/keyutils.git/commit/?id=d4d758a04616b770
https://gitlab.gnome.org/GNOME/gdm/merge_requests/91
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
libgdm: Remove duplicate sessions when on Xorg
See merge request GNOME/gdm!84
|
| |/
|
|
|
| |
When gdm works on Xorg it's possible to have duplicate sessions, we need
to remove them.
|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
gdm-session-worker: Assume login_vt is on GDM_INITIAL_VT
Closes #515
See merge request GNOME/gdm!86
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When a session ends, its "session worker" is closed. Since
3e8220921bb608afd06ed677104fd2244b901a28 (3.33.4), we uninitialise PAM
when this happens. As part of this procedure, we jump back to the login
screen, if the screen being killed is not itself the login screen.
This has broken fast user switching. It goes like this - this
explanation is a bit complicated, bear with us:
We want to jump back to the login screen when a normal user session
ends, so that people can log in again. We do not want to do this when a
login screen itself ends. When session workers start up, they query for
the *currently active VT* and save this in `login_vt`. Then later on, we
check if our session ID is the same as `login_vt`, and jump to
`login_vt` if they are different - this means that it was a user session
not a login session. Querying the currently active VT is fine for the
first greeter, but when initiating a user switch it's wrong as this
gives the user VT.
GDM greeters are killed once they have spawned a session. They are
associated with a logind session, and therefore a PAM session. There are
some actions performed when unregistering PAM sessions, including the
previously mentioned VT jump. Before
3e8220921bb608afd06ed677104fd2244b901a28 we only uninitialised PAM when
the session itself exited so the bug was masked, but now (since this
commit), if the login screen's *worker* exits first - as happens in the
normal case when GDM kills it - we also do this uninitialisation. Since
we falsely recorded the login screen as the first user's VT, this means
that checking `login_vt != session_vt` returns `TRUE` and we jump back
to the previous user's session immediately after logging into the new
session: fast user switching is broken.
Since the work on shutting down the GDM session has been finished, we
can assume that the login_vt is always on GDM_INITIAL_VT (see
example c71bc5d6c3bc2ec448b5c72ce9a811d9c0c7905e
"local-display-factory: Remove initial VT is in use check" and
39fb4ff64e6a0653e70a3bfab31da47b49227d59 "manager: don't run autologin
display on tty1"). So simply replace all usages of login_vt with
GDM_INITIAL_VT to solve the above problem.
Note that in the case where ENABLE_USER_DISPLAY_SERVER is not enabled,
the login_vt is always the same as the session_vt. We can simply remove
the VT switching magic there and everything should be working as
expected.
This is a simpler version of the patch by Iain Lane <iainl@gnome.org>,
taking into account that we can make the assumption about the login_vt.
Closes #515
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
local-display-factory: reap login session on vt switch to registered session
Closes #509
See merge request GNOME/gdm!83
|
| |/
|
|
|
|
|
|
|
|
|
|
|
| |
Since commit 1c061b84ffc3e874da825982d18d970556ff74bb we reap the login
screen after the user logs into a session, instead of after a timeout.
Unfortunately, that means we no longer reap the login screen when
unlocking a session.
This commit adds back the timeout in the case seat0 is switched to a
registered login session.
Closes https://gitlab.gnome.org/GNOME/gdm/issues/509
|
| |\
| |
| |
| |
| | |
display: fix "forceing" typo in debug message
See merge request GNOME/gdm!79
|
| |/ |
|
| |\
| |
| |
| |
| | |
Revert "Merge branch 'environment-fix' into 'master'"
See merge request GNOME/gdm!82
|
| |/
|
| |
This reverts merge request !71
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
Revert "session-worker: don't take control of a vt just because we're changing to it"
Closes #508
See merge request GNOME/gdm!80
|
