tails issueshttps://gitlab.tails.boum.org/tails/tails/-/issues2021-09-06T09:19:54Zhttps://gitlab.tails.boum.org/tails/tails/-/issues/18566Upgrade to Tor Browser 10.5.6 (78.14.0esr)2021-09-06T09:19:54ZanonymUpgrade to Tor Browser 10.5.6 (78.14.0esr)Tails_4.22anonymanonymhttps://gitlab.tails.boum.org/tails/tails/-/issues/18563News page isn't building correctly: includes raw Farsi PO news articles, whic...2021-09-06T07:23:16ZcbrownsteinNews page isn't building correctly: includes raw Farsi PO news articles, which should be excludedOur [News](https://tails.boum.org/news/) page isn't building correctly at the moment (Thu 02 Sep 2021 03:09:29 PM UTC).
@anonym suggested that the problem might be related to https://gitlab.tails.boum.org/tails/sysadmin/-/issues/6907.
...Our [News](https://tails.boum.org/news/) page isn't building correctly at the moment (Thu 02 Sep 2021 03:09:29 PM UTC).
@anonym suggested that the problem might be related to https://gitlab.tails.boum.org/tails/sysadmin/-/issues/6907.
FWIW, thinking that the problem might be resulting from the Farsi translations being disabled in 9f8222eedfe234999fe3db7b3ecef2749f831e11, I deleted all of the Farsi `.po` files in `/news/` before locally building our website. Deleting all of the Farsi `.po` files did indeed fix the problem for me.Tails_4.22intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/18562Don't restart tor after exiting the Unsafe Browser2021-08-31T09:15:41ZintrigeriDon't restart tor after exiting the Unsafe BrowserThe current rationale for restarting tor there is:
```
# Restart Tor if it's not working (a captive portal may have prevented
# Tor from bootstrapping, and a restart is the fastest way to get
# wheels turning)
```
I think t...The current rationale for restarting tor there is:
```
# Restart Tor if it's not working (a captive portal may have prevented
# Tor from bootstrapping, and a restart is the fastest way to get
# wheels turning)
```
I think that is:
- risky: any tor restart outside of _Tor Connection_'s control can cause trouble
- useless: after using the Unsafe Browser to connect to a captive portal, the user will supposedly retry connecting to Tor in _Tor Connection_
cc @anonym, @boyskaTails_4.22intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/18560Some Pidgin test suite scenarios fail when using XMPP accounts on a server th...2021-08-31T08:19:20ZintrigeriSome Pidgin test suite scenarios fail when using XMPP accounts on a server that requires going through the "Create New Room" UISee https://gitlab.tails.boum.org/tails/sysadmin/-/issues/17851#note_176158.
We should at least update `features/images/PidginCreateNewRoomPrompt.png` and then we'll see if we also have to update `PidginCreateNewRoomAcceptDefaultsButton...See https://gitlab.tails.boum.org/tails/sysadmin/-/issues/17851#note_176158.
We should at least update `features/images/PidginCreateNewRoomPrompt.png` and then we'll see if we also have to update `PidginCreateNewRoomAcceptDefaultsButton.png` (and who knows, perhaps the UI in current Pidgin has changed and this will require more work).Tails_4.22intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/18556Upgrade firmware-amd-graphics to 20210818-1+2021-09-06T14:52:56ZintrigeriUpgrade firmware-amd-graphics to 20210818-1+In 4.22~rc1 we upgraded to 20210427-1, which has a serious bug on various AMD GPUs: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992551
This was fixed 20210818-1.In 4.22~rc1 we upgraded to 20210427-1, which has a serious bug on various AMD GPUs: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992551
This was fixed 20210818-1.Tails_4.22intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/18551Only mention Persistent Storage in Unsafe Browser disabled warning if there i...2021-09-14T12:43:52ZintrigeriOnly mention Persistent Storage in Unsafe Browser disabled warning if there is oneThis is a finding from usability testing: 2 participants wanted to enable the Welcome Screen feature of the Persistent Storage without having one to avoid having to reboot.
Benefit = 2, cost = 1This is a finding from usability testing: 2 participants wanted to enable the Welcome Screen feature of the Persistent Storage without having one to avoid having to reboot.
Benefit = 2, cost = 1Tails_4.22segfaultsegfaulthttps://gitlab.tails.boum.org/tails/tails/-/issues/18550Only allow typing 1 bridge2022-06-28T10:48:11ZintrigeriOnly allow typing 1 bridgeThis is a finding from usability testing: 1 participant wondered whether they had to add a line between IP and fingerprint.
We should change the textarea to be a single line.
Benefit = 3, cost = 1This is a finding from usability testing: 1 participant wondered whether they had to add a line between IP and fingerprint.
We should change the textarea to be a single line.
Benefit = 3, cost = 1Tails_4.22intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/18540check_mirrors should have an option to report success, too2021-08-25T10:34:40Zboyskacheck_mirrors should have an option to report success, tooWhile doing release management, it is often needed to check the status of mirrors. In particular, before testing IUKs, "most" of them must be update. However, `./check-mirrors.rb --channel ${DIST:?} --allow-multiple --fast tails-amd64-${...While doing release management, it is often needed to check the status of mirrors. In particular, before testing IUKs, "most" of them must be update. However, `./check-mirrors.rb --channel ${DIST:?} --allow-multiple --fast tails-amd64-${VERSION:?}` (the command suggested in [the doc](https://tails.boum.org/contribute/release_process/)) isn't very useful, because it only reports errors.
As a release manager, I want to know the _ratio_ of mirrors that have the update.
Proposal: have an option to both report good mirrors and failed mirrors clearlyTails_4.22intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/18539Tor Connection: allow the user to retry from the error screen2021-08-30T08:28:32ZintrigeriTor Connection: allow the user to retry from the error screenLet's say we fail to connect to Tor due to an unstable Internet connection that went off briefly, then came back, like a satellite link or poor mobile Internet connectivity in the countryside. I land on the Tor Connection error screen.
...Let's say we fail to connect to Tor due to an unstable Internet connection that went off briefly, then came back, like a satellite link or poor mobile Internet connectivity in the countryside. I land on the Tor Connection error screen.
In this scenario, simply retrying with the same configuration will most likely be sufficient to fix the error.
But we don't allow users to easily do this, short of restarting Tails of course: currently, on the error screen, the "Connect" button is disabled by default, until the user goes to one of the sub-screens (clock, proxy, etc.) and comes back. (At least in some cases it then becomes enabled even if the user did not do any change in the sub-screen they visited, so in practice we already have a hidden, convoluted way to retry, but that's somewhat besides the point.)
Decreasing the "sign of life" timeout on !567, from 30s to 10s, will make things worse for these user scenarios: it will increase the chances that the Internet connectivity won't recover in time to give us "sign of life" before the timeout, so these users will land on the error page more often. [Depending on the exact timing, and whether the user configured bridges or not, the timeout that matters here can be either 30s vs. 10s, or 2×30s vs. 2×10s: in some of these situations we would fall back to the default bridges and succeed, in some situations we would not fallback, in some situations we would fall back and fail.]
IMO !567 is worth it anyway, because I believe the scenarios that regress are rare, while !567 improves UX significantly _for every boot_ in some user scenarios that seem more common and more important to our personas, such as using obfs4 East of UTC.
However, @boyska argued, and mostly convinced me, that if we do this change, then we should mitigate the impact of that regression, by making it easy for users who hit the regression to retry connecting to Tor with the exact same configuration.
Here's the design boyska proposed:
- The "Connect to Tor" button is always sensitive, as in: the user can click it and Tor Connection will try to connect.
- Until the user has visited one of the sub-screens, this button reads "Retry Connecting to Tor".
- Once the user has visited one of the sub-screens, this button reads "Connect to Tor".
I agree it is important to pay attention to the scenarios that !567 will make worse. I'm not sure this proposal is the best possible one but I mostly like it. The main drawback I see is that this encourages users to just retry, while I think most of them actually _need_ to fix something first. Also, I'm not a fan of a button changing labels (even if the action it triggers remains the same) but that's a minor thing I suppose.
cc @sajolidaTails_4.22intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/18538Investigate image size increase between 4.21 and 4.22~rc12021-08-29T10:15:08ZintrigeriInvestigate image size increase between 4.21 and 4.22~rc14.22~rc1 is 16 MiB larger than 4.21. How come?
Is this justified or explained by new stuff we don't need to ship?4.22~rc1 is 16 MiB larger than 4.21. How come?
Is this justified or explained by new stuff we don't need to ship?Tails_4.22intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/18533Cruft in reprepro custom APT suite2021-08-18T16:06:39ZintrigeriCruft in reprepro custom APT suite```
$ ssh reprepro@incoming.deb.tails.boum.org tails-merge-suite testing 4.22-rc1
Will not copy as not found: calendar-google-provider, cpio, cpio-win32, gconf, gconf2, gconf2-common, gconf2-dbgsym, gconf-defaults-service, gconf-defaults...```
$ ssh reprepro@incoming.deb.tails.boum.org tails-merge-suite testing 4.22-rc1
Will not copy as not found: calendar-google-provider, cpio, cpio-win32, gconf, gconf2, gconf2-common, gconf2-dbgsym, gconf-defaults-service, gconf-defaults-service-dbgsym, gconf-gsettings-backend, gconf-gsettings-backend-dbgsym, gconf-service, gconf-service-dbgsym, gdk-pixbuf, gir1.2-gconf-2.0, gir1.2-gdkpixbuf-2.0, gir1.2-gtk-2.0, gir1.2-mutter-3.0, gir1.2-networkmanager-1.0, glib2.0, gtk+2.0, gtk2.0-examples, gtk2-engines-pixbuf, hunspell, hunspell-tools, icedove, icedove-dbg, icedove-dev, icedove-l10n-all, icedove-l10n-ar, icedove-l10n-ast, icedove-l10n-be, icedove-l10n-bg, icedove-l10n-bn-bd, icedove-l10n-br, icedove-l10n-ca, icedove-l10n-cs, icedove-l10n-da, icedove-l10n-de, icedove-l10n-dsb, icedove-l10n-el, icedove-l10n-en-gb, icedove-l10n-es-ar, icedove-l10n-es-es, icedove-l10n-et, icedove-l10n-eu, icedove-l10n-fi, icedove-l10n-fr, icedove-l10n-fy-nl, icedove-l10n-ga-ie, icedove-l10n-gd, icedove-l10n-gl, icedove-l10n-he, icedove-l10n-hr, icedove-l10n-hsb, icedove-l10n-hu, icedove-l10n-hy-am, icedove-l10n-id, icedove-l10n-is, icedove-l10n-it, icedove-l10n-ja, icedove-l10n-kab, icedove-l10n-ko, icedove-l10n-lt, icedove-l10n-nb-no, icedove-l10n-nl, icedove-l10n-nn-no, icedove-l10n-pa-in, icedove-l10n-pl, icedove-l10n-pt-br, icedove-l10n-pt-pt, icedove-l10n-rm, icedove-l10n-ro, icedove-l10n-ru, icedove-l10n-si, icedove-l10n-sk, icedove-l10n-sl, icedove-l10n-sq, icedove-l10n-sr, icedove-l10n-sv-se, icedove-l10n-ta-lk, icedove-l10n-tr, icedove-l10n-uk, Exporting indices...
icedove-l10n-vi, icedove-l10n-zh-cn, icedove-l10n-zh-tw, iceowl-extension, iceowl-l10n-ar, iceowl-l10n-ast, iceowl-l10n-be, iceowl-l10n-bg, iceowl-l10n-bn-bd, iceowl-l10n-br, iceowl-l10n-ca, iceowl-l10n-cs, iceowl-l10n-cy, iceowl-l10n-da, iceowl-l10n-de, iceowl-l10n-dsb, iceowl-l10n-el, iceowl-l10n-en-gb, iceowl-l10n-es-ar, iceowl-l10n-es-es, iceowl-l10n-et, iceowl-l10n-eu, iceowl-l10n-fi, iceowl-l10n-fr, iceowl-l10n-fy-nl, iceowl-l10n-ga-ie, iceowl-l10n-gd, iceowl-l10n-gl, iceowl-l10n-he, iceowl-l10n-hr, iceowl-l10n-hsb, iceowl-l10n-hu, iceowl-l10n-hy-am, iceowl-l10n-id, iceowl-l10n-is, iceowl-l10n-it, iceowl-l10n-ja, iceowl-l10n-kab, iceowl-l10n-ko, iceowl-l10n-lt, iceowl-l10n-nb-no, iceowl-l10n-nl, iceowl-l10n-nn-no, iceowl-l10n-pa-in, iceowl-l10n-pl, iceowl-l10n-pt-br, iceowl-l10n-pt-pt, iceowl-l10n-rm, iceowl-l10n-ro, iceowl-l10n-ru, iceowl-l10n-si, iceowl-l10n-sk, iceowl-l10n-sl, iceowl-l10n-sq, iceowl-l10n-sr, iceowl-l10n-sv-se, iceowl-l10n-ta-lk, iceowl-l10n-tr, iceowl-l10n-uk, iceowl-l10n-vi, iceowl-l10n-zh-cn, iceowl-l10n-zh-tw, iceweasel-l10n-ach, iceweasel-l10n-af, iceweasel-l10n-ak, iceweasel-l10n-all, iceweasel-l10n-ar, iceweasel-l10n-as, iceweasel-l10n-ast, iceweasel-l10n-be, iceweasel-l10n-bg, iceweasel-l10n-bn-bd, iceweasel-l10n-bn-in, iceweasel-l10n-br, iceweasel-l10n-bs, iceweasel-l10n-ca, iceweasel-l10n-cs, iceweasel-l10n-csb, iceweasel-l10n-cy, iceweasel-l10n-da, iceweasel-l10n-de, iceweasel-l10n-el, iceweasel-l10n-en-gb, iceweasel-l10n-en-za, iceweasel-l10n-eo, iceweasel-l10n-es-ar, iceweasel-l10n-es-cl, iceweasel-l10n-es-es, iceweasel-l10n-es-mx, iceweasel-l10n-et, iceweasel-l10n-eu, iceweasel-l10n-fa, iceweasel-l10n-ff, iceweasel-l10n-fi, iceweasel-l10n-fr, iceweasel-l10n-fy-nl, iceweasel-l10n-ga-ie, iceweasel-l10n-gd, iceweasel-l10n-gl, iceweasel-l10n-gu-in, iceweasel-l10n-he, iceweasel-l10n-hi-in, iceweasel-l10n-hr, iceweasel-l10n-hu, iceweasel-l10n-hy-am, iceweasel-l10n-id, iceweasel-l10n-is, iceweasel-l10n-it, iceweasel-l10n-ja, iceweasel
-l10n-kk, iceweasel-l10n-km, iceweasel-l10n-kn, iceweasel-l10n-ko, iceweasel-l10n-ku, iceweasel-l10n-lg, iceweasel-l10n-lij, iceweasel-l10n-lt, iceweasel-l10n-lv, iceweasel-l10n-mai, iceweasel-l10n-mk, iceweasel-l10n-ml, iceweasel-l10n-mr, iceweasel-l10n-nb-no, iceweasel-l10n-nl, iceweasel-l10n-nn-no, iceweasel-l10n-nso, iceweasel-l10n-or, iceweasel-l10n-pa-in, iceweasel-l10n-pl, iceweasel-l10n-pt-br, iceweasel-l10n-pt-pt, iceweasel-l10n-rm, iceweasel-l10n-ro, iceweasel-l10n-ru, iceweasel-l10n-si, iceweasel-l10n-sk, iceweasel-l10n-sl, iceweasel-l10n-son, iceweasel-l10n-sq, iceweasel-l10n-sr, iceweasel-l10n-sv-se, iceweasel-l10n-ta, iceweasel-l10n-ta-lk, iceweasel-l10n-te, iceweasel-l10n-th, iceweasel-l10n-tr, iceweasel-l10n-uk, iceweasel-l10n-vi, iceweasel-l10n-zh-cn, iceweasel-l10n-zh-tw, iceweasel-l10n-zu, initramfs-tools, initramfs-tools-core, libgail18, libgail-common, libgail-dbg, libgail-dev, libgail-doc, libgconf-2-4, libgconf2-4, libgconf-2-4-dbgsym, libgconf2-dev, libgconf2-doc, libgdk-pixbuf2.0-0, libgdk-pixbuf2.0-0-dbgsym, libgdk-pixbuf2.0-common, libgdk-pixbuf2.0-dev, libgdk-pixbuf2.0-dev-dbgsym, libgdk-pixbuf2.0-doc, libglib2.0-0, libglib2.0-0-dbg, libglib2.0-bin, libglib2.0-data, libglib2.0-dev, libglib2.0-doc, libglib2.0-tests, libgtk2.0-0, libgtk2.0-0-dbg, libgtk2.0-bin, libgtk2.0-common, libgtk2.0-dev, libgtk2.0-doc, libhunspell-1.3-0, libhunspell-1.3-0-dbg, libhunspell-dev, libmutter0i, libmutter0i-dbgsym, libmutter-dev, libnm-glib4, libnm-glib-dev, libnm-glib-vpn1, libnm-glib-vpn-dev, libnm-util2, libnm-util-dev, lightning, lightning-l10n-ar, lightning-l10n-ast, lightning-l10n-be, lightning-l10n-bg, lightning-l10n-bn-bd, lightning-l10n-br, lightning-l10n-ca, lightning-l10n-cs, lightning-l10n-cy, lightning-l10n-da, lightning-l10n-de, lightning-l10n-dsb, lightning-l10n-el, lightning-l10n-en-gb, lightning-l10n-es-ar, lightning-l10n-es-es, lightning-l10n-et, lightning-l10n-eu, lightning-l10n-fi, lightning-l10n-fr, lightning-l10n-fy-nl, lightning-l10n-
ga-ie, lightning-l10n-gd, lightning-l10n-gl, lightning-l10n-he, lightning-l10n-hr, lightning-l10n-hsb, lightning-l10n-hu, lightning-l10n-hy-am, lightning-l10n-id, lightning-l10n-is, lightning-l10n-it, lightning-l10n-ja, lightning-l10n-kab, lightning-l10n-ko, lightning-l10n-lt, lightning-l10n-nb-no, lightning-l10n-nl, lightning-l10n-nn-no, lightning-l10n-pa-in, lightning-l10n-pl, lightning-l10n-pt-br, lightning-l10n-pt-pt, lightning-l10n-rm, lightning-l10n-ro, lightning-l10n-ru, lightning-l10n-si, lightning-l10n-sk, lightning-l10n-sl, lightning-l10n-sq, lightning-l10n-sr, lightning-l10n-sv-se, lightning-l10n-ta-lk, lightning-l10n-tr, lightning-l10n-uk, lightning-l10n-vi, lightning-l10n-zh-cn, lightning-l10n-zh-tw, linux-image-amd64, mutter, mutter-common, mutter-dbgsym, tails-greeter, thunderbird, thunderbird-dbg, thunderbird-dev, thunderbird-l10n-all, thunderbird-l10n-ar, thunderbird-l10n-ast, thunderbird-l10n-be, thunderbird-l10n-bg, thunderbird-l10n-bn-bd, thunderbird-l10n-br, thunderbird-l10n-ca, thunderbird-l10n-cs, thunderbird-l10n-da, thunderbird-l10n-de, thunderbird-l10n-dsb, thunderbird-l10n-el, thunderbird-l10n-en-gb, thunderbird-l10n-es-ar, thunderbird-l10n-es-es, thunderbird-l10n-et, thunderbird-l10n-eu, thunderbird-l10n-fi, thunderbird-l10n-fr, thunderbird-l10n-fy-nl, thunderbird-l10n-ga-ie, thunderbird-l10n-gd, thunderbird-l10n-gl, thunderbird-l10n-he, thunderbird-l10n-hr, thunderbird-l10n-hsb, thunderbird-l10n-hu, thunderbird-l10n-hy-am, thunderbird-l10n-id, thunderbird-l10n-is, thunderbird-l10n-it, thunderbird-l10n-ja, thunderbird-l10n-kab, thunderbird-l10n-ko, thunderbird-l10n-lt, thunderbird-l10n-nb-no, thunderbird-l10n-nl, thunderbird-l10n-nn-no, thunderbird-l10n-pa-in, thunderbird-l10n-pl, thunderbird-l10n-pt-br, thunderbird-l10n-pt-pt, thunderbird-l10n-rm, thunderbird-l10n-ro, thunderbird-l10n-ru, thunderbird-l10n-si, thunderbird-l10n-sk, thunderbird-l10n-sl, thunderbird-l10n-sq, thunderbird-l10n-sr, thunderbird-l10n-sv-se, thunderbird-l10n-ta-lk
, thunderbird-l10n-tr, thunderbird-l10n-uk, thunderbird-l10n-vi, thunderbird-l10n-zh-cn, thunderbird-l10n-zh-tw, whisperback, zenity, zenity-common.
```Tails_4.22intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/18532Problems connecting to Tor when Wi-Fi network settings are saved in Persisten...2021-09-07T08:51:35ZcbrownsteinProblems connecting to Tor when Wi-Fi network settings are saved in Persistent StorageSeveral users (and I believe @emmapeel also) have reported problems connecting to Tor when the Wi-Fi network settings are saved in Persistent Storage:
* In WB report 28d6a28a6618942947e48ee72263e957, the user reports that with Persisten...Several users (and I believe @emmapeel also) have reported problems connecting to Tor when the Wi-Fi network settings are saved in Persistent Storage:
* In WB report 28d6a28a6618942947e48ee72263e957, the user reports that with Persistent Storage enabled, TCA freezes.
* In WB report af0cfe9ce0d601f3ce0b16e9c8302fc, the user reports that with Persistent Storage enabled, "the tor connection wizard skips the loading page and doesnt connect to tor."
* In WB report b27ab0883dc7392f83978f9a38e4954e, the user reports that "If 'persistent' configured, Tor reset is not permitted."
* In WB report 835e30d4dea532553fd2c3b581ee13f4, the user reports that "Tor does not connect if wifi network information is saved in persistent volume." The user provides the following steps to reproduce the problem:
> Save wifi network information in persistent volume
> Start Tails using persistent volume
> Tor "onion" appears immediately in menu bar, but Tor will not connect
> Tor connects normally if persistent volume not used, if network
> information not saved in persistent volume, or if wired (dhcp)
> connection used instead of wifi
I tried but was unable to reproduce any problems connecting to Tor with Persistent Storage enabled and my Wi-Fi network settings saved.Tails_4.22intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/18531"Select Target USB" dropdown freezes in Tails Installer2022-03-16T08:17:33ZJack B"Select Target USB" dropdown freezes in Tails InstallerSince 4.21, the "Select Target USB" dropdown in Tails Installer freezes after selecting a downloaded iso image. This issue probably started after the [#18494](https://gitlab.tails.boum.org/tails/tails/-/issues/18494) fix.Since 4.21, the "Select Target USB" dropdown in Tails Installer freezes after selecting a downloaded iso image. This issue probably started after the [#18494](https://gitlab.tails.boum.org/tails/tails/-/issues/18494) fix.Tails_4.22toustoushttps://gitlab.tails.boum.org/tails/tails/-/issues/18526Write release notes for 4.222021-08-17T17:26:05ZboyskaWrite release notes for 4.22Tails_4.22https://gitlab.tails.boum.org/tails/tails/-/issues/18525Write release notes for 4.22~rc12021-08-19T10:42:37ZboyskaWrite release notes for 4.22~rc1Tails_4.22cbrownsteincbrownstein2021-08-18https://gitlab.tails.boum.org/tails/tails/-/issues/18516tails::profile::rss2email and tails::meeting squat users' UIDs and GIDs2021-08-11T08:35:32Zintrigeritails::profile::rss2email and tails::meeting squat users' UIDs and GIDsThese 2 classes create users with a UID and GID in the 1000+ range, which is reserved for human users.
As a consequence, on `misc.lizard` our Puppet code fails to create boyska's user and group, which blocks me from completing his onboa...These 2 classes create users with a UID and GID in the 1000+ range, which is reserved for human users.
As a consequence, on `misc.lizard` our Puppet code fails to create boyska's user and group, which blocks me from completing his onboarding on the RM team (to be done by August 17).
Please:
- adjust these classes so they manage system users and groups, with UID and GID < 100; this may require switching from `user::managed` to `user` and `group` with `system => true`
- move the already existing users and groups managed by these classes to their new UIDs and GIDs
Thanks in advance!Tails_4.22Zen FuZen Fu2021-08-17https://gitlab.tails.boum.org/tails/tails/-/issues/18513./refresh-translations is broken on the devel branch2021-08-10T08:56:00Zintrigeri./refresh-translations is broken on the devel branch`no element found at line 1, column 0, byte 0 at /usr/lib/x86_64-linux-gnu/perl5/5.32/XML/Parser.pm line 187.`
`config/chroot_local-includes/usr/share/tails/tca/main.ui.in` is emptied.`no element found at line 1, column 0, byte 0 at /usr/lib/x86_64-linux-gnu/perl5/5.32/XML/Parser.pm line 187.`
`config/chroot_local-includes/usr/share/tails/tca/main.ui.in` is emptied.Tails_4.22intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/18507"TCA can reconnect after a connection failure" scenario fails: tca.conf parsi...2021-08-16T07:01:04Zintrigeri"TCA can reconnect after a connection failure" scenario fails: tca.conf parsing errorThat's on the devel branch.
See e.g. https://jenkins.tails.boum.org/view/RM/job/test_Tails_ISO_devel/2385/cucumber-html-reports/report-feature_3_1399846743.html.
I suppose I introduced this regression so I'll take a look, but I'm surpr...That's on the devel branch.
See e.g. https://jenkins.tails.boum.org/view/RM/job/test_Tails_ISO_devel/2385/cucumber-html-reports/report-feature_3_1399846743.html.
I suppose I introduced this regression so I'll take a look, but I'm surprised because I don't remember seeing it on the test suite runs of my recently merged MRs.
cc @boyska, so you're aware of it when you analyze test suite results for branches based on devel.Tails_4.22intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/18502Remove tordate2021-08-12T09:54:21ZintrigeriRemove tordateTails_4.22boyskaboyskahttps://gitlab.tails.boum.org/tails/tails/-/issues/18501Improve the timeout logic of Tor Connection2021-09-07T09:48:07Zsajolidasajolida@pimienta.orgImprove the timeout logic of Tor ConnectionTracking here bits of discussion from https://gitlab.tails.boum.org/tails/tails/-/issues/18470. My technical summary might be totally flawed, but I want a place to track this.
If I understand correctly, right now the timeout logic of TC...Tracking here bits of discussion from https://gitlab.tails.boum.org/tails/tails/-/issues/18470. My technical summary might be totally flawed, but I want a place to track this.
If I understand correctly, right now the timeout logic of TCA makes it so that the error screen could be returned on very slow networks even if connecting to Tor is possible.
Ideally, we should have a shorter timeout when "nothing happened" and a longer timeout when "something happens but it's slow". It would improve UX for both people on slow networks (prevent false negatives) and people on fast networks (get faster errors when nothing happens).
I understand that we currently don't make a different between "nothing happened" and "something happens but it's slow", otherwise we shouldn't fallback on an error so quickly when it's still possible to connect to Tor. This might not be possible to improve right now and might require some work at Tor.
I might be totally mistaken and need an update from @boyska on how the timeout currently works.
**Blocked by** #18539Tails_4.22intrigeriintrigeri