summaryrefslogtreecommitdiff
path: root/data
Commit message (Collapse)AuthorAgeFilesLines
* 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
* systemd: change to KillMode=process•Ray Strode2015-03-301-0/+1
| | | | | | | | | | | | By default systemd will kill the entire control-group in one fell swoop. The problem is, things don't get shutdown in the right order then, and there's a race where GDM will begin restarting X servers as soon as they're killed. This commit tells systemd to just kill the main GDM process, and let it handle killing all its children on its own. https://bugzilla.gnome.org/show_bug.cgi?id=747088
* data: correct comment for disabling waylandRay Strode2015-03-201-1/+1
| | | | | | | | | The comment incorrectly says to put WaylandEnable=true to disable wayland. This commit flips it to say WaylandEnable=false https://bugzilla.gnome.org/show_bug.cgi?id=746523
* data: add a couple of tips to custom.confRay Strode2015-03-191-0/+4
| | | | | | | | | | | There are two things that are pretty useful for a user to do when troubleshooting problems: 1) turn on debugging 2) turn of wayland support since it's so new This commit adds comments to custom.conf to give tips on how to do those things.
* systemd: call plymouth-quit if gdm failsSimon McVittie2015-03-121-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | gdm.service Conflicts with plymouth-quit.service, so it does not run when it normally would (because GDM wants to handle the handover from plymouth to X11 itself). This means that if gdm fails to start for whatever reason, plymouth is never stopped, so plymouth-quit-wait.service never finishes. This, in turn, means that getty@tty*.service, which is After plymouth-wait-quit.service, never starts, and there is no way to log in locally and fix the problem (Debian bug #780257, but not Debian-specific). In Debian 8, not all display managers have been migrated to participate in managing the display-manager.service symlink yet (in particular, kdm and wdm have not), so gdm has a transitional ExecStartPre that stops it from running if kdm or wdm is selected as the active DM. This has the same effect of preventing plymouth from running (Debian-specific bug #766462). It's easy to avoid both of those situations by scheduling plymouth-quit.service to run if gdm fails. Bug: https://bugzilla.gnome.org/show_bug.cgi?id=746023 Bug-Debian: https://bugs.debian.org/766462 Bug-Debian: https://bugs.debian.org/780257
* systemd: don't require lang file to existRay Strode2015-03-091-1/+1
| | | | | | | | | | | | | | commit fbb922cfcf4e389b0aa416d9a81c45f8f938f104 made sure to source /etc/default/locale on debian so that GDM gets started with the correct locale. Unfortunately, now if that file doesn't exist (which is entirely legitimate) then GDM won't start. This commit makes sure to still start GDM, even if the file couldn't be sourced. https://bugzilla.gnome.org/show_bug.cgi?id=745868
* systemd: don't have After=plymouth-quit-wait.serviceRay Strode2015-03-091-1/+3
| | | | | | | plymouth-quit-wait waits for plymouth to quit, we quit plymouth, so putting After=plymouth-quit-wait means we'll wait forever. https://bugs.freedesktop.org/show_bug.cgi?id=89475
* systemd: add back blank line between sectionsRay Strode2015-03-091-0/+1
| | | | This looks cleaner. Suggested by Daniel Drake
* systemd: make sure to only start plymouth is startedRay Strode2015-03-091-2/+11
| | | | | | | | | | | This commit makes sure gdm doesn't start in parallel with plymouth, which could lead to plymouth activating after X is started. Furthermore, GDM is replacing getty@tty1.service and plymouth-quit.service, so it needs to have the same dependencies as them. https://bugs.freedesktop.org/show_bug.cgi?id=89475
* data: drop caribou autostart fileRay Strode2015-03-032-9/+0
| | | | | | | It's no longer needed and it makes assumptions about install location. https://bugzilla.gnome.org/show_bug.cgi?id=740788
* systemd: import language into daemon environmentRay Strode2015-02-272-0/+2
| | | | | | | | | By default GDM is started with a pretty blank environment. This commit makes sure that the default locale for the system is used. https://bugzilla.gnome.org/show_bug.cgi?id=745286
* Revert "defaults: disable InitialSetup for now"Ray Strode2015-02-241-1/+1
| | | | | | | | This reverts commit 2d089ea6f5c123f8ad67fcab964e9ca8bd58b7ad. It's working again. https://bugzilla.gnome.org/show_bug.cgi?id=745139
* defaults: disable InitialSetup for nowRay Strode2015-02-211-1/+1
| | | | | It's actually pretty broken at the moment, for now disable it.
* local-display-factory: provide override for disabling waylandRay Strode2015-02-181-0/+5
| | | | | | | | | | Since this wayland code is still pretty new, we need to provide an exit tactic for users. This commit introduces daemon/WaylandEnable which can be set to false, to disable wayland support. https://bugzilla.gnome.org/show_bug.cgi?id=744764
* data: add a gnome-shell-wayland.desktop fileRay Strode2015-02-182-0/+9
| | | | | | | This is like gnome-shell.desktop but for wayland. It adds the --mode=gdm argument. https://bugzilla.gnome.org/show_bug.cgi?id=744764
* data: drop gdm-shell.sessionRay Strode2015-02-183-17/+0
| | | | | | | It's identical to gnome.session these days. All GDMification comes from the overriden gnome-shell.desktop file. https://bugzilla.gnome.org/show_bug.cgi?id=744764
* Revert "pam: drop postlogin from fedora pam config"Ray Strode2015-01-167-0/+15
| | | | | | | | | This reverts commit 76d26d8c1c37c6bd38bcac082d5cc62670fe5d39. It breaks pam_ecryptfs. Downstream: https://bugzilla.redhat.com/show_bug.cgi?id=1174366 https://bugzilla.gnome.org/show_bug.cgi?id=743045
* defaults: set default ping interval to 0Ray Strode2014-12-191-1/+1
| | | | | | | | | | We apparently never reset the ping alarm() so a non-0 ping interval means the session will unconditionally be killed after the ping interval. For now set the ping interval to 0. https://bugzilla.gnome.org/show_bug.cgi?id=741766
* systemd: strip plymouth bits from unit file if built --without-plymouthRay Strode2014-12-192-2/+4
| | | | | | | Otherwise, if you have plymouth, but build --without-plymouth then boot will screw up https://bugzilla.gnome.org/show_bug.cgi?id=740802
* redhat-pam: get rid of pam_nologin from launch environment stackRay Strode2014-10-101-1/+0
| | | | | pam_nologin is supposed to prevent users from logging in, not prevent the login screen from coming up.
* Remove files related to the simple-greeter and the fallback sessionLaurent Bigonville2014-10-015-33/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=710847
* Update caribou autostart file for caribou path changesKalev Lember2014-09-172-2/+13
| | | | | | The executable was moved from bin to libexec in caribou 0.14.4 release. https://bugzilla.gnome.org/show_bug.cgi?id=736612
* xdmcp: Allow timed/autologin on remote displaysMario Izquierdo Rodríguez2014-08-201-0/+5
| | | | | | | | This commit readds the security/AllowRemoteAutoLogin key (deprecated in >= 2.20) and so XDMCP setups can be configured to use autologin and timedlogin. https://bugzilla.gnome.org/show_bug.cgi?id=624958
* Fix a typo in openembedded pam autologin rulesVadim Rutkovsky2014-05-311-1/+1
|
* Fix autologin on continuousMatthias Clasen2014-05-301-0/+1
| | | | | This is the minimal addition needed to make autologin on gnome-continuous not end up with a black screen.
* pam: drop postlogin from fedora pam configRay Strode2014-04-157-13/+0
| | | | | | | It's just used in practice to inflict ugly "Last Login" messages on the GDM screen https://bugzilla.gnome.org/show_bug.cgi?id=728281
* pam: improve keyring integration on fedoraRay Strode2014-03-271-1/+2
| | | | | | This commit properly hooks in gnome-keyring into the password stack, so password changes are caught at login time, and the keyring is appropriately rekeyed.
* Add caribou to the greeter autostart directoryMatthias Clasen2014-03-112-0/+7
| | | | | | | This is necessary to make the on-screen keyboard work for gnome-initial-setup. https://bugzilla.gnome.org/show_bug.cgi?id=726143
* data: removing 'workingdir' dconf manipulationsRyan Lortie2014-02-011-7/+0
| | | | | | | According to Ray, this is left over from the (now very) old way of generating the dconf database at install time and should be removed. https://bugzilla.gnome.org/show_bug.cgi?id=722241
* move over to using 'dconf compile' and file-dbRyan Lortie2014-01-317-43/+20
| | | | | | | | | | | | | | | | | | | Instead of installing keyfiles in /etc and running 'dconf update' to generate the database in place (or requiring package system triggers to do so for us), just build the database in-tree using the new 'dconf compile' command. We can install that in our pkgdatadir. dconf now also looks in XDG_DATA_DIRS in addition to /etc when finding profiles, so install ours there too. This makes gdm /etc-clean with respect to dconf. If users want to make additional customisations to the gdm login session then they should create their own dconf database in /etc/dconf and then replace the 'gdm' profile with one that references their new db (by way of /etc/dconf/profile/gdm, which is searched first). https://bugzilla.gnome.org/show_bug.cgi?id=722241
* Revert "move over to using 'dconf compile' and file-db"Ray Strode2014-01-277-19/+43
| | | | This reverts commit 766d07bd1b6aa1c0e631676ad6b6a983d46624f2.
* Revert "data: removing 'workingdir' dconf manipulations"Ray Strode2014-01-271-0/+20
| | | | This reverts commit d74c93a2d2c3e88ec8fc0765edac8722bd57408d.
* data: removing 'workingdir' dconf manipulationsRyan Lortie2014-01-151-20/+0
| | | | | | | According to Ray, this is left over from the (now very) old way of generating the dconf database at install time and should be removed. https://bugzilla.gnome.org/show_bug.cgi?id=722241
* move over to using 'dconf compile' and file-dbRyan Lortie2014-01-157-43/+19
| | | | | | | | | | | | | | | | | | | Instead of installing keyfiles in /etc and running 'dconf update' to generate the database in place (or requiring package system triggers to do so for us), just build the database in-tree using the new 'dconf compile' command. We can install that in our pkgdatadir. dconf now also looks in XDG_DATA_DIRS in addition to /etc when finding profiles, so install ours there too. This makes gdm /etc-clean with respect to dconf. If users want to make additional customisations to the gdm login session then they should create their own dconf database in /etc/dconf and then replace the 'gdm' profile with one that references their new db (by way of /etc/dconf/profile/gdm, which is searched first). https://bugzilla.gnome.org/show_bug.cgi?id=722241
* daemon: get rid of greeter language selectionRay Strode2013-12-161-7/+0
| | | | | | | These days the greeter doesn't let you pick a language at log in time. This commit drops the interface, since it's unused, and we don't have any API guarantees in libgdm.
* Add an option to use GDM as a standalone XDMCP serverLaurent Bigonville2013-11-111-0/+5
| | | | | | | | | This patch add an option (xdmcp/ShowLocalGreeter) to disable the local X console and turn GDM into a simple XDMCP server Thanks to Patrick Monnerat and Josselin Mouette for the patch https://bugzilla.gnome.org/show_bug.cgi?id=567522
* data: Make pam_systemd optional in exherbo/fsPacho Ramos2013-10-162-2/+2
| | | | This prevents it from breakings setups building using --without-systemd
* data/pam-lfs: update for latest systemd/PAM changesArmin K2013-08-287-19/+12
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=706975
View Lorry Controller Status