1. 23 Jun, 2015 1 commit
  2. 12 Jun, 2015 1 commit
  3. 01 Jun, 2015 1 commit
  4. 29 Apr, 2015 1 commit
  5. 01 Apr, 2015 1 commit
  6. 31 Mar, 2015 1 commit
    • Ray Strode's avatar
      systemd: change to KillMode=process• · cd0a0bab
      Ray Strode authored
      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
      cd0a0bab
  7. 20 Mar, 2015 1 commit
  8. 19 Mar, 2015 1 commit
    • Ray Strode's avatar
      data: add a couple of tips to custom.conf · 7421c016
      Ray Strode authored
      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.
      7421c016
  9. 12 Mar, 2015 1 commit
    • Simon McVittie's avatar
      systemd: call plymouth-quit if gdm fails · 234fbc82
      Simon McVittie authored
      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
      234fbc82
  10. 09 Mar, 2015 4 commits
  11. 03 Mar, 2015 1 commit
  12. 27 Feb, 2015 1 commit
  13. 25 Feb, 2015 1 commit
  14. 22 Feb, 2015 1 commit
  15. 18 Feb, 2015 3 commits
  16. 16 Jan, 2015 1 commit
  17. 19 Dec, 2014 2 commits
  18. 10 Oct, 2014 1 commit
  19. 02 Oct, 2014 1 commit
  20. 17 Sep, 2014 1 commit
  21. 20 Aug, 2014 1 commit
  22. 30 May, 2014 2 commits
  23. 15 Apr, 2014 1 commit
  24. 27 Mar, 2014 1 commit
  25. 12 Mar, 2014 1 commit
  26. 01 Feb, 2014 1 commit
  27. 31 Jan, 2014 1 commit
    • Allison Karlitskaya's avatar
      move over to using 'dconf compile' and file-db · feb6ddaf
      Allison Karlitskaya authored
      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
      feb6ddaf
  28. 27 Jan, 2014 2 commits
  29. 15 Jan, 2014 2 commits
    • Allison Karlitskaya's avatar
      data: removing 'workingdir' dconf manipulations · d74c93a2
      Allison Karlitskaya authored
      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
      d74c93a2
    • Allison Karlitskaya's avatar
      move over to using 'dconf compile' and file-db · 766d07bd
      Allison Karlitskaya authored
      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
      766d07bd
  30. 16 Dec, 2013 1 commit
  31. 11 Nov, 2013 1 commit