Skip to content
Snippets Groups Projects
  1. Dec 01, 2022
  2. Nov 09, 2022
  3. Nov 01, 2022
  4. Jan 26, 2021
  5. Dec 22, 2020
  6. Dec 09, 2020
  7. Nov 11, 2020
  8. Nov 06, 2020
  9. Oct 04, 2020
  10. May 21, 2020
  11. Mar 05, 2020
  12. Aug 11, 2019
  13. Jul 28, 2019
  14. Jun 30, 2019
  15. May 17, 2019
  16. Dec 18, 2017
  17. Nov 09, 2017
  18. May 31, 2016
    • Eric Koegel's avatar
      Handle screensaver activity with it's own class (Bug #12603) · 9e70d2e4
      Eric Koegel authored
      Move the screensaver inhibit, heartbeat, and lock code to its own
      set of files we can easily share with xfce4-session. Use the
      screensaver's dbus API if it supports it for inhibit and lock
      calls. Otherwise, use the heartbeat-command and LockCommand
      from xfpm and xfsm if available. Finally, for the lock function,
      fallback to trying xdg-screensaver, xflock4, and xscreensaver-command
      in that order.
      9e70d2e4
  19. Mar 18, 2016
  20. Mar 13, 2016
  21. Feb 16, 2016
    • Eric Koegel's avatar
      Replace XTestFakeKeyEvent with inhibit/heartbeat (Bug #11083) · d0ea6d92
      Eric Koegel authored
      Instead of using XTestFakeKeyEvent, attempt to contact whatever
      screensaver is running via its dbus interface. Failing that,
      a /xfce4-power-manager/heartbeat-command xfconf property will be
      executed every 30 seconds to keep the screensaver from
      launching. This way xscreensaver, xdg-screensaver, caffeine or
      a similar tool can be used.
      d0ea6d92
  22. Jan 25, 2016
  23. Jun 21, 2015
  24. Jun 11, 2015
  25. Jun 06, 2015
  26. May 25, 2015
  27. Apr 09, 2015
Loading