1. 21 Jan, 2016 2 commits
  2. 27 Dec, 2015 1 commit
  3. 12 Dec, 2014 1 commit
  4. 24 Mar, 2014 1 commit
  5. 23 Jan, 2014 1 commit
  6. 21 Aug, 2013 1 commit
  7. 20 Aug, 2013 3 commits
  8. 06 Mar, 2013 1 commit
  9. 28 Feb, 2013 1 commit
  10. 31 Jan, 2013 1 commit
  11. 13 Jan, 2013 1 commit
  12. 23 Nov, 2012 1 commit
  13. 13 Nov, 2012 6 commits
  14. 07 Nov, 2012 7 commits
  15. 28 Oct, 2012 1 commit
  16. 15 Oct, 2012 1 commit
  17. 30 Sep, 2012 1 commit
  18. 07 Jul, 2012 1 commit
  19. 19 Oct, 2011 2 commits
  20. 07 Jun, 2011 1 commit
  21. 14 Mar, 2011 1 commit
    • Matthias Clasen's avatar
      gnome-session-check-accelerated: Avoid double checking · ce296840
      Matthias Clasen authored
      Add a mechanism to have a second gnome-session-check-accelerated
      instance wait until a first instance is done with the GL checks.
      This is meant to accomodate the situation where we run the check
      in the gdm login session, but the user quickly logs in, and
      gnome-session runs the check again.
      ce296840
  22. 09 Mar, 2011 1 commit
  23. 08 Mar, 2011 2 commits
  24. 03 Mar, 2011 1 commit
    • Colin Walters's avatar
      gnome-session-check-accelerated: Set X property _GNOME_SESSION_ACCELERATED · ffe98dd1
      Colin Walters authored
      It would make sense to run gnome-session-is-accelerated in
      GDM, in parallel with the user is typing their password.  A
      good way to pass that knowledge through to gnome-session
      so it knows it can avoid repeating the same check is via
      an X property.
      
      So create a new tool "gnome-session-check-accelerated", which takes
      the name of the old one (now renamed "gnome-session-check-accelerated-helper")
      and stores that status as an X property.  gnome-session will then
      itself run it again, but it should pick up the property and reuse that
      value.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=641992
      ffe98dd1