tails issueshttps://gitlab.tails.boum.org/tails/tails/-/issues2024-03-28T23:28:32Zhttps://gitlab.tails.boum.org/tails/tails/-/issues/20310Missing "</div>" in support page2024-03-28T23:28:32ZjawlenskyMissing "</div>" in support pageIn 2ae56fef1f53dadd3f3c9f7e26708fc87b0278a7 a `</div>` tag was removed by mistake, causing problems in https://tails.net/support/index.en.html
The missing tag is [this one](https://gitlab.tails.boum.org/tails/tails/-/commit/2ae56fef1f53...In 2ae56fef1f53dadd3f3c9f7e26708fc87b0278a7 a `</div>` tag was removed by mistake, causing problems in https://tails.net/support/index.en.html
The missing tag is [this one](https://gitlab.tails.boum.org/tails/tails/-/commit/2ae56fef1f53dadd3f3c9f7e26708fc87b0278a7?page=5#6805556a7c6db4c70cd67f22c5cac9361eb09408_52_46).https://gitlab.tails.boum.org/tails/tails/-/issues/20309Ctrl+Alt+F1 displays the Welcome Screen2024-03-28T21:49:00Zsajolidasajolida@pimienta.orgCtrl+Alt+F1 displays the Welcome ScreenFrom wb:44826e00326dcede8c3855ab1a19e53c, I could reproduce this.
When I do Ctrl+Alt+F1 in Debian, I get the GDM login screen, but I don't think that's appropriate in the context of Tails.
Could we get a normal console instead?From wb:44826e00326dcede8c3855ab1a19e53c, I could reproduce this.
When I do Ctrl+Alt+F1 in Debian, I get the GDM login screen, but I don't think that's appropriate in the context of Tails.
Could we get a normal console instead?https://gitlab.tails.boum.org/tails/tails/-/issues/20308Ukrainian keyboard layout not shown as option in gnome config2024-03-28T21:56:03ZgroenteUkrainian keyboard layout not shown as option in gnome configThe greeter does allow to select Ukrainian keyboard layout and ``dconf write /org/gnome/desktop/input-sources/sources "[('xkb', 'ua')]"`` works fine, but it can't be found through gnome-control-center.The greeter does allow to select Ukrainian keyboard layout and ``dconf write /org/gnome/desktop/input-sources/sources "[('xkb', 'ua')]"`` works fine, but it can't be found through gnome-control-center.groentegroentehttps://gitlab.tails.boum.org/tails/tails/-/issues/20307KeePassXC does not clear clipboard in Tails 6.12024-03-28T21:03:59Zsajolidasajolida@pimienta.orgKeePassXC does not clear clipboard in Tails 6.1Reported in wb:11253ac207f68cbdbd610dc5c0b5b507, I could reproduce this in Tails 6.1.Reported in wb:11253ac207f68cbdbd610dc5c0b5b507, I could reproduce this in Tails 6.1.https://gitlab.tails.boum.org/tails/tails/-/issues/20306Consider disabling the spell checked in Text Editor2024-03-28T20:50:38Zsajolidasajolida@pimienta.orgConsider disabling the spell checked in Text EditorIn Tails 6.1, spell checking is enabled by default in Text Editor:
![Screenshot_from_2024-03-28_20-32-54](/uploads/1eaca62b7d9cf02670d1abd40c27ada2/Screenshot_from_2024-03-28_20-32-54.png)
As much as I love spell checkers, I wonder whe...In Tails 6.1, spell checking is enabled by default in Text Editor:
![Screenshot_from_2024-03-28_20-32-54](/uploads/1eaca62b7d9cf02670d1abd40c27ada2/Screenshot_from_2024-03-28_20-32-54.png)
As much as I love spell checkers, I wonder whether we should have it enabled by default.
It also tries to check spelling in code, though it doesn't underline that many words:
![Screenshot_from_2024-03-28_20-47-48](/uploads/38db03f11e8361981f2136e24556728e/Screenshot_from_2024-03-28_20-47-48.png)
When Tails is in another language, the spell checkers uses that language by default instead of English.
That said, we also have spell checking enabled in LibreOffice Writer and also matching the language of the session, so I'm not sure why we would have it in LibreOffice and not in Text Editor. Maybe because it's more likely to be used for non-human languages?https://gitlab.tails.boum.org/tails/tails/-/issues/20305Make pause() verbosely run pry in the caller's context2024-03-28T14:51:32ZanonymMake pause() verbosely run pry in the caller's contextSee !1471.See !1471.Tails_6.2anonymanonymhttps://gitlab.tails.boum.org/tails/tails/-/issues/20304Support redefining steps during a run for development purposes2024-03-28T14:49:37ZanonymSupport redefining steps during a run for development purposesSee tails!1470.See tails!1470.Tails_6.2anonymanonymhttps://gitlab.tails.boum.org/tails/tails/-/issues/20303Drop Screen#find()2024-03-28T14:48:41ZanonymDrop Screen#find()It currently is an alias for `wait(..., 10)` which is surprising, and made us use `wait(..., 0.5)` in `wait_vanish()` to work around this. It is used in some places as if it is a one-shot scan (which is what is desired in `wait_vanish()`...It currently is an alias for `wait(..., 10)` which is surprising, and made us use `wait(..., 0.5)` in `wait_vanish()` to work around this. It is used in some places as if it is a one-shot scan (which is what is desired in `wait_vanish()`), i.e. like `real_find()`. So let's just drop that silly `find()` and make `real_find()` the new `find()`.Tails_6.2anonymanonymhttps://gitlab.tails.boum.org/tails/tails/-/issues/20302wait_vanish does nothing2024-03-28T14:48:52Zanonymwait_vanish does nothingI have already fixed this (tails!1467), this issue is just for Sponsor11 tracking. It's best explained by the commit itself:
```
commit 3ec590aed35e84ac4e15f07fc4d3ea2671a4d8f9 (origin/make-find-not-wait, make-find-not-wait)
Author: ano...I have already fixed this (tails!1467), this issue is just for Sponsor11 tracking. It's best explained by the commit itself:
```
commit 3ec590aed35e84ac4e15f07fc4d3ea2671a4d8f9 (origin/make-find-not-wait, make-find-not-wait)
Author: anonym <anonym@riseup.net>
Date: Thu Mar 28 12:36:53 2024 +0100
Test suite: fix wait_vanish()
Since try_for() considers an iteration a success (and returns) as long
as the block returns something true-ish (i.e. everything but false and
nil) we used to return from the try_for() when finding a match, since
that becomes the block's return value and is true-ish, which is the
opposite of what we want.
We can observe this in this debug log where I temporarily enabled
debug logging (which we explicitly disable) for find() and try_for()
so we can see more clearly what happens:
Screen: waiting for TorBrowserStopButton.png to vanish
try_for: attempt 1 (0.01s elapsed of 120s)...
Screen: trying to find TorBrowserStopButton.png
Screen[match_screen]: taking screenshot
Screen[match_screen]: matching template to screenshot
OpenCV: starting opencv_match_template.py
Screen: found TorBrowserStopButton.png at (96, 97)
try_for: success!
Screen: TorBrowserStopButton.png has vanished
Whoops! So this method has been doing nothing except block execution
until it returns, which I guess has been enough in most cases it's
used, but this fix will probably fix some fragile tests.
```Tails_6.2anonymanonymhttps://gitlab.tails.boum.org/tails/tails/-/issues/20301failure in tails-create-iuk causes extremely large output to stderr2024-03-27T15:06:23Zgroentefailure in tails-create-iuk causes extremely large output to stderrIf you mistakenly switched python-xattr for python-pyxattr (and I assume other kinds of errors may also cause this behaviour), creating IUK's fails with an excessive barrage or error messages about read-only filesystems. So much that it ...If you mistakenly switched python-xattr for python-pyxattr (and I assume other kinds of errors may also cause this behaviour), creating IUK's fails with an excessive barrage or error messages about read-only filesystems. So much that it completely fills reasonable terminal buffers and makes it hard to figure out what actually caused the problem. For a command that's taking it's sweet time to run that's pretty annoying.
I'm not sure if this is easy to fix in the perl code (I assume there's some cleanup routine assuming squashfs mounts are already unmounted?). If not, we may want to change the release process documentation and add a tee catching stderr while doing the iuk creation, so at least you'll have a file where you can see the more useful error messaging at the beginning.intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/20300Release process document somewhat unclear on when to wait for manual testers2024-03-27T12:10:12ZgroenteRelease process document somewhat unclear on when to wait for manual testersThe release process documentation mentions triaging manual test results, ensuring tests are done in time, and adds checking the internal testing pad for feedback as sanity check before pushing to our master branch.
This implies finishing...The release process documentation mentions triaging manual test results, ensuring tests are done in time, and adds checking the internal testing pad for feedback as sanity check before pushing to our master branch.
This implies finishing the release is blocked on manual testing, but the documentation doesn't seem to treat the TR's work as a special case, whereas the TR documentation mentions they have 72 hours to complete their tests.
Let's make it more explicit in the documentation which tests are blockers and which ones aren't.groentegroentehttps://gitlab.tails.boum.org/tails/tails/-/issues/20299review research2024-03-28T10:56:25Zboyskareview researchTails_6.2boyskaboyskahttps://gitlab.tails.boum.org/tails/tails/-/issues/20298First round of research2024-03-26T16:21:47ZboyskaFirst round of researchroughly 3 hoursroughly 3 hoursTails_6.2segfaultsegfaulthttps://gitlab.tails.boum.org/tails/tails/-/issues/20297"The proxy server is refusing connections" after Tor has bootstrapped2024-03-28T08:09:32Zsegfault"The proxy server is refusing connections" after Tor has bootstrappedSometimes Tor Browser shows "The proxy server is refusing connections" after Tor has bootstrapped successfully.
The last journal entry with identifiers "Tor" or "tor" from test run [1]:
```
Mar 22 22:48:21 amnesia Tor[8620]: Bootstrapp...Sometimes Tor Browser shows "The proxy server is refusing connections" after Tor has bootstrapped successfully.
The last journal entry with identifiers "Tor" or "tor" from test run [1]:
```
Mar 22 22:48:21 amnesia Tor[8620]: Bootstrapped 100% (done): Done
[...]
Mar 22 22:48:37 amnesia onion-grater[4388]: 10.200.1.2:45186 (filter: tor-browser) connected: loaded filter: tor-browser
Mar 22 22:48:38 amnesia Tor[8620]: New control connection opened from 127.0.0.1.
```
I couldn't find anything else relevant in the journal.
Failed test suite runs:
* [1] https://jenkins.tails.boum.org/job/test_Tails_ISO_20277-extend-apparmor-regex/2//cucumber-html-reports/report-feature_35_1732831431.html ([screenshot](/uploads/4829e45d81d76f80944a6c280e663b51/03_36_59_The_Tor_Browser_directory_is_usable.png), [journal](/uploads/89376cbdbb0b3a06820b04c02f4dd560/03_36_59_The_Tor_Browser_directory_is_usable.journal), [debug.log](/uploads/f8a8ee81d09900c0b43204ae7ed56409/debug.log))
* https://jenkins.tails.boum.org/job/test_Tails_ISO_20277-extend-apparmor-regex/4//cucumber-html-reports/report-feature_35_1732831431.html ([screenshot](/uploads/77bc51126fe3a3f3ff3c0625470e0a2e/04_08_12_Persistent_browser_bookmarks.png), [journal](/uploads/2bd76d40b3a36a1c7b0936a215f82de3/04_08_12_Persistent_browser_bookmarks.journal), [debug.log](/uploads/107cfa8f6f8e704c1279b884508c2f83/debug.log))
I'm not sure if this only affects the test suite.Tails_6.2https://gitlab.tails.boum.org/tails/tails/-/issues/20294Make security audits easier to find in the website2024-03-28T17:11:38ZZen FuMake security audits easier to find in the websiteS11 includes a security audit to happen ["later in the year"](summit#166) (2024) which makes 2 "recent" audits counting the one conducted on [March 2023](https://tails.net/news/audit_by_ROS/index.en.html). If we keep posting them as news...S11 includes a security audit to happen ["later in the year"](summit#166) (2024) which makes 2 "recent" audits counting the one conducted on [March 2023](https://tails.net/news/audit_by_ROS/index.en.html). If we keep posting them as news, they'll "only" be found via the News page (or its archive after some time) or by searching.
Peryhaps we could make them easier to find (for example by having an Audit section or linking them somewhere that makes sense, etc).https://gitlab.tails.boum.org/tails/tails/-/issues/20292Workaround for ATI RV5162024-03-25T10:50:36ZboyskaWorkaround for ATI RV516A user reported us that, when using RV516
The system seems to boot OK. The problem is after a while I am finding that I am unable to operate the system.
> Problems
>
> 1)The mouse cursor (arrow) disappears entirely when on the deskt...A user reported us that, when using RV516
The system seems to boot OK. The problem is after a while I am finding that I am unable to operate the system.
> Problems
>
> 1)The mouse cursor (arrow) disappears entirely when on the desktop and only shows on the top Menu Bar
>
> 2) I get continuous mouse cursors (arrows) that fill up the screen as I move the mouse around and the mouse buttons stop working on the desktop although they do work on the top menu (this has been almost every time since you moved to version 6). Note: for both mouse issues, I tried moving the mouse to a different USB port but it didn't help.
>
> 3) Locations in Places menu have stop opening the appropriate program ie: Files when I click on them (I have to manually open a file manager from Applications to view files and folders). I have included a screen shot of this problem.
>
>
> My Solution (workaround)
>
> The only way I have found to get around these problems is restart Gnome and Wayland which I do in the following manner:
>
> 1) use Alt+F2 to bring up a run box and enter `killall -HUP gnome-shell`. This kills the existing non working session and applications.
>
> 2) In the new terminal screen I login as `amnesia` and use a admin password which I setup when starting tails ( I am not happy about setting up a admin password - for security reasons, but I don't know how to log in without one).
>
> 3) I restart Gnome and Wayland with the following command `gnome-shell --wayland`
But of course this leads them to a session which is different from the original.
Is there any way to "convert" this workaround into a more proper one that we might want to document?https://gitlab.tails.boum.org/tails/tails/-/issues/20291Mobile broadband not working anymore2024-03-25T14:24:22ZboyskaMobile broadband not working anymoreAccording to a user, mobile SIM cards used to work on 5.x, but are not working anymore on Tails 6.0.
> Now in 6.0 the broadband setup wizard is gone and saving the APN doesn't work, tails 20 times refuses to save it. On 21st time it sav...According to a user, mobile SIM cards used to work on 5.x, but are not working anymore on Tails 6.0.
> Now in 6.0 the broadband setup wizard is gone and saving the APN doesn't work, tails 20 times refuses to save it. On 21st time it saved it but then the LTE icon just starts to flicker and no connection is possible.
I kindly ask you to fix it. And please bring back the broadband wizard.intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/20290URLs in Tails Upgrader dialogs should be hyperlinks2024-03-25T11:22:53ZBen Westgatebenwestgate@protonmail.comURLs in Tails Upgrader dialogs should be hyperlinksI can't click these and copy and paste is extra work!
![image](/uploads/d4fa35269a7a593f9e7f7aa33cb5dc2b/image.png)
Line 523 & 526 here appear to be a culprit and may need tags to create a hyperlink.
https://gitlab.tails.boum.org/tails...I can't click these and copy and paste is extra work!
![image](/uploads/d4fa35269a7a593f9e7f7aa33cb5dc2b/image.png)
Line 523 & 526 here appear to be a culprit and may need tags to create a hyperlink.
https://gitlab.tails.boum.org/tails/tails/-/blob/stable/config/chroot_local-includes/usr/src/iuk/lib/Tails/IUK/Frontend.pmhttps://gitlab.tails.boum.org/tails/tails/-/issues/20288Incorrect CI recommendation: "Need to upgrade to a new APT snapshot: thunderb...2024-03-25T13:35:17ZsegfaultIncorrect CI recommendation: "Need to upgrade to a new APT snapshot: thunderbird (1:115.9.0-1~deb12u1) to Debian sid (1:115.9.0-1)"Noticed by the test suite in https://jenkins.tails.boum.org/job/test_Tails_ISO_20269-test-suite-robust-terminal-pasting/1//cucumber-html-reports/overview-failures.htmlNoticed by the test suite in https://jenkins.tails.boum.org/job/test_Tails_ISO_20269-test-suite-robust-terminal-pasting/1//cucumber-html-reports/overview-failures.htmlTails_6.2https://gitlab.tails.boum.org/tails/tails/-/issues/20287Ticket Gardening 2024Q22024-03-21T19:50:28ZZen FuTicket Gardening 2024Q2- Doc: https://tails.boum.org/contribute/working_together/roles/ticket_gardener/
- Last time: #20134+
Steps to complete:
* Manual tasks:
* [ ] Go through relevant GitLab views
* [ ] Identify and fix inadequate milestones
* [ ] Auto...- Doc: https://tails.boum.org/contribute/working_together/roles/ticket_gardener/
- Last time: #20134+
Steps to complete:
* Manual tasks:
* [ ] Go through relevant GitLab views
* [ ] Identify and fix inadequate milestones
* [ ] Automated tasks: Run ticket triage
* A few weeks after:
* [ ] Take a look at what happened since the issues were created; take a look at the issues/MRs linked from there, and whether they've already been on the list of problems during the last round(s) of triaging
* [ ] Report any problematic trend back to the relevant teams and to Management together, so they can coordinate with each other and handle the problem
* [ ] Close the issues
* [ ] Schedule next roundZen FuZen Fu