1. 13 Jan, 2017 2 commits
  2. 24 Oct, 2016 1 commit
  3. 10 Oct, 2016 1 commit
  4. 18 Aug, 2016 1 commit
  5. 22 Jul, 2016 1 commit
    • Hanno Böck's avatar
      main: fix heap overflow in dbus-launch wrapping · 7ee3571c
      Hanno Böck authored
      I have discovered a heap overflow with the help of an address sanitizer.
      
      The require_dbus_session() function has this code:
      
              new_argv = g_malloc (argc + 3 * sizeof (*argv));
      
      The intention is to allocate space for (argc + 3) pointers. However obviously a
      parenthesis is missing, therefore only argc bytes + 3 * pointer size gets
      allocated, which is insufficient space. This leads to invalid memory writes.
      
      The fix is trivial: Parentheses around argc + 3.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=768441
      7ee3571c
  6. 09 Apr, 2016 2 commits
  7. 01 Apr, 2016 1 commit
  8. 31 Mar, 2016 1 commit
    • Andreas Henriksson's avatar
      main: fix starting gnome session via startx · 890a797a
      Andreas Henriksson authored
      The changes related to gsm_util_setenv during 3.19.x seems to have
      broken starting a gnome desktop the old fashioned way, eg. via startx.
      
      The gnome.session required components has OnlyShowIn=GNOME; which
      disqualifies them from being started unless XDG_CURRENT_DESKTOP is also
      set to GNOME (by the gio utility function used to look up info).
      
      Currently gnome-session already carries code to catch the case of
      XDG_CURRENT_DESKTOP being unset and set it to GNOME as a fallback.
      Unfortunately the changes to gsm_util_setenv seems to have made it only
      set the values in the (dbus activated) child environment, rather than
      the current environment which g_desktop_app_info_get_show_in is looking
      at.
      
      Make the fallback code set XDG_CURRENT_DESKTOP in both current
      and child environment fixes it.
      Also move the entire hunk of code before initializing gio to
      prevent potential thread issues, now that is uses g_setenv.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=764379
      890a797a
  9. 25 Feb, 2016 2 commits
  10. 21 Jan, 2016 2 commits
  11. 14 Oct, 2015 4 commits
  12. 18 Dec, 2014 1 commit
  13. 17 Dec, 2014 1 commit
  14. 12 Dec, 2014 2 commits
  15. 24 Nov, 2014 1 commit
  16. 19 May, 2014 1 commit
  17. 23 Jan, 2014 1 commit
  18. 03 Sep, 2013 1 commit
  19. 08 Jul, 2013 1 commit
  20. 06 May, 2013 1 commit
  21. 06 Mar, 2013 1 commit
  22. 18 Feb, 2013 1 commit
  23. 25 Jan, 2013 1 commit
  24. 23 Jan, 2013 1 commit
  25. 22 Jan, 2013 1 commit
  26. 15 Dec, 2012 1 commit
  27. 12 Dec, 2012 1 commit
    • Matthias Clasen's avatar
      Support automatic logout after a maximum period of idleness · 7d0e8aed
      Matthias Clasen authored
      This is very commonly requested in any situation with
      shared resources: servers, labs, etc.
      
      We simply start counting down once the session goes idle,
      and display a warning notification when we get close to the
      maximum allowed idle time.
      
      The feature is controlled by two new org.gnome.SessionManager
      settings: max-idle-time and max-idle-action. The time is specified
      in minutes, and the action can be 'none', 'logout' or 'force-logout',
      with 'none' being the default.
      
      This commit adds a libnotify dependency.
      
      http://bugzilla.gnome.org/show_bug.cgi?id=597030
      7d0e8aed
  28. 03 Dec, 2012 1 commit
    • Ray Strode's avatar
      main: disconnect shutdown_cb when manager is destroyed · 6b621684
      Ray Strode authored
      shutdown_cb is supposed to be called when gnome-session is
      running and suddenly the bus is ripped away from it.  Unfortunately,
      it also gets run as part of the normal shutdown path, which it isn't
      designed for.
      
      This commit changes g_signal_connect_swapped to g_signal_connect_object
      to ensure the handler is disconnected when the manager object goes away,
      so the handler isn't called in the normal shutdown path.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=688992
      6b621684
  29. 23 Nov, 2012 1 commit
  30. 21 Nov, 2012 1 commit
  31. 13 Nov, 2012 1 commit
  32. 07 Nov, 2012 1 commit