1. 16 Jul, 2019 9 commits
  2. 08 Jul, 2019 1 commit
  3. 07 Jul, 2019 1 commit
  4. 06 Jul, 2019 1 commit
  5. 12 Apr, 2019 1 commit
  6. 23 Mar, 2019 2 commits
  7. 08 Sep, 2018 1 commit
  8. 16 May, 2018 1 commit
  9. 24 Jan, 2018 3 commits
  10. 04 Dec, 2017 1 commit
    • Jonas Ådahl's avatar
      monitor-manager: compare keys when checking whether a config is complete · b7afc0ac
      Jonas Ådahl authored
      We only counted configured monitors and whether the config was
      applicable (could be assigned), howeverwe didn't include disabled
      monitors when comparing. This could caused incorrect configurations to
      be applied when trying to use the previous configuration.
      
      One scenario where this happened was one a system with one laptop
      screen and one external monitor that was hot plugged some point after
      start up. When the laptop lid was closed, the 'previous configuration'
      being the configuration where only the laptop panel was enabled, passed
      'is-complete' check as the number of configured monitors were correct,
      and the configuration was applicable.
      
      Avoid this issue by simply comparing the configuration key of the
      previous configuration and the configuration key of the current state.
      This correctly identifies a laptop panel with the lid closed as
      inaccessible, thus doesn't incorrectly revert to the previous
      configuration.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=788915
      b7afc0ac
  11. 28 Nov, 2017 1 commit
  12. 05 Nov, 2017 1 commit
  13. 02 Oct, 2017 1 commit
  14. 29 Sep, 2017 3 commits
  15. 28 Sep, 2017 6 commits
  16. 21 Sep, 2017 1 commit
  17. 20 Sep, 2017 6 commits