summaryrefslogtreecommitdiff
path: root/data
Commit message (Collapse)AuthorAgeFilesLines
* build: Don't dist generated filesIain Lane2019-02-251-4/+3
| | | | | | 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.
* pam-exherbo: drop legacy pam_systemd argumentMarc-Antoine Perennou2019-02-161-1/+1
| | | | | | kill-session-processes=1 is long gone Signed-off-by: Marc-Antoine Perennou <Marc-Antoine@Perennou.com>
* Accept all keyboard layouts by default to prevent confusing behaviourilmaisin2019-02-011-0/+3
|
* Launch systemd service with KeyringMode=sharedMichael Catanzaro2018-11-051-0/+1
| | | | | | | This allows gdm to pass the LUKS password through to PAM. The login keyring will now be unlocked automatically if autologin is enabled!
* Revert "Launch systemd service with KeyringMode=shared"Michael Catanzaro2018-11-051-2/+1
| | | This reverts commit 762b312bb98d31bd036fbcc8d61e53d5b1298d65
* Launch systemd service with KeyringMode=sharedMichael Catanzaro2018-11-051-1/+2
| | | | | This allows gdm to pass the LUKS password through to PAM. The login keyring will now be unlocked automatically if autologin is enabled!
* data: disable wayland for proprietary nvidia machinesJonas Ådahl2018-09-061-0/+2
| | | | | | | | | 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)
* autogoo: make udev rules dir configurableBin Li2018-09-051-1/+3
| | | | | | | | | | | | | | | | | | | | | | 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
* data: 61-gdm.rules.inBin Li2018-08-291-0/+2
| | | | | | | | | 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
* data: Makefile.amBin Li2018-08-231-1/+1
| | | | | The $prefix was /usr in general, but rules in /usr/lib/udev/ can't be loaded by udev, so just remove it.
* data: add gdm.schemas.inRay Strode2018-06-221-0/+134
| | | | | | This got dropped accidentally i think because of .gitignore See merge request GNOME/gdm!5
* Migrate from intltool to gettext.wip/nielsdg/intltool2gettextNiels De Graef2018-06-124-184/+48
|
* data: change cirrus blacklist to use gdm-disable-waylandRay Strode2018-05-213-2/+7
| | | | | | | | | | 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
* data: correct typo in commentYan Huang2018-05-171-1/+1
| | | | | | | | | | | 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
* Remove obsolete references to XNEST from the build systemLaurent Bigonville2018-02-121-3/+0
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=764567
* data: Add udev rules to disable Wayland on CirrusFelix Zhang2018-02-122-0/+6
| | | | | | Disable Wayland on Cirrus chipsets where it is not supported yet. https://bugzilla.gnome.org/show_bug.cgi?id=789081
* gnome-login: Adjust to g-s-d's plugin removalsRay Strode2018-02-091-1/+1
| | | | | | | | | | 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
* dconf: Set universal-access icon to always showFlorian Müllner2017-10-131-0/+3
| | | | | | | 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
* gschema: Fix gettext-domainPiotr Drąg2017-09-301-1/+2
|
* systemd: send SIGHUP to gdm on reloadSam Spilsbury2017-09-051-0/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=787288
* data: drop dropped g-s-d servicesRay Strode2017-07-191-1/+1
| | | | | | | | | 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
* Revert "Drop locked down /org/gnome/desktop/session/session-name setting"Ray Strode2017-06-291-0/+1
| | | | | | This reverts commit 9fb36b5bef44bfe4aa1dda52196e08480638ce35. https://bugzilla.gnome.org/show_bug.cgi?id=784340
* data: Add gnome-login.sessionJeremy Bicha2017-06-293-1/+16
| | | | | | | | | | | | | 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
* build-goo: fix distcheckRay Strode2017-06-221-17/+6
|
* dconf defaults: Restore session-name overrideJeremy Bicha2017-04-261-0/+3
| | | | | | | 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
* data: remove stray -n passed to testRay Strode2017-04-191-1/+1
|
* data: install systemd unit even if unit dir already existsDJ Lucas2017-04-191-1/+4
| | | | | | | | | | | 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
* Drop locked down /org/gnome/desktop/session/session-name settingMario Sanchez Prada2017-04-131-1/+0
| | | | | | | 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
* dconf defaults: Remove deprecated a11y related keysMario Sanchez Prada2017-04-041-6/+0
| | | | | | | 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
* dconf defaults: Remove obsolete configurationBastien Nocera2017-03-272-4/+0
| | | | | | | | | | 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
* pam-lfs,pam-redhat: get rid of gdm.pamRay Strode2016-09-073-32/+2
| | | | | These files haven't been used since multistack became a hard requirement.
* pam-exherbo,pam-redhat: avoid password-auth/common-authRay Strode2016-09-072-5/+2
| | | | | | | | | | | 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.
* pam-redhat: don't use substack in autologin caseRay Strode2016-09-061-5/+5
| | | | It prevents postlogin from getting run.
* pam: don't call into pam_unix if pam_gdm fails for autolgoinRay Strode2016-08-302-2/+2
| | | | | | | | | | | 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
* pam: update gdm-autologin for exherbpMarc-Antoine Perennou2016-08-301-1/+1
| | | | Signed-off-by: Marc-Antoine Perennou <Marc-Antoine@Perennou.com>
* dconf defaults: Drop input-devices/hotplug-commandJeremy Bicha2016-08-252-4/+0
| | | | | | Since it was dropped in gnome-settings-daemon 3.20 https://bugzilla.gnome.org/show_bug.cgi?id=770418
* pam: grab cached password from systemd and pass it onRay Strode2016-08-194-7/+14
| | | | | | | | | | | | | 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
* pam-redhat: don't run full account and password stacks for gdm sessionRay Strode2016-04-011-2/+2
| | | | | | | | The login screen user account won't ever have a password or get locked, so there's no reason to run the system-auth password and account stacks for the login screen launch environment. https://bugzilla.gnome.org/show_bug.cgi?id=764472
* openembedded: rename gdm pam file to gdm-passwordRay Strode2016-02-242-1/+1
| | | | | | | This is api expected by the shell, it has to be called gdm-password. https://bugzilla.gnome.org/show_bug.cgi?id=762636
* Update gsettings descriptions for login screen logo settingsMichael Catanzaro2016-01-181-6/+4
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=760495
* Remove [greeter] section from custom.confMichael Catanzaro2016-01-131-2/+0
| | | | | | There are no greeter options anymore https://bugzilla.gnome.org/show_bug.cgi?id=760589
* Add Arch Linux PAM config filesJan Alexander Steffens (heftig)2015-11-107-0/+84
|
* data: drop override xsession filesRay Strode2015-11-093-23/+1
| | | | | | | | We now tell gnome-shell to use GDM mode a different way so we don't need to override the desktop files anymore. https://bugzilla.gnome.org/show_bug.cgi?id=757715
* Xsession: get rid of "custom" sessionRay Strode2015-11-061-9/+0
| | | | | | | | | | | | custom is a magic name we used to allow for having the user decide their session by a ~/.xsession file. We no longer support that construct and haven't for many years. Instead, users who want that functionality can just add a xsession file to accomplish it. This commit just removes some left over cruft that never got cleaned up.
* get rid of references to slavesRay Strode2015-10-271-3/+0
| | | | | | | | I really don't want $ git grep slave to return hits.
* configure: get rid of more conditionalized systemdRay Strode2015-06-231-4/+0
| | | | Woops, 3.17.3 doesn't ship a unit file.
* drop consolekit supportRay Strode2015-06-125-5/+0
| | | | | | It was deprecated in 3.16 to be removed in 3.18 https://bugzilla.gnome.org/show_bug.cgi?id=743940
* Make Xsession installation conditional, and off by defaultJasper St. Pierre2015-06-011-6/+15
| | | | | | | | Most distros use custom logic for their Xsession, so we can't really ship a default here. Doing so would break people running "make install" and expecting things to work. https://bugzilla.gnome.org/show_bug.cgi?id=750220
* Do not hardcode path to true(1).Antoine Jacoutot2015-04-292-2/+2
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=747987
* systemd: change to KillMode=mixedRay Strode2015-04-011-1/+1
| | | | | | | | This is like the previous commit, but a slightly better choice, because it's more fault tolerant; if GDM fails to kill a child, systemd will help out. https://bugzilla.gnome.org/show_bug.cgi?id=747088
View Lorry Controller Status