1. 12 Jun, 2018 2 commits
    • Ray Strode's avatar
      Merge branch 'fix_issue_381' into 'master' · e8c9ba13
      Ray Strode authored
      daemon/gdm-session-record.c: open/close the utmp database
      
      Closes #381
      
      See merge request !1
      e8c9ba13
    • Jason Pleau's avatar
      daemon/gdm-session-record.c: open/close the utmp database · 086d68f2
      Jason Pleau authored
      pututxline() was used without first opening the utxmp database and
      without closing it, preventing the logout entry from being fully
      committed.
      
      This caused the number of logged-in users to increment after each login,
      as logging out did not correctly remove the user login record from utmp.
      
      This commit wraps pututxline() between setutxent() and endutxent(),
      making sure that the login/logout operation are fully flushed.
      
      Fixes #381
      086d68f2
  2. 09 Jun, 2018 1 commit
  3. 04 Jun, 2018 2 commits
  4. 02 Jun, 2018 6 commits
  5. 22 May, 2018 1 commit
  6. 21 May, 2018 2 commits
  7. 17 May, 2018 1 commit
  8. 16 May, 2018 12 commits
  9. 07 May, 2018 3 commits
  10. 24 Apr, 2018 1 commit
  11. 10 Apr, 2018 1 commit
    • Yifan J's avatar
      daemon/gdm-manager.c: quit plymouth when xdmcp is the only allowed connection. · ef9977bf
      Yifan J authored
      gdm is responsible to kill plymouth by spawning the "plymouth quit"
      subprocesses in gdm-manager.c. The current code pathes of quiting
      plymouth can never be reached when xdmcp is the only connection
      allowed. Consequently in the case of
      
          !show_local_greeter && xdmcp_enabled
      
      the plymouth-quit-wait.service will never quit and the login prompt
      will not popup without manual interference. This issue could be
      more obviously observed when a downstream like openSUSE which
      allows a customized sysconfig to switch the corresponding two
      options on a headless server (s390), where the setup is usually:
      
          DISPLAYMANAGER_REMOTE_ACCESS="yes"
          DISPLAYMANAGER_STARTS_XSERVER="no"
      
      The proposed patch handles this edge case by quit plymouth immediately
      when the condition is detected.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=795120
      ef9977bf
  12. 26 Mar, 2018 1 commit
  13. 16 Mar, 2018 1 commit
  14. 13 Mar, 2018 2 commits
  15. 12 Mar, 2018 2 commits
  16. 07 Mar, 2018 2 commits