1. 27.12.2016 1 коммит
  2. 05.12.2016 1 коммит
  3. 25.11.2016 1 коммит
  4. 22.11.2016 1 коммит
  5. 01.11.2016 1 коммит
  6. 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
  7. 21.10.2016 1 коммит
  8. 18.10.2016 1 коммит
  9. 11.10.2016 1 коммит
  10. 29.09.2016 2 коммита
  11. 20.09.2016 1 коммит
  12. 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
  13. 13.09.2016 1 коммит
  14. 12.09.2016 1 коммит
  15. 05.09.2016 3 коммита
  16. 04.09.2016 1 коммит
  17. 02.09.2016 1 коммит
  18. 31.08.2016 1 коммит
  19. 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
  20. 12.08.2016 2 коммита
  21. 11.08.2016 1 коммит
  22. 10.08.2016 5 коммитов
    • Kai Uwe Broulik's avatar
      Merge branch 'Plasma/5.7'
      · 435bc0d7
      Kai Uwe Broulik создал
      435bc0d7
    • Kai Uwe Broulik's avatar
      Revert "Don't unconditionally emit buttonPressed on profile load"
      · 71e9a336
      Kai Uwe Broulik создал
      It turns out this code was a fix for Bug 243618 and the bug addressed by
      the aforementioned commit was actually caused by KScreen failing to
      map the output to a type and then PowerDevil did not prevent lid action
      because it didn't see an external screen (it ignores unknown ones).
      This has been fixed in KScreen 5.7 already, so we should be all set \o/
      
      This reverts commit 48c3dca6.
      71e9a336
    • l10n daemon script's avatar
      SVN_SILENT made messages (.desktop file) - always resolve ours
      · 71655f8d
      l10n daemon script создал
      In case of conflict in i18n, keep the version of the branch "ours"
      To resolve a particular conflict, "git checkout --ours path/to/file.desktop"
      71655f8d
    • Kai Uwe Broulik's avatar
      Merge branch 'Plasma/5.7'
      · 391b9cc2
      Kai Uwe Broulik создал
      391b9cc2
    • Kai Uwe Broulik's avatar
      Don't unconditionally emit buttonPressed on profile load
      · 48c3dca6
      Kai Uwe Broulik создал
      A button press (technically the "lid closed" event is also a button press) should
      always be some consicious action triggered by the user. By emitting this signal
      unconditionally on profile load (ie. whenever changing an activity or (un)plugging AC)
      the session might always lock or suspend when this happens.
      
      If and only if a profile would really like to take some action or set some state
      depending on the lid state on profile load - which none do, the handle button
      press action should only react on explicit button presses anyway - it can still
      ask the backend for isLidClosed in its onProfileLoad method.
      
      BUG: 366125
      FIXED-IN: 5.7.4
      
      Differential Revision: https://phabricator.kde.org/D2325
      48c3dca6
  23. 09.08.2016 2 коммита
  24. 08.08.2016 1 коммит
    • Bhushan Shah's avatar
      Convert powerdevil backends to proper plugins
      · 2e2faec9
      Bhushan Shah создал
      Summary:
      This converts the powerdevil backends into proper plugins that are
      loaded at runtime instead of just hardcoding upowerbackend. And are also
      seperated from the powerdevil kded. This is first step to have other
      modules for example, wayland, hwcomposer etc.
      
      Logic for finding and loading backends is mostly inspired from the
      kscreen, currently it just loads upower backend because it is only
      module available. This logic can be changed when new backends are
      introduced in powedevil.
      
      Test Plan:
      compiles, builds and installs backend module powerdevilupowerbackend.so
      into proper plugin path. Also verified with powerdevil kded that it gets
      loaded properly.
      
      Reviewers: #plasma, broulik
      
      Reviewed By: #plasma, broulik
      
      Subscribers: plasma-devel
      
      Tags: #plasma
      
      Differential Revision: https://phabricator.kde.org/D2369
      2e2faec9
  25. 06.08.2016 2 коммита
  26. 02.08.2016 1 коммит
  27. 28.07.2016 2 коммита