1. 18 May, 2022 1 commit
    • Louis Moureaux's avatar
      Fix profile switching in the brightness actions · 3cdeeb68
      Louis Moureaux authored
      The current code assumes that the action is notified of every profile change,
      which is only the case when the action is configured to run in all profiles.
      The code that prevents brightness from being raised when switching to a more
      conservative profile gets confused if the action didn't run in the "previous"
      profile. Make it more robust by always querying the core for the previous
      profile, which it luckily hasn't updated yet when the action gets executed.
      
      BUG: 394945
      FIXED-IN: 5.25
      3cdeeb68
  2. 16 May, 2022 1 commit
  3. 15 May, 2022 1 commit
  4. 28 Apr, 2022 1 commit
  5. 24 Apr, 2022 1 commit
  6. 23 Apr, 2022 6 commits
  7. 11 Apr, 2022 1 commit
  8. 08 Apr, 2022 1 commit
    • Edo Friedman's avatar
      Add percentage display next to the brightness and keyboard backlight sliders in KCM · 04815f45
      Edo Friedman authored and Nate Graham's avatar Nate Graham committed
      Currently if you were to open System Settings and go to the
      Power Management -> Energy Saving KCM, you will see the "Screen Brightness"
      and "Keyboard Backlight" sliders, but there will be no way to know the exact
      number you selected until you apply the change and look at the "Energy Saving"
      applet. This commit changes that by adding percentage labels to the right of
      both sliders.
      
      BUG: 440314
      FIXED-IN: 5.25
      04815f45
  9. 26 Mar, 2022 1 commit
  10. 24 Mar, 2022 1 commit
  11. 23 Mar, 2022 1 commit
    • Max Ramanouski's avatar
      Write brightness to all raw devices · 761fc8a4
      Max Ramanouski authored and Nate Graham's avatar Nate Graham committed
      On some laptops, there are multiple enabled raw backlight devices, and
      backlighthelper can't choose right device.
      
      For example: NVIDIA Optimus laptop, Lenovo 15ARH05. It has two GPUs: AMD
      and NVIDIA, both of them provide their backlight device, both backlight
      devices are raw type and enabled(in case prime is used). Backlighthelper
      without this fix selects NVIDIA device for backlight, but on this laptop
      brightness is controlled by AMD gpu, so user can't control brightness.
      
      This fix implements additional list for all raw devices. This list is
      loaded on initUsingBacklightType. List contains pairs of sysfs path and
      max brightness of device. When brightness is changed, backlighthelper goes
      through entries starting from second(first device is written by data from
      m_dirname) and writes brightness with correcting difference between
      max_brightness in different devices. For all other cases(read brightness
      and other) first raw device is used.
      
      BUG: 399646
      FIXED-IN: 5.25
      761fc8a4
  12. 14 Mar, 2022 1 commit
  13. 11 Mar, 2022 1 commit
  14. 08 Mar, 2022 1 commit
  15. 28 Feb, 2022 1 commit
  16. 26 Feb, 2022 2 commits
  17. 24 Feb, 2022 1 commit
  18. 23 Feb, 2022 1 commit
    • Xingang Li's avatar
      Improved backlight devices selection · 401e3ed8
      Xingang Li authored
      1. Change backlight devices selection order, return more early;
      2. Only check raw type devices's enable attribute. If no raw
      device available, we will search again without above checking.
      
      BUG: 399646
      401e3ed8
  19. 22 Feb, 2022 1 commit
  20. 14 Feb, 2022 1 commit
  21. 07 Feb, 2022 1 commit
  22. 18 Jan, 2022 1 commit
  23. 13 Jan, 2022 2 commits
  24. 04 Jan, 2022 1 commit
  25. 23 Dec, 2021 1 commit
    • Fushan Wen's avatar
      powerprofileconfig: Use m_profileCombo as the watcher's parent · 9b8a9dfd
      Fushan Wen authored
      `m_profileCombo` could be an invalid pointer, because when clicking an
      item, `QAbstractItemView::clicked` and `QAbstractItemView::activated` in
      systemsettings both will be emitted, and `IconMode::changeModule` will be
      called twice, and `closeModules()` will free `m_profileCombo` in the
      second call, which will crash systemsettings.
      
      To fix the crash, set the watcher's parent to `m_profileCombo`, so when
      `m_profileCombo` is destroyed, the watcher is also destroyed and the
      connection is disconnected to prevent modification to the old `m_profileCombo`.
      
      CCBUG: 443858
      9b8a9dfd
  26. 21 Dec, 2021 1 commit
  27. 19 Dec, 2021 1 commit
  28. 16 Dec, 2021 1 commit
  29. 13 Dec, 2021 1 commit
  30. 12 Dec, 2021 2 commits
  31. 11 Dec, 2021 1 commit
  32. 07 Dec, 2021 1 commit