| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
data: Remove deprecated StandardOutput=syslog
Closes #623
See merge request GNOME/gdm!108
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is now equivalent to StandardOutput=journal, and recent versions
of systemd log a warning for it. Instead of updating it to journal,
remove it: the default if not specified is to respect the
DefaultStandardOutput setting from /etc/systemd/system.conf, which
in turn defaults to journal. Removing the explicit setting here means
gdm is included if a sysadmin edits system.conf to change the logging
destination for (almost) all system services at the same time, which
seems desirable.
Similarly, StandardError defaults to DefaultStandardError, which
in turn defaults to inherit, so we don't need to override it here.
Resolves: https://gitlab.gnome.org/GNOME/gdm/-/issues/623
Signed-off-by: Simon McVittie <smcv@debian.org>
|
| |
|
|\
| |
| |
| |
| | |
Meson fixes
See merge request GNOME/gdm!107
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
GDM has a quite complex configuration and it might be hard to spot some
values from the log, so having a summary makes sense.
Meson introduced it starting from 0.53, but we can enable it without bumping
the dependency by using a dynamic version check.
|
| |
| |
| |
| |
| |
| |
| |
| | |
This was already the case in autotools, as it used to be a feature that was
set to auto and disabled only in the case there was no libsystemd.
Now, being systemd a required gdm component, there's no point to use it as
a feature, but still give the packagers the ability to toggle it.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Systemd journal library is provided by libsystemd, given that such API has
more than 8 years, is probably not needed to convert this into a feature and
check for a required systemd version in case it's enabled.
So, just set ENABLE_SYSTEMD_JOURNAL just reading the option.
|
| |
| |
| |
| |
| |
| | |
With meson 0.53 we can check whether a binary is in a specified path, as it
was possible with `AC_PATH_PROG`, so use it as we did before of meson switch
even if I'm not sure that this tool is shipped by most distros these days
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Don't leave to humans what machines can do, the gnome-login.session list
is filled with an hard-to-maintain single-line semicolon separated list of
components, that then are repeated in the gnome systemd session.conf.
And these are meant to be kept in sync.
Meson can help us in this, so let's just keep a single list in meson and
use it to generate the various formats we need.
|
| | |
|
| |
| |
| |
| |
| |
| | |
When udev is installed we compute the udevdir from pkg-config, however that
is only the parent folder of the rules.d, so in any case consider it a
prefix.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
No matter what parameter was passed to gdm, the custom.conf was always
installed in $gdmcomnfdir/custom.conf, even if the config.h was using the
configured path.
Ensure that we use the passed argument, setting its name as configure_file
output and its path as the install_dir.
Unfortunately we've to be hackish here, using coreutils tools until we
require meson 0.53 (and can use its FS module).
|
|/
|
|
|
| |
Keyutils includes a .pc file as mentioned in commit 141f8bc244, however its
name was wrongly changed from 'libkeyutils' during the meson port
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
GNOME 3.38 systemd session update
See merge request GNOME/gdm!88
|
|/
|
|
|
| |
GDM needs to ship the systemd definition for the custom GNOME session it
starts.
|
|\
| |
| |
| |
| | |
Replace deprecated macros from use
See merge request GNOME/gdm!105
|
|/
|
|
|
| |
Deprecated (atleast) from version 0.10.0.
Bug: https://bugs.gentoo.org/733708
|
|\
| |
| |
| |
| |
| |
| | |
local-display-factory: again don't require wayland support to kill X
Closes #614
See merge request GNOME/gdm!104
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
commit ac083ec2d3d663a48c4aa6693978669243880dd0 attempted fix killing
X in the background even when wayland support is disabled.
Unfortunately, it missed yet more places in the code that does
ifdef ENABLE_WAYLAND_SUPPORT
endif
This commit fixes that.
Closes: https://gitlab.gnome.org/GNOME/gdm/-/issues/614
|
|\
| |
| |
| |
| |
| |
| | |
local-display-factory: don't require wayland support to kill X
Closes #614
See merge request GNOME/gdm!103
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
commit d35805116113acbf1e112962c54785c604b13181 changed GDM to
kill X on login just like it does for wayland sessions.
Unfortunately, that commit neglected to pull the code out of the
ifdef ENABLE_WAYLAND_SUPPORT
endif
guards, so users who build without wayland support entirely, don't
get the feature.
This commit fixes that.
Closes: https://gitlab.gnome.org/GNOME/gdm/-/issues/614
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Update Arch Linux PAM files
See merge request GNOME/gdm!102
|
| |
| |
| |
| | |
Copied from pam-exherbo.
|
|/
|
|
|
|
|
|
| |
systemd-sysusers now creates expired accounts, which broke the greeter
on new installations.
Doesn't actually fully fix the problem as the user@.service still fails
to launch.
|
|\
| |
| |
| |
| | |
Wip/kill x on login too plz
See merge request GNOME/gdm!51
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The login screen for both Xorg and wayland sessions is now silently
killed in the background post login.
We still kill initial-setup for Xorg sessions up front, though.
This commit fixes that.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
These days we kill the wayland login screen during login to
conserve system resources.
We've been reluctant to do the same for X based login screens,
because X didn't handle being killed in the background so well.
This is no longer a problem, since this commit:
https://gitlab.freedesktop.org/xorg/xserver/-/commit/ff91c696ff8f5f56da40e107cb5c321539758a81
So let's go ahead and kill it now.
|
|/
|
|
|
|
| |
gdm already handles the VT switching on X's behalf,
so it's redundant, and X does it at inopportune times,
so instruct it to not get involved.
|
|
|
|
| |
(cherry picked from commit 1943fed48a9821adb5516ad8f47a1058bf74412e)
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
local-display-factory: Always force login screen to VT 1
Closes #602
See merge request GNOME/gdm!100
|
|/
|
|
|
|
|
|
|
|
|
|
| |
These days we always want the login screen on VT 1, even
when it's created by user switching.
Unfortunately, since commit f843233ad the login screen
won't naturally pick VT 1 when user switching.
This commit forces it to make the right choice.
Closes https://gitlab.gnome.org/GNOME/gdm/-/issues/602
|
|\
| |
| |
| |
| | |
data: disable wayland if modesetting is disabled
See merge request GNOME/gdm!99
|
|/
|
|
|
|
|
|
| |
wayland requires working modesetting, so don't even
bother trying it if modesetting is disabled.
This is more efficient and side-steps a bug in the fallback
logic if start up is unreasonably slow.
|
|
|
|
| |
Time for a release.
|