1. 30 Aug, 2022 1 commit
  2. 22 Aug, 2022 2 commits
  3. 19 Aug, 2022 1 commit
    • David Edmundson's avatar
      Set normal logging category default severity · e9b940a1
      David Edmundson authored
      Hiding warnings only makes life harder when people add logs to bug
      reports. If it does result in superfluous output then those warnings
      shouldn't exist in the first place.
      kscreenlocker has none in the common case.
  4. 17 Aug, 2022 1 commit
  5. 09 Aug, 2022 1 commit
  6. 03 Aug, 2022 1 commit
  7. 30 Jul, 2022 2 commits
  8. 21 Jul, 2022 1 commit
  9. 06 Jul, 2022 1 commit
  10. 03 Jul, 2022 1 commit
  11. 02 Jul, 2022 1 commit
  12. 01 Jul, 2022 2 commits
  13. 27 Jun, 2022 2 commits
  14. 26 Jun, 2022 2 commits
  15. 24 Jun, 2022 2 commits
  16. 21 Jun, 2022 1 commit
  17. 20 Jun, 2022 2 commits
  18. 15 Jun, 2022 2 commits
    • David Edmundson's avatar
      Drop call to QApplication::desktop in x11locker · 71c1cde4
      David Edmundson authored
      We previously needed to create the root window so that we would be
      notified when the root window changed size.
      Since then API has moved to QScreen to get window sizes which has other
      ways of monitoring changes.
      This is for Qt6 porting.
      Testing done:
      - removed this whole block of code and confirmed it still does
       - removed just this one line and confirmed input is still grabbed
    • Fushan Wen's avatar
      Add `repaintNeeded` to fix warning · d3ff9f3c
      Fushan Wen authored
      This is to keep compatible with WallpaperInterface in plasma-framework.
      It doesn't have any practical use.
  19. 14 Jun, 2022 1 commit
  20. 10 Jun, 2022 2 commits
  21. 07 Jun, 2022 1 commit
  22. 01 Jun, 2022 1 commit
    • Arjen Hiemstra's avatar
      Handle fallback packages when checking for screenlocker API version · fdbba676
      Arjen Hiemstra authored
      The current lookandfeel package may not contain the
      "X-Plasma-ApiVersion" metadata key but at the same time also not define
      a custom lockscreen, instead relying on the fallback mechanism. In that
      case, we would end up setting the package path to an empty string,
      causing everything else that is using the package to treat it as
      To fix that, we need to check if the lockscreen comes from the current
      package and if not, check the API version of the fallback package
      instead. Additionally, we also should explicitly set the package path to
      the default of Breeze instead of using an empty string as path, which
      implies an invalid package rather than "use the default".
  23. 31 May, 2022 1 commit
    • David Edmundson's avatar
      Wait for screenlocker UI to call close · 8dbec4a1
      David Edmundson authored
      This is important as it allows the screenlocker to show a prompt for
      passwordless users before unlocking. For example mobile having a simple
      swipe to unlock.
      It also potentially allows a future successful login animation.
      An additional guard is added so rogue QML can't trivially bypass the
      user password; though pragamtically they could before if they emit the
      right signal in the authenticator.
  24. 28 May, 2022 1 commit
  25. 26 May, 2022 1 commit
    • Nate Graham's avatar
      Remove old non-compliant Ctrl+Alt+L shortcut that interferes with apps · 0ce96496
      Nate Graham authored
      KScreenLocker lets the user lock the screen with the Meta+L and
      Ctrl+Alt+L shortcuts by default. This latter shortcut has been reported
      by users to conflict with the Ctrl+Alt+L shortcut in at least one
      user-facing app. System components shouldn't break apps by masking
      their shortcuts.
      This commit removes the Ctrl+Alt+L shortcut, leaving only Meta+L. This
      un-breaks userspace apps using that shortcut.
      BUG: 454397
      FIXED-IN: 5.25
  26. 25 May, 2022 1 commit
  27. 22 May, 2022 1 commit
  28. 21 May, 2022 1 commit
  29. 19 May, 2022 2 commits
  30. 16 May, 2022 1 commit
    • David Edmundson's avatar
      Disable logind integration for kwin's unit tests · 67782537
      David Edmundson authored
      Using real logind causes issues with CI as it's dependent on external
      factors and it can leave the host machine is an unclean state.
      We can't mock it like we do in the internal tests as easily and it
      wouldn't be very useful to do so. We can't disable completly as
      lockscreentest relies on externally emitting a signal on this object.