1. 18 Jun, 2020 2 commits
  2. 08 Jun, 2020 1 commit
  3. 04 Jun, 2020 3 commits
  4. 29 May, 2020 1 commit
  5. 27 May, 2020 3 commits
  6. 14 May, 2020 3 commits
  7. 13 May, 2020 1 commit
    • intrigeri's avatar
      Disable periodic APT operations (refs: #17278) · 575ae9eb
      intrigeri authored
      We have already masked apt-daily.timer (#12390), but apt-daily-upgrade.timer was
      left enabled. AFAICT it's a no-op by default, but better safe than sorry.
      
      Finally, drop masking of apt-daily.timer: APT::Periodic::Enable effectively
      makes apt-daily*.timer no-ops.
      575ae9eb
  8. 12 May, 2020 1 commit
  9. 20 Apr, 2020 1 commit
  10. 05 Apr, 2020 1 commit
  11. 03 Apr, 2020 2 commits
  12. 26 Mar, 2020 1 commit
    • intrigeri's avatar
      Switch Japanese input method from Anthy to Mozc (refs: #16719) · c56cd06b
      intrigeri authored
      A Japanese speaker (passis12345678) tells us that:
      
      "I don't think any Japanese users would agree that Anthy is better than Mozc.
      The accuracy of Mozy's Kanji conversion is clearly superior to that of Anthy.
      I’ve never seen or heard of anyone who likes Anthy.
      Any Japanese user would be happy to replace Anthy with Mozc."
      
      They also note that ibus-anthy has one advantage over ibus-mozc: it defaults to
      Japanese input, while ibus-mozc defaults to alphabetic and the user has to
      change the setting to Japanese every time they login. Despite that drawback,
      passis12345678 thinks that switching to Mozc is worth it anyway: it's
      a one-per-Tails-session annoyance, as opposed to a permanent annoyance while
      typing in Japanese.
      
      This would be fixed by fcitx-mozc (which defaults to Japanese), but switching to
      fcitx is another, much bigger matter: IBus seems to be much better integrated
      into GNOME than fcitx. Let's stick to IBus for now and try this minimal change.
      c56cd06b
  13. 21 Mar, 2020 1 commit
  14. 15 Mar, 2020 1 commit
  15. 09 Mar, 2020 1 commit
  16. 22 Feb, 2020 1 commit
  17. 21 Feb, 2020 2 commits
  18. 28 Jan, 2020 1 commit
    • intrigeri's avatar
      live-persist: don't backup empty configuration files (refs: #17112) · ee6ff8d1
      intrigeri authored
      In some cases, the previous code would overwrite a non-empty backup file with an
      empty one, making it harder to recover from the already painful #10976.
      
      For example, if the permissions get wrong and we run
      disable_and_create_empty_persistence_conf_file(), but the user does _not_
      immediately fix the problem, then next time they unlock their persistence,
      the (non-empty) backup gets overwritten by live-persist which replaces it with
      the new, empty config file it created during last boot.
      ee6ff8d1
  19. 23 Dec, 2019 1 commit
  20. 22 Dec, 2019 1 commit
  21. 18 Dec, 2019 1 commit
  22. 02 Dec, 2019 2 commits
    • segfault's avatar
      Fix database renaming prompt not working with KeePassXC (refs: #17212) · 4c60897e
      segfault authored
      KeePassXC creates "*.old.kdbx" backup files for each database file it
      saves, and our code to show a dialog asking to rename the database only
      opened the dialog if exactly one "*.kdbx" file is in the Persistent dir.
      
      This commit ignores the "*.old.kdbx" files when counting the kdbx files
      in the Persistent dir.
      4c60897e
    • segfault's avatar
      Fix wrong KeePassXC database opened · a01d7c64
      segfault authored
      If the user asked to open a specific database, we shouldn't change the
      target (in case the user clicks "Rename") or drop the argument
      entirely (in case the user clicks "Open").
      
      We now only open the renaming prompt if KeePassXC is opened without
      arguments.
      a01d7c64
  23. 27 Nov, 2019 1 commit
  24. 24 Nov, 2019 2 commits
  25. 23 Nov, 2019 2 commits
  26. 13 Nov, 2019 1 commit
  27. 10 Nov, 2019 1 commit
  28. 18 Oct, 2019 1 commit