tails issueshttps://gitlab.tails.boum.org/tails/tails/-/issues2024-03-26T08:58:11Zhttps://gitlab.tails.boum.org/tails/tails/-/issues/20019Design and implement new criterion for listing languages in the Welcome Screen2024-03-26T08:58:11ZintrigeriDesign and implement new criterion for listing languages in the Welcome ScreenIn #16095+ we started listing only tier-1 languages + those that have reviewed translations in Transifex.
Then, when Tor migrated from Transifex to Hosted Weblate, we lost trivial access to (only) the reviewed strings via Git. So tempor...In #16095+ we started listing only tier-1 languages + those that have reviewed translations in Transifex.
Then, when Tor migrated from Transifex to Hosted Weblate, we lost trivial access to (only) the reviewed strings via Git. So temporarily, in !1000 we had to switch to a hard-coded list of languages, which is not great: it's going to bitrot and we're end up offering languages that are not well translated, and not offering languages that are well translated, which defeats the original goal of #16095.
Meanwhile we also realized on #19359 that it would not make sense to go back to pulling only reviewed translation strings, and it's OK to pull all translations.
But if we just switch to importing everything from Hosted Weblate via Git, we end up with 76 languages, many of them with a very low translation rate, which again defeats the goal of #16095.
So, what would be a good criterion for listing languages in the Welcome Screen, based on the data we import from https://gitlab.torproject.org/tpo/translation/-/tree/tails-misc?ref_type=heads?
intrigeri will do the initial data gathering e.g. X% → this set of languages. Not high priority, still worth a few hours of intri-time to ensure we can update our currently-temporarily-hard-coded list of languages listed in the Welcome Screen.
# Tasks
- [x] Design
- [x] Decide where we set the bar
- [ ] ImplementTails_6.2intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/15451Provide fsck from Welcome Screen when the file system of the Persistent Stora...2024-03-27T19:12:36ZGhost UserProvide fsck from Welcome Screen when the file system of the Persistent Storage is corrupted[[_TOC_]]
# New Persistent Storage
In the Welcome Screen, we fail to activate the Persistent Storage. I don't know if we freeze, but some users think they have lost their data, while it could be that a `fsck` operation would fix it.
W...[[_TOC_]]
# New Persistent Storage
In the Welcome Screen, we fail to activate the Persistent Storage. I don't know if we freeze, but some users think they have lost their data, while it could be that a `fsck` operation would fix it.
WhisperBack reports which show this problem:
* ed58ea093d6fda6d6175449e30b11b95
* 6db8ba7f10e5c055574f6793ced1ebcc
* c3e724b6d6a7c6eacc394b512c58a9e3
* 7b16f32e2d50ee33cfb33aa5b94db434
# Plan
* [x] Phase 0: automatically run `e2fsck -f -p`, log its result and continue in any case (!1351)
* [ ] Phase 1.A: Depending on the exit code of `e2fsck -f -p`:
* 0, 1: continue mounting
* 2: "system should be rebooted" → should never happen in our context (only makes sense when checking the root filesystem)
* 4: so we have "File system errors left uncorrected". We could try mounting anyway but we're (almost?) certain it'll fail since fsck marked the filesystem as unclean. This is the situation when a more forceful repair (`fsck -y` or the same via GNOME Disks) is necessary and generally sufficient.
* others: indicates a bug somewhere, so probably an error message and then try continue to unlock
* [ ] Phase 1.B: Detect buggy hardware (#5856)
* [ ] Phase 2: Automate `fsck -y` when `fsck -p` was not enough
Phase 1.A and 1.B could happen independently.
# Tips
## Corrupted filesystem that `e2fsck -p -f` *can* fix
Corrupt filesystem:
```
rm -rf /live/persistence/TailsData_unlocked/lost+found
```
## Corrupted filesystem that `e2fsck -p -f` *cannot* fix but `e2fsck -y -f` can.
Corrupt filesystem:
```
dd if=/dev/zero of=/dev/mapper/TailsData_unlocked bs=1k seek=10 count=4k
```
# Old Persistent Storage
_Originally created by @eugene__k on [#15451 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15451)_
If the user attempts to mount the persistent filesystem from the greeter
UI and it happens to be corrupted, the attempting-to-mount animation
never goes away, and the “Start Tails” button stops working. There are
no errors and it is not apparent to the user why it’s stuck. After that,
the user has no choice but to to hard-reboot the system since the OS
won’t load.
I’ve seen this happen on two separate occasions, probably because the OS
was not properly flushing its caches on shutdown (which may be a
separate issue) or because the thumb drive was somehow malfunctioning.
In both cases, after I rebooted and logged in without mounting
persistent storage up front, I could unlock the partition using the
“Disks” app with no errors, but the underlying partition was displayed
as “Unknown” (rather than “ext4”) and I had to run fsck to repair it.
Instead of freezing, the UI should attempt to unlock the filesystem and,
if the filesystem is unlocked but can’t be mounted, display an error
advising the user that the filesystem may be corrupted.Tails_6.2segfaultsegfaulthttps://gitlab.tails.boum.org/tails/tails/-/issues/20253Power off button in the user menu of the Welcome Screen does not work in 6.02024-03-27T01:09:00ZintrigeriPower off button in the user menu of the Welcome Screen does not work in 6.0Reported in wb:9166e7bf9b8975b0599328185aaefae3. It's not a huge deal because the **Shutdown** button in the Welcome Screen window works, but still, it feels unpolished.
I doubt that's worth spending any non-trivial developer time on, s...Reported in wb:9166e7bf9b8975b0599328185aaefae3. It's not a huge deal because the **Shutdown** button in the Welcome Screen window works, but still, it feels unpolished.
I doubt that's worth spending any non-trivial developer time on, so not flagging for FT, but maybe @sajolida thinks differently :)https://gitlab.tails.boum.org/tails/tails/-/issues/20231Changing locale in the Welcome Screen doesn't change it for Accessibility menu2024-02-27T14:50:37ZboyskaChanging locale in the Welcome Screen doesn't change it for Accessibility menu... nor for the date widget or anything else, actually
<img src="/uploads/a181fd8a8fac4534956b479677a7474c/Screenshot_tails-amd64-6.0_2024-02-27_12_49_58.png" width="300px" />... nor for the date widget or anything else, actually
<img src="/uploads/a181fd8a8fac4534956b479677a7474c/Screenshot_tails-amd64-6.0_2024-02-27_12_49_58.png" width="300px" />https://gitlab.tails.boum.org/tails/tails/-/issues/20226syntax error in gdm-shell-tails.desktop2024-02-29T09:58:17Zboyskasyntax error in gdm-shell-tails.desktopI found these errors in the journal. I don't know how serious is that, but maybe we should investigate?
```
gdm-shell-tails.desktop[4953]: syntax error: line 1 of stdin
gdm-shell-tails.desktop[4953]: Errors encountered in stdin; not com...I found these errors in the journal. I don't know how serious is that, but maybe we should investigate?
```
gdm-shell-tails.desktop[4953]: syntax error: line 1 of stdin
gdm-shell-tails.desktop[4953]: Errors encountered in stdin; not compiled
```https://gitlab.tails.boum.org/tails/tails/-/issues/20102Detect and notify if there is no supported keyboard or mouse2024-01-11T18:57:09Zsajolidasajolida@pimienta.orgDetect and notify if there is no supported keyboard or mouseSometimes, the keyboard or the mouse doesn't work. This is pretty common on Apple hardware, but seems to happen on PC as well sometimes (eg. ASUS Vivobook GO14).
Could we detect when there is no keyboard or mouse and notify the use in t...Sometimes, the keyboard or the mouse doesn't work. This is pretty common on Apple hardware, but seems to happen on PC as well sometimes (eg. ASUS Vivobook GO14).
Could we detect when there is no keyboard or mouse and notify the use in the Welcome Screen?https://gitlab.tails.boum.org/tails/tails/-/issues/19907Orca doesn't change language while in the Welcome Screen2024-02-27T12:35:37Zsajolidasajolida@pimienta.orgOrca doesn't change language while in the Welcome ScreenIf I activate the screen reader in the Welcome Screen and change the language to "Spanish", for example, Orca reads Spanish text with an English voice, which is not really understandable. Orca reads Spanish fine with a Spanish voice once...If I activate the screen reader in the Welcome Screen and change the language to "Spanish", for example, Orca reads Spanish text with an English voice, which is not really understandable. Orca reads Spanish fine with a Spanish voice once on the GNOME desktop.https://gitlab.tails.boum.org/tails/tails/-/issues/19906Sound indication when getting to the Welcome Screen2024-02-26T10:56:38Zsajolidasajolida@pimienta.orgSound indication when getting to the Welcome ScreenFrom #18989:
We recommend to offer a sound indication (music or beat sound) to let users know that the operative system is fully loaded and ready to use.
If this works correctly, this may be a solution for blind users to being able to i...From #18989:
We recommend to offer a sound indication (music or beat sound) to let users know that the operative system is fully loaded and ready to use.
If this works correctly, this may be a solution for blind users to being able to install independently if they know the shortcut to start the screen reader.
We probably don't want to "sound like Tails" not to raise too much attention, but a simple and neutral *beep* could help. For example, /usr/share/sounds/gnome/default/alerts/drip.ogg.
I guess that the same reasoning should apply to the Boot Menu: could we play a system beep when GRUB loads to reassure blind users that Tails is loading?https://gitlab.tails.boum.org/tails/tails/-/issues/19905Settings on the Welcome Screen are not read by Orca2023-07-20T22:38:30Zsajolidasajolida@pimienta.orgSettings on the Welcome Screen are not read by OrcaFrom #18989:
When navigation with the keyboard only, Orca reads the name of the settings (eg. "Language") but not its current value (eg. "English").
Both should be read to offer a screen reader confirmation of about the current setup.
...From #18989:
When navigation with the keyboard only, Orca reads the name of the settings (eg. "Language") but not its current value (eg. "English").
Both should be read to offer a screen reader confirmation of about the current setup.
This applies to both the *Language & Region* settings and the additional settings.https://gitlab.tails.boum.org/tails/tails/-/issues/19868Welcome Screen: pressing enter is not intuitive for child languages2023-06-28T13:01:06ZboyskaWelcome Screen: pressing enter is not intuitive for child languages!1176 was merged, but a small glitch is still there:
- [ ] @boyska started a [discussion](https://gitlab.tails.boum.org/tails/tails/-/merge_requests/1176#note_213038): (+1 comment)
> filtering works well. however, pressing enter a...!1176 was merged, but a small glitch is still there:
- [ ] @boyska started a [discussion](https://gitlab.tails.boum.org/tails/tails/-/merge_requests/1176#note_213038): (+1 comment)
> filtering works well. however, pressing enter after filtering is misleading.
>
> As an example, I typed "swit fr" which filters down to *French - Switzerland*. If I now press Enter, it selects *French - France*, which is clearly not what I wanted.https://gitlab.tails.boum.org/tails/tails/-/issues/19469Need to press Enter twice to log in2023-08-11T13:31:35ZintrigeriNeed to press Enter twice to log inSince a few weeks or months, most (?) of the time pressing Enter in the Welcome Screen yields no visible effect. Pressing it again logs in. Is it only me?Since a few weeks or months, most (?) of the time pressing Enter in the Welcome Screen yields no visible effect. Pressing it again logs in. Is it only me?https://gitlab.tails.boum.org/tails/tails/-/issues/19319Instruct about the possibility of creating a Persistent Storage: UX when boot...2023-05-09T13:05:21ZintrigeriInstruct about the possibility of creating a Persistent Storage: UX when booting from ISOThe initial implementation of #15586+ does not pay attention to whether the user can actually create a Persistent Storage or not: we display the same UI in the *Welcome Screen* when booting from ISO/DVD as when booting from a USB stick.
...The initial implementation of #15586+ does not pay attention to whether the user can actually create a Persistent Storage or not: we display the same UI in the *Welcome Screen* when booting from ISO/DVD as when booting from a USB stick.
The status quo (i.e. what I expect we'll ship in Tails 5.8), when starting from ISO/DVD, is that I can click the *Create Persistent Storage* button in the *Welcome Screen*; then, once in the GNOME session, the *Persistent Storage* app appears and tells me "Unfortunately, this Tails device does not support creating a Persistent Storage".
I suppose that ideally, when booting from ISO/DVD, in the *Welcome Screen* we should:
- at least, *not* display the *Create Persistent Storage* button
- maybe let the user know that if they were using a USB stick, they could benefit from the Persistent Storage?
cc @sajolida and @boyskahttps://gitlab.tails.boum.org/tails/tails/-/issues/19286Tell what Persistent Storage feature failed to activate on the Welcome Screen2023-02-13T14:43:31Zsajolidasajolida@pimienta.orgTell what Persistent Storage feature failed to activate on the Welcome Screen# To do
When we fail to activate a feature of the Persistent Storage in the Welcome Screen, tell the user what feature failed:
`Failed to activate some features of the Persistent Storage: Dotfiles. Please start Tails and send an error ...# To do
When we fail to activate a feature of the Persistent Storage in the Welcome Screen, tell the user what feature failed:
`Failed to activate some features of the Persistent Storage: Dotfiles. Please start Tails and send an error report.`
# Original report
While dogfooding Tails 5.8~beta1, I got the following error message on the Welcome Screen:
Failed to activate the Persistent Storage . Please start Tails and send an error report.
But my Persistent Storage seems to be mounted fine.
See wb:b61b93bf1db5faf447ecd51ddd14860 for details.
A user reported this situation as "alarming", I think because of the inconsistency between "Failed to activate" while still having access. It didn't really failed to activate.https://gitlab.tails.boum.org/tails/tails/-/issues/18156Allow saving accessibility options from the Welcome Screen2024-02-27T12:35:36Zsajolidasajolida@pimienta.orgAllow saving accessibility options from the Welcome ScreenSplitting this out of #5501.Splitting this out of #5501.https://gitlab.tails.boum.org/tails/tails/-/issues/18149Split the Welcome Screen into 2 when running from a USB stick2023-01-15T23:20:25Zsajolidasajolida@pimienta.orgSplit the Welcome Screen into 2 when running from a USB stick![welcome_-_discovery](/uploads/cc0797ee48a997254761322b3b451f9b/welcome_-_discovery.png)
![welcome_-_review](/uploads/db12d15cbaac926aa84e946ec76adedb/welcome_-_review.png)
We had something like this before the redesign of the Welcome...![welcome_-_discovery](/uploads/cc0797ee48a997254761322b3b451f9b/welcome_-_discovery.png)
![welcome_-_review](/uploads/db12d15cbaac926aa84e946ec76adedb/welcome_-_review.png)
We had something like this before the redesign of the Welcome Screen in 2015:
- Without storing these settings in the Persistent Storage, it was better to allow people to do everything in the same screen.
- We also imagined adding more such settings to the Welcome Screen, and thus hiding them all behind a generic "additional setting" made more sense.
Since 2015, we didn't add any setting to the Welcome Screen and rather have plans to move most of them from the Welcome Screen to the session: Unsafe Browser (#15859), Network Connection (#17330), and MAC spoofing that should depends on the network and not the entire session.
Until then, it sounds better to move these few settings to a second step when they can be stored in the Persistent Storage.
Where there is no Persistent Storage, the Welcome Screen could still be displayed in a single screen and save users some extra clicks.https://gitlab.tails.boum.org/tails/tails/-/issues/17721welcome screen difficult to use with keyboard only2021-03-04T16:52:56Zsysterwelcome screen difficult to use with keyboard onlyThe welcome screen is a bit difficult to be used by keyboard only.
Reason: The visibility of marking some fields by pressing tab is bad. Effected fields are "start tails" and some others.
possible improvement: making the lines thicke...The welcome screen is a bit difficult to be used by keyboard only.
Reason: The visibility of marking some fields by pressing tab is bad. Effected fields are "start tails" and some others.
possible improvement: making the lines thicker or choosing a higher contrast.
https://gitlab.tails.boum.org/tails/tails/-/issues/5760tails-greeter: give feedback while successfully repairing a damaged persisten...2024-01-17T15:44:24Zimport-from-Redminetails-greeter: give feedback while successfully repairing a damaged persistent filesystem_Originally created by Tails on [#5760 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/5760)_
When one enables persistence with a persistent FS whose state is
inconsistent state, tails-greeter appears to hang, while..._Originally created by Tails on [#5760 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/5760)_
When one enables persistence with a persistent FS whose state is
inconsistent state, tails-greeter appears to hang, while it’s actually
waiting for the fsck/recovery process to finish. Some people will
interpret this as a system crash, because it takes longer than normal.
On a 14GB test persistent volume, the recovery took more than a minute.
It continued booting fine after recovery.
Relevant kernel messages:
kjournald starting. Commit interval 5 seconds
EXT3-fs (dm-0): using internal journal
EXT3-fs (dm-0): recovery complete
EXT3-fs (dm-0): mounted filesystem with ordered data mode
Also, regarding filesystem corruption caused by users unplugging their USB stick while the Persistent Storage is mounted, @sajolida suggested:
1. When unlocking, we create a flag file in the Persistent Storage.
2. When shutting down cleanly, we delete this flag file.
3. If this empty file is there when unlocking the Persistent Storage:
- In all cases, we can instruct the user to shutdown properly next time.
- If the file system is corrupted, it can help us troubleshooting this failure mode.
(In theory we should know whether the filesystem was unmounted cleanly
or not, and the ext4 repair operation is visible in the kernel logs,
but I doubt udisks makes this info available to us, so a flag file may be the best approach.)https://gitlab.tails.boum.org/tails/tails/-/issues/6084tails-greeter: localize keyboard layout names2021-12-03T07:20:34Zimport-from-Redminetails-greeter: localize keyboard layout names_Originally created by Tails on [#6084 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/6084)_
Seems like all the UI’s l10n is correctly updated on language change,
but the keyboard layout widget is constantly displa..._Originally created by Tails on [#6084 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/6084)_
Seems like all the UI’s l10n is correctly updated on language change,
but the keyboard layout widget is constantly displayed using the locale
the window was loaded with.
- in ubiquity, the `d-i/make-keyboard-names` script uses
`/usr/share/locale/*/LC_MESSAGES/xkeyboard-config.mo` to translate
the keyboard layout names, from list of keyboard layouts gathered
using the d-i’s console-setup `Keyboard/KeyboardNames.pl` script
- `kbd-chooser.c` in `git://git.debian.org/d-i/kbd-chooser.git` uses
`/usr/share/console/lists/`
Feature Branch: feature/localized_layouts
### Related issues
- **Has duplicate** tails/tails#16442https://gitlab.tails.boum.org/tails/tails/-/issues/7001Hint user about the strength of their administration password2023-08-02T17:59:46ZGhost UserHint user about the strength of their administration password_Originally created by @tmc on [#7001 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/7001)_
The GUI bits should be stolen from existing, well-thought solutions to
the same problem, e.g. GNOME Disks.
The (Python) c..._Originally created by @tmc on [#7001 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/7001)_
The GUI bits should be stolen from existing, well-thought solutions to
the same problem, e.g. GNOME Disks.
The (Python) code lives at <https://git-tails.immerda.ch/greeter/>.
### Related issues
- **Related to** tails/tails#7002https://gitlab.tails.boum.org/tails/tails/-/issues/7335The power button does not trigger emergency shutdown in the Greeter2020-05-15T18:53:54ZanonymThe power button does not trigger emergency shutdown in the Greeter_Originally created by @anonym on [#7335 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/7335)_
In 1.1\~beta1:
> When pressing the power button during Greeter, the emergency shutdown
is not triggered, it more or le..._Originally created by @anonym on [#7335 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/7335)_
In 1.1\~beta1:
> When pressing the power button during Greeter, the emergency shutdown
is not triggered, it more or less
> starts a screensaver (nothing displayed though, just black screen)
For me, the first press does nothing. Then there seems to be some amount
of time (20s) where pressing it again still seems to have no effect, but
after that time has passed, pressing it brings the computer to sleep. If
I do not press the button after this time, nothing seems to happen.
Regression since 1.0.
### Related issues
- **Related to** tails/tails#7334
- **Related to** tails/tails#11385