1. 07.02.2018 1 коммит
  2. 05.02.2018 1 коммит
  3. 28.12.2017 1 коммит
  4. 20.12.2017 1 коммит
  5. 08.11.2017 1 коммит
  6. 25.10.2017 1 коммит
  7. 25.05.2017 1 коммит
  8. 23.05.2017 1 коммит
  9. 07.03.2017 1 коммит
  10. 21.02.2017 1 коммит
  11. 27.12.2016 1 коммит
  12. 05.12.2016 1 коммит
  13. 25.11.2016 1 коммит
  14. 22.11.2016 1 коммит
  15. 01.11.2016 1 коммит
  16. 25.10.2016 1 коммит
    • Kai Uwe Broulik's avatar
      Manually delete PowerDevil Core on teardown
      · 70177b06
      Kai Uwe Broulik создал
      The QObject children cleanup routine is run after QGuiApplication's destructor after which
      the X connection has already been cleaned up. By manually deleting in PowerDevilApp's
      destructor, we delete Core first before any Qt cleanup happens.
      
      CHANGELOG: PowerDevil no longer crashes on logout
      
      BUG: 371127
      FIXED-IN: 5.8.3
      
      Differential Revision: https://phabricator.kde.org/D3152
      70177b06
  17. 21.10.2016 1 коммит
  18. 18.10.2016 1 коммит
  19. 11.10.2016 1 коммит
  20. 29.09.2016 2 коммита
  21. 20.09.2016 1 коммит
  22. 15.09.2016 3 коммита
    • Jonathan Riddell's avatar
      Update version number for 5.7.95
      · 76ce82b8
      Jonathan Riddell создал
      GIT_SILENT
      76ce82b8
    • Kai Uwe Broulik's avatar
      Clear idle timeouts when session becomes inactive
      · ece8adac
      Kai Uwe Broulik создал
      When the session becomes inactive, clear all idle timeouts, so we don't get them delivered
      while we're inactive or just when we're about to become active again.
      
      Depending on your setup, PowerDevil might be blocked on X before it gets the "session is now
      inactive" signal, so it still suspends when becoming active again :/ It should still make it
      a bit less likely (and works for me :D)
      
      CCBUG: 354250
      
      Differential Revision: https://phabricator.kde.org/D2033
      ece8adac
    • Kai Uwe Broulik's avatar
      Emit brightnessSupportQueried with the proper value
      · 03717dc7
      Kai Uwe Broulik создал
      Just because the sysfs helper succeeded, doesn't mean we actually have screen brightness support.
      Only if maximum brightness greater than 0 is reported, we'll announce its support.
      This fixes the brightness slider showing up in the KCM on desktop computers.
      
      The battery monitor already has the same logic and correctly did not show brightness
      sliders in this case.
      
      Differential Revision: https://phabricator.kde.org/D2775
      03717dc7
  23. 13.09.2016 1 коммит
  24. 12.09.2016 1 коммит
  25. 05.09.2016 3 коммита
  26. 04.09.2016 1 коммит
  27. 02.09.2016 1 коммит
  28. 31.08.2016 1 коммит
  29. 18.08.2016 1 коммит
    • Bhushan Shah's avatar
      [upowerbackend] set cached brightness manually in case of led backlight
      · 26a48f9d
      Bhushan Shah создал
      Summary:
      In normal backlight subsystem's drivers typical workflow is,
      
      - setBrightness gets called
      - it writes to sysfs file using backlight helper
      - kernel sends uevent for brightness change
      - onDeviceChanged is triggered
      - we update cache value
      
      However in case of leds subsystem, kernel doesn't send uevent for
      brightness change, hence uevent is never triggered and this doesn't
      update cached value of brightness, resulting in DBus signal for
      brightnessChanged never being emitted.
      
      Test Plan: Tested on Nexus 5 which uses leds subsystem
      
      Reviewers: #plasma, broulik
      
      Reviewed By: #plasma, broulik
      
      Subscribers: graesslin, plasma-devel
      
      Tags: #plasma
      
      Differential Revision: https://phabricator.kde.org/D2470
      26a48f9d
  30. 12.08.2016 2 коммита
  31. 11.08.2016 1 коммит
  32. 10.08.2016 3 коммита