1. 14 Sep, 2019 7 commits
  2. 09 Sep, 2019 1 commit
  3. 08 Sep, 2019 2 commits
  4. 07 Sep, 2019 1 commit
    • intrigeri's avatar
      Add GNOME bookmarks earlier in the session login process (refs: #17030) · a0ba13e1
      intrigeri authored
      commit 9efaffaf moved this unit to
      desktop.target, which has an unfortunate side-effect: the places-menu GNOME
      Shell extension has already loaded, and thus the bookmarks we're adding won't
      appear in the Places menu.
      
      So let's start this unit earlier, as part of gnome-early-initialization.target,
      that is during X-GNOME-Autostart-Phase=EarlyInitialization.
      a0ba13e1
  5. 02 Sep, 2019 2 commits
  6. 31 Aug, 2019 5 commits
    • intrigeri's avatar
      Improve comments. · edc71c6f
      intrigeri authored
      I.e. integrate as code comments all the relevant explanations
      that were in commit messages, in the previous non-squashed branch
      for refs: #12092.
      edc71c6f
    • segfault's avatar
    • intrigeri's avatar
      Fix unlocking the screen. · 6c8cd784
      intrigeri authored
      6c8cd784
    • intrigeri's avatar
    • intrigeri's avatar
      Terminate GDM's GNOME session after the amnesia user logs in, in order to free... · 9e6df451
      intrigeri authored
      Terminate GDM's GNOME session after the amnesia user logs in, in order to free memory (refs: #12092)
      
      I've heard rumors that we can drop this hack when we switch to Wayland (#12213).
      We'll see :)
      
      We kill it as part of desktop.target, i.e. during the "Applications" phase of
      the initialization of the GNOME session. We cannot do this earlier reliably:
      
       - basic.target is started by "systemd --user" for almost every command run as
         the amnesia user and may thus be triggered too early, at a time when we still
         need GDM's processes.
      
       - If we do this as part of basic.target, it sometimes happens before amnesia's
         X.Org has started, and sometimes after that, which causes racy behaviour,
         weird bugs, and amnesia's $DISPLAY can be either :0 or :1, which breaks our
         code that relies on that value to be always the same.
      
      We're in no rush to kill GDM's GNOME session super early anyway.
      
      Note that we keep GDM running while we kill its GNOME session,
      otherwise, the amnesia user can't unlock the screen:
      
        Fai...
      9e6df451
  7. 26 Aug, 2019 1 commit
  8. 25 Aug, 2019 2 commits
  9. 23 Aug, 2019 2 commits
    • intrigeri's avatar
    • intrigeri's avatar
      tails-unblock-network: only sleep until all-net-blacklist.conf is gone (refs: #16805) · 1527d3c0
      intrigeri authored
      Sleeping 5 seconds unconditionally harms UX.
      
      The assumption here is that:
      
       - #9012 was caused by an aufs bug that somehow affects how udev (and the
         kernel?) monitor /etc/modprobe.d/, and make them need time until they notice
         that all-net-blacklist.conf was deleted.
      
       - The same bug would also affect the "-e" test done by the shell this script
         runs under. That is, it would affect essentially any process that accesses
         /etc/modprobe.d/.
      
       - So for example, this bug can't be "the inode number of /etc/modprobe.d
         changed between the time udev started monitoring it, and the time we trigger
         a replay of the kernel 'add' events". According to the aufs documentation,
         inode numbers can change when using the noxino mount option, which we do,
         and actually that's been one of my primary suspects when investigating
         #9012.
      1527d3c0
  10. 19 Aug, 2019 2 commits
    • intrigeri's avatar
      Test suite: install Dogtail from Bullseye and run it with Python 3 (refs: #16976) · 2ded9055
      intrigeri authored
      This will give us UTF-8 support.
      
      Note the switch from raw bytes IO to StringIO: the equivalent of what we used to
      do in Python 3 is io.BytesIO(), but that won't work out of the box: the code
      we're running prints strings on stdout/stderr, not bytes, and Python 3 knows
      the difference. So accordingly, remove decoding of the output, since we get
      a string already.
      
      Drop anonym's "showingOnly" patch that was merged upstream :)
      2ded9055
    • intrigeri's avatar
      Remote shell: print traceback to stderr so we can see it. · 05d75e85
      intrigeri authored
      Otherwise, it gets lost (or at least I could not find it).
      In any case, it does not make sense to print "The error was:"
      somewhere and the actual error elsewhere.
      05d75e85
  11. 16 Aug, 2019 1 commit
  12. 14 Aug, 2019 1 commit
  13. 11 Aug, 2019 3 commits
  14. 10 Aug, 2019 7 commits
  15. 08 Aug, 2019 2 commits
  16. 07 Aug, 2019 1 commit