tails issueshttps://gitlab.tails.boum.org/tails/tails/-/issues2024-03-27T01:09:00Zhttps://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/20204Rename "Language & Region" as "Language & Formats"2024-03-26T23:46:53Zsajolidasajolida@pimienta.orgRename "Language & Region" as "Language & Formats"Someone wrote us thinking that the time zone would be set to their country since it was selected in the "Region" settings.
The real solution to their problem would be #12094.
Still, people might find "Formats" more neutral than "Region...Someone wrote us thinking that the time zone would be set to their country since it was selected in the "Region" settings.
The real solution to their problem would be #12094.
Still, people might find "Formats" more neutral than "Region" in the sense that it's not linked to their location (even though I don't remember this being an issue in usability tests).sajolidasajolida@pimienta.orgsajolidasajolida@pimienta.orghttps://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/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/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/17633Support live-config's locales= and keyboard-layouts= boot options in the Welc...2020-05-15T12:34:30Zbeta-testerSupport live-config's locales= and keyboard-layouts= boot options in the Welcome Screen_Originally created by @beta-tester on [#17633 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/17633)_
hello,
when i add the boot options **`locales=de_DE.UTF-8`** and
**`keyboard-layouts=de`** then the “**Wecome t..._Originally created by @beta-tester on [#17633 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/17633)_
hello,
when i add the boot options **`locales=de_DE.UTF-8`** and
**`keyboard-layouts=de`** then the “**Wecome to Tails**” dialog ignores
those options.
in Debian those options will be used to preselect the settings in the
Welcome dialog, in my case locale: **`de_DE`** “Germany” and keyboard
layout: **`de`** “German”.
but Tails Welcoms dialog behaves even worse:
- the boot option boot option **`keyboard-layouts=de`** is ignored by
the dialog and the default selection is **`en`**
and after passing the dialog the keyboard layout is **`en`** as it
was shown in the welcome dialog.
- the boot options **`locales=de_DE.UTF-8`** was also ignored by the
dialog and the default selection is **`us_EN`**
but after passing the the dialog the user interface was setted to
**`de_DE`** as it was requested by the bootoption
**`locales=de_DE.UTF-8`**
but not as it was shown in the dialog.
the best way would be to take those boot options **`locales=`** and
**`keyboard-layouts=`** into account
to preselect the settings for location and keyboard-layout in the dialog
as Debian’s Welcom dialog does
and use those selections for the environment after passing the dialog.https://gitlab.tails.boum.org/tails/tails/-/issues/17532Clarify the privacy implication of setting a locale2020-05-15T12:35:58Zsajolidasajolida@pimienta.orgClarify the privacy implication of setting a locale_Originally created by @sajolida on [#17532 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/17532)_
Question raised in
<https://lists.autistici.org/message/20200103.094500.22ffbd74.en.html>
Answered in
<https://lis..._Originally created by @sajolida on [#17532 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/17532)_
Question raised in
<https://lists.autistici.org/message/20200103.094500.22ffbd74.en.html>
Answered in
<https://lists.autistici.org/message/20200228.074212.684e7e99.en.html>
First, most, if not all, exploited applications have access to
locale configuration.
Wrt. network fingerprinting:
- We have to assume that some applications may expose the system’s
locale configuration as part of their network activity.
<!-- end list -->
- For Tor Browser and Thunderbird, our configuration tries to avoid
this (best effort) but it’s impossible to prove we did not
miss anything.
Wrt. local storage:
- If an adversary can read the content of the persistent storage,
I’m
pretty sure that the locale configuration can be easily inferred
from that.
<!-- end list -->
- If/once we allow persisting the locale in cleartext on the system
partition, this information will be available to an adversary
who seizes the Tails device.https://gitlab.tails.boum.org/tails/tails/-/issues/16677Journal size is too small when booting with the "debug" boot option2023-07-06T12:52:27ZsegfaultJournal size is too small when booting with the "debug" boot option_Originally created by @segfault on [#16677 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/16677)_
After seeing tails/tails#12373, I expected to see debug messages from the greeter
in the journal when booting Tails..._Originally created by @segfault on [#16677 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/16677)_
After seeing tails/tails#12373, I expected to see debug messages from the greeter
in the journal when booting Tails with the “debug” kernel command line
option, but I don’t see **any** messages from the greeter in the
journal, not even `tails-greeter is ready.` which should be logged with
the `INFO` level (which should be the default level if I interpret
`data/tails-logging.conf` correctly). Am I doing something wrong?
### Attachments
* [Screenshot_tails-amd64-bugfix_13438-parts-of-greeter-translation-not-applied-3.14-20190425T1757Z-60cfe544f9.iso_2019-04-28_13_04_47.png](https://redmine.tails.boum.org/code/attachments/download/2339/Screenshot_tails-amd64-bugfix_13438-parts-of-greeter-translation-not-applied-3.14-20190425T1757Z-60cfe544f9.iso_2019-04-28_13_04_47.png)
* [Screenshot_tails-amd64-bugfix_13438-parts-of-greeter-translation-not-applied-3.14-20190425T1757Z-60cfe544f9.iso_2019-04-28_16_08_38.png](https://redmine.tails.boum.org/code/attachments/download/2340/Screenshot_tails-amd64-bugfix_13438-parts-of-greeter-translation-not-applied-3.14-20190425T1757Z-60cfe544f9.iso_2019-04-28_16_08_38.png)
* [Screenshot_tails-amd64-tmp-13438-16337-3.14-20190427T1818Z-f8fda11d94.img_2019-04-28_12_44_37.png](https://redmine.tails.boum.org/code/attachments/download/2341/Screenshot_tails-amd64-tmp-13438-16337-3.14-20190427T1818Z-f8fda11d94.img_2019-04-28_12_44_37.png)
### Related issues
- **Blocks** tails/tails#17967https://gitlab.tails.boum.org/tails/tails/-/issues/16676Greeter window sometimes broken2020-05-21T12:16:23ZsegfaultGreeter window sometimes broken_Originally created by @segfault on [#16676 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/16676)_
When at least two additional settings are added and the infobar which
says that an incorrect persistence password w..._Originally created by @segfault on [#16676 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/16676)_
When at least two additional settings are added and the infobar which
says that an incorrect persistence password was entered is displayed,
the greeter window is not updated correctly and displays UI elements in
wrong places, in a way that makes it very hard to impossible to use it.
I’m attaching a screenshot.
### Attachments
* [screenshot-greeter-window-broken.png](https://redmine.tails.boum.org/code/attachments/download/2338/screenshot-greeter-window-broken.png)