| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
| |
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).
|
|
|
|
|
| |
GDM needs to ship the systemd definition for the custom GNOME session it
starts.
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
Our turkey has freezer burn, so I'm dropping it.
https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/96
|
|
|
|
|
|
|
|
|
|
| |
We're going to be switching to meson, and meson doesn't
deal too well with an @ in the configuration file that's not
part of a substitution variable.
This commit switches the gdm service over to use a cmake style
of substitution variables, so we can later tell meson to use
configure in cmake mode and workaround the @ confusion.
|
|
|
|
|
|
|
|
| |
We disable Wayland on Cirrus since f15e6451, but the cirrus driver was
reimplemented in kernel v5.2 or later. This commit will enable Wayland
on Cirrus chipset.
Closes #586
|
| |
|
|
|
|
|
|
| |
In theory, XSettings is irrelevant to the services that are spawned
in the gdm session. In practice, this would allow us to use a pure
Wayland compositor (i.e. no Xwayland) in the gdm session.
|
|
|
|
|
|
| |
Both gsd-mouse and gsd-clipboard are dropped from gnome-settings-daemon,
and their functionality implemented in mutter. GDM shouldn't require them
either.
|
|
|
|
|
|
| |
Various generated files are ending up being disted, which is wrong
becuase they leak the maintainer's prefix into the tarball and are
generated anyway during build.
|
|
|
|
|
|
| |
kill-session-processes=1 is long gone
Signed-off-by: Marc-Antoine Perennou <Marc-Antoine@Perennou.com>
|
| |
|
|
|
|
|
|
|
| |
This allows gdm to pass the LUKS password through to PAM.
The login keyring will now be unlocked automatically if autologin is
enabled!
|
|
|
| |
This reverts commit 762b312bb98d31bd036fbcc8d61e53d5b1298d65
|
|
|
|
|
| |
This allows gdm to pass the LUKS password through to PAM.
The login keyring will now be unlocked automatically if autologin is enabled!
|
|
|
|
|
|
|
|
|
| |
At the moment GLX applications don't work well when the
proprietary nvidia driver is used with a wayland session.
For now, disable wayland on that hardware, and users who
want to opt in can just edit the udev rule.
(or add their own that overrides it)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Different distributions place udev rules in
different locations (depending on whether or
not /usr is a symlink to /)
That means the location needs to be configurable.
This commit adds a new ./configure argument,
--with-udevdir that allows distributions to specify
where udev looks for its data files.
By default it pulls the answer from pkg-config.
This commit also fixes `make distcheck` when run
by an unprivileged user by disabling udev rule
installation entirely during distcheck.
Small changes by Ray Strode.
Closes https://gitlab.gnome.org/GNOME/gdm/merge_requests/44
|
|
|
|
|
|
|
|
|
| |
Disable wayland for Huawei Hi1710 chipsets.
The login screen is skewed/distorted on arm server, and I couldn't
find root cause, and no other developer ever has access to the hardware.
https://gitlab.gnome.org/GNOME/mutter/issues/219
|
|
|
|
|
| |
The $prefix was /usr in general, but rules in /usr/lib/udev/ can't
be loaded by udev, so just remove it.
|
|
|
|
|
|
| |
This got dropped accidentally i think because of .gitignore
See merge request GNOME/gdm!5
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Now that we have a gdm-disable-wayland binary for disabling
wayland at boot, we should use it.
This commit changes the cirrus udev rule to use gdm-disable-wayland,
rather than running sh and printf.
https://bugzilla.gnome.org/show_bug.cgi?id=796315
|
|
|
|
|
|
|
|
|
|
|
| |
gdm.conf-custom.in has a comment explaining how to disable wayland and
force Xorg.
That comment misspells the word "Uncomment".
This commit corrects the spelling.
https://bugzilla.gnome.org/show_bug.cgi?id=795825
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=764567
|
|
|
|
|
|
| |
Disable Wayland on Cirrus chipsets where it is not supported yet.
https://bugzilla.gnome.org/show_bug.cgi?id=789081
|
|
|
|
|
|
|
|
|
|
| |
The "org.gnome.SettingsDaemon.A11yKeyboard" has been been removed,
now handled in gnome-shell/mutter instead.
This is similar to the analagous commit in gnome-session for the
user session definition.
https://bugzilla.gnome.org/show_bug.cgi?id=792932
|
|
|
|
|
|
|
| |
This used to be done with a special greeter indicator, but it's
much simpler to just define the presets accordingly.
https://bugzilla.gnome.org/show_bug.cgi?id=788942
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=787288
|
|
|
|
|
|
|
|
|
| |
We no longer have the orientation and xrandr services for g-s-d anymore.
That stuff is now part of mutter (see bug 7782232)
This commit drops them from the session file.
https://bugzilla.gnome.org/show_bug.cgi?id=785135
|
|
|
|
|
|
| |
This reverts commit 9fb36b5bef44bfe4aa1dda52196e08480638ce35.
https://bugzilla.gnome.org/show_bug.cgi?id=784340
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts
https://git.gnome.org/browse/gdm/commit/?id=f66cdfcb2
and renames the session from gdm-shell to gnome-login.
The removal caused problems for Ubuntu 17.10 which does not
include gnome.session by default.
https://launchpad.net/bugs/1701243
https://bugzilla.gnome.org/show_bug.cgi?id=784340
|
| |
|
|
|
|
|
|
|
| |
This was dropped in f66cdfcb but GDM won't start when the
default session-name is set to something else
https://bugzilla.gnome.org/show_bug.cgi?id=781793
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
A logic error in the Makefile means that the systemd unit will
only get installed if the unit dir doesn't yet exist. That's normally
the case for package builds, but won't be the case at all for builds
from tarball.
This commit fixes up the logic.
https://bugzilla.gnome.org/show_bug.cgi?id=781082
|
|
|
|
|
|
|
| |
This is no longer set in the 00-upstream-settings defaults key file
since commit f66cdfcb, so no point on locking it down here.
https://bugzilla.gnome.org/show_bug.cgi?id=744764
|
|
|
|
|
|
|
| |
This are ignored by GTK3 and GNOME Shell now, and are only relevant
for GTK2 and other legacy apps now, not for GDM or gnome-initial-setup.
https://bugzilla.gnome.org/show_bug.cgi?id=780866
|
|
|
|
|
|
|
|
|
|
| |
gnome-settings-daemon will not use dconf to know which plugin (now
helper daemon) to run anymore. Instead, this logic will be implemented
directly in gnome-settings-daemon.
See https://bugzilla.gnome.org/show_bug.cgi?id=772370
https://bugzilla.gnome.org/show_bug.cgi?id=772447
|
|
|
|
|
| |
These files haven't been used since multistack became
a hard requirement.
|
|
|
|
|
|
|
|
|
|
|
| |
In theory sending the password to them could be beneficial.
If for instance, they have pam_krb5 or pam_ecryptfs or pam_sss.
In practice, the stacks will fail if the passwords don't match,
and prevent autologin from continuing.
This commit just sidesteps them for now. Eventually,
authconfig/et al, will need to get updated to accomodate us.
|
|
|
|
| |
It prevents postlogin from getting run.
|
|
|
|
|
|
|
|
|
|
|
| |
If pam_gdm fails we shouldn't call into pam_unix since it can lead
to the system asking for a password, and autologin isn't equipped for
that.
This commit changes the pam configuration to jump to pam_permit if
pam_gdm fails.
https://bugzilla.gnome.org/show_bug.cgi?id=770612
|
|
|
|
| |
Signed-off-by: Marc-Antoine Perennou <Marc-Antoine@Perennou.com>
|
|
|
|
|
|
| |
Since it was dropped in gnome-settings-daemon 3.20
https://bugzilla.gnome.org/show_bug.cgi?id=770418
|