1. 15 May, 2020 2 commits
  2. 04 May, 2020 4 commits
  3. 01 May, 2020 3 commits
  4. 30 Apr, 2020 5 commits
  5. 28 Apr, 2020 3 commits
  6. 22 Apr, 2020 3 commits
    • Benjamin Berg's avatar
      Merge branch 'benzea/fix-multiple-greeter-sessions' into 'master' · 407f0d5f
      Benjamin Berg authored
      manager: Try looking up session based on PID first
      
      See merge request !90
      407f0d5f
    • Benjamin Berg's avatar
      session: Always use separate session bus for greeter sessions · febeb9a9
      Benjamin Berg authored
      This is a workaround for the fact that we currently need to run multiple
      greeter sessions in multi-seat environments that use the same user. We
      should not be doing this in the first place. Doing this effectively
      prevents GNOME from using a systemd startup, which would cause relevant
      processes to be outside of the session scope preventing lookups of the
      logind session from the PID.
      
      Instead, we really should be running each of the greeter session as a
      separate (dynamic) user. But lacking that, this workaround should get
      multi-seat support up and running again for the time being.
      
      See: #526
      febeb9a9
    • Benjamin Berg's avatar
      manager: Try looking up session based on PID first · 32646105
      Benjamin Berg authored
      Unfortunately, GDM may be running multiple greeters, and each greeter is
      currently using the same user. So while in a lot of setups each user
      should only have one graphical session and also only one DBus session
      bus, this is not true for the gdm greeter.
      
      Lacking another solution (e.g. separate users), we need to be able to
      correctly lookup the session information for all greeter instances. We
      can do so by using sd_pid_get_session and using this information is safe
      if it does return something.
      
      See: #526
      32646105
  7. 18 Apr, 2020 1 commit
  8. 09 Apr, 2020 1 commit
  9. 07 Apr, 2020 1 commit
    • Ray Strode's avatar
      session-worker: ensure initial vt is never picked for !is_initial displays · f843233a
      Ray Strode authored
      Normally, a !is_initial display would never "get" tty1, since the system
      boots to tty1.  But if, for some reason, the user booted to runlevel 3,
      then switched to runlevel 5, the login screen could get started when
      tty1 is free.
      
      That means, e.g., an autologin user can end up getting allocated tty1,
      which is bad, since we assume tty1 is used for the login screen.
      
      This commit opens up /dev/tty1 when querying for available VTs, so that
      it never gets returned by the kernel as available.
      f843233a
  10. 03 Apr, 2020 1 commit
  11. 02 Apr, 2020 1 commit
  12. 30 Mar, 2020 1 commit
  13. 10 Mar, 2020 1 commit
  14. 22 Feb, 2020 1 commit
  15. 07 Feb, 2020 1 commit
  16. 31 Jan, 2020 1 commit
  17. 19 Jan, 2020 1 commit
  18. 27 Dec, 2019 2 commits
  19. 25 Dec, 2019 1 commit
  20. 17 Dec, 2019 1 commit
  21. 27 Nov, 2019 1 commit
  22. 11 Nov, 2019 1 commit
  23. 20 Oct, 2019 1 commit
  24. 11 Oct, 2019 1 commit
  25. 09 Oct, 2019 1 commit