1. 15 Feb, 2017 1 commit
  2. 05 Feb, 2017 1 commit
  3. 02 Feb, 2017 1 commit
    • Owen W. Taylor's avatar
      gsm-systemd.c: Restrict the login monitor to the "session" category · a9e98056
      Owen W. Taylor authored
      We only are interested in changes to sd_session_get_active(), so only
      listen for changes in the "session" category. This reduces overhead
      by a small amount, and also reduces the amount of /var/run/systemd
      that needs to be read. (Bug 772537 is a failure because of a SELinux
      policy preventint reading /var/run/systemd/machines - which we don't
      need to monitor anyways.)
      a9e98056
  4. 13 Jan, 2017 3 commits
  5. 09 Jan, 2017 1 commit
  6. 05 Jan, 2017 1 commit
  7. 24 Oct, 2016 1 commit
  8. 10 Oct, 2016 2 commits
  9. 20 Sep, 2016 1 commit
  10. 25 Aug, 2016 1 commit
  11. 18 Aug, 2016 1 commit
  12. 16 Aug, 2016 1 commit
    • Dominique Leuenberger's avatar
      Do not report errors in absence of dbus-update-activation-environment · 4abdb792
      Dominique Leuenberger authored
      dbus-update-activation-environment was introduced with dbus 1.10.4
      gnome-session by itself does not depend on any specific version of
      dbus at all - but on dbus-glib-1 (DBUS_GLIB_REQUIRED=0.76)
      
      The latest version of dbus-glib (ver 106) requires dbus-1 1.8: it is
      thus a valid setup to run not have dbus-update-activation-environment
      on the system. Warning the user about its absence is alerting users
      for not reason.
      4abdb792
  13. 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
  14. 01 Jul, 2016 1 commit
  15. 30 Jun, 2016 1 commit
  16. 09 May, 2016 3 commits
  17. 09 Apr, 2016 2 commits
  18. 01 Apr, 2016 1 commit
  19. 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
  20. 14 Mar, 2016 2 commits
  21. 09 Mar, 2016 2 commits
  22. 07 Mar, 2016 3 commits
  23. 04 Mar, 2016 7 commits
  24. 03 Mar, 2016 1 commit