1. 11 Oct, 2020 2 commits
  2. 06 Jul, 2020 14 commits
  3. 05 Jul, 2020 2 commits
  4. 26 Jun, 2020 1 commit
  5. 24 Jun, 2020 1 commit
  6. 18 Jun, 2020 4 commits
  7. 29 May, 2020 1 commit
  8. 15 May, 2020 1 commit
    • Adam Williamson's avatar
      Fix default keyboard layout / input source choice priority (#104) · d6323bec
      Adam Williamson authored
      This attempts to fix the problem I identified in #104 while also
      not breaking for the case where there is no system source and
      gnome_get_input_source_from_locale returns nothing. It should
      implement the intended logic fully:
      * If gnome-desktop gives us an input source, always preselect that
      * If gnome-desktop gives us a keyboard layout and there's no
        system sources, preselect the layout gnome-desktop gave us
      * If there is a system source and we didn't get an input source
        from gnome-desktop, preselect the system source
      Signed-off-by: default avatarAdam Williamson <awilliam@redhat.com>
      (cherry picked from commit 3096b533bc5d07a86a79748cdefbe62b96d556b3)
  9. 28 Apr, 2020 4 commits
  10. 25 Apr, 2020 1 commit
  11. 15 Apr, 2020 2 commits
    • Philip Withnall's avatar
      keyboard: Fix use of uninitialised variables if localed properties unset · ee2b4147
      Philip Withnall authored
      If localed returns a `NULL` list of sources, the code which was
      introduced in commit 07e24d6f would go ahead and dereference the `id`
      and `type` variables which hadn’t yet been set.
      From reading the comment in `preselect_input_source()`, it looks like
      the intention was to prefer the `system_sources` over the data returned
      by `gnome_get_input_source_from_locale()` — if both were set. The code
      didn’t properly handle the situation where either or both of them were
      unset, though.
      Signed-off-by: default avatarPhilip Withnall <withnall@endlessm.com>
      (cherry picked from commit e5563bcce1123e5d079b7d5969f3be4013af2815)
    • Philip Withnall's avatar
      keyboard: Nullify pointers if getting layout fails · 6c36fba5
      Philip Withnall authored
      It’s possible for `get_layout()` to fail if the wrong type is specified,
      in which case the `layout` and `variant` pointers will be left dangling.
      This might fix an occasional bug where the keyboard layout isn’t saved
      correctly and warnings are spewed to the console about
      g_variant_new_string: assertion 'g_utf8_validate (string, -1, NULL)' failed
      Or it might not. I haven’t been able to reproduce that bug.
      Signed-off-by: default avatarPhilip Withnall <withnall@endlessm.com>
      (cherry picked from commit 954e0b150f5abe9b921a4bfc03f7607910e3e905)
  12. 13 Apr, 2020 1 commit
    • Will Thompson's avatar
      po: Sort LINGUAS · 2f7ceb33
      Will Thompson authored
      This file is conventionally kept in lexicographic order.
      (cherry picked from commit cc86d02aea1d653e2e2bf5031748836a279d208d)
  13. 05 Apr, 2020 1 commit
  14. 02 Apr, 2020 5 commits