Feature #15573

Ask for confirmation when starting without unlocking the persistent storage

Added by sajolida 2018-05-05 14:15:46 . Updated 2020-04-15 06:02:17 .

Status:
In Progress
Priority:
Normal
Assignee:
Category:
Persistence
Target version:
Start date:
2018-05-05
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Welcome Screen
Deliverable for:

Description

During the user testing of the Additional Software beta, 3 participants out of 5 missed the new field to unlock the “Encrypted Persistent Storage” when restarting with a persistent storage for the first time:

  • 2 of them restarted without seeing it.
  • 1 of them saw it right before restarting.

They would probably easily learn from their mistake for the next time. Still, P4 missed it a second time :)

If we assume that people who have a persistent storage want to unlock it in the vast majority of cases, it could be worth asking for confirmation before starting without unlocking the persistent storage in case one is detected.

That might save some of our users a bunch of restarts.

Files

confirm.png (53114 B) sajolida, 2019-12-11 18:38:51

Subtasks

Related issues

Related to Tails - Feature #15586: Instruct about the possibility of creating a persistent storage when there is none Confirmed 2018-05-05
Related to Tails - Feature #14544: Spend software developer time on smallish UX improvements In Progress 2018-08-31
Blocked by Tails - Feature #8948: Reconsider the terminology around "persistence" Resolved 2015-08-15

History

#1 Updated by sajolida 2018-05-05 18:57:32

  • related to Feature #15586: Instruct about the possibility of creating a persistent storage when there is none added

#2 Updated by sajolida 2018-05-05 18:57:44

  • related to Feature #14544: Spend software developer time on smallish UX improvements added

#3 Updated by sajolida 2019-11-21 18:44:16

  • blocks Feature #16688: Core work 2019Q3 → 2019Q4: User experience added

#4 Updated by sajolida 2019-11-21 18:45:46

  • blocked by Feature #8948: Reconsider the terminology around "persistence" added

#5 Updated by sajolida 2019-11-21 18:46:52

  • blocked by deleted (Feature #16688: Core work 2019Q3 → 2019Q4: User experience)

#6 Updated by sajolida 2019-11-21 18:46:58

  • related to Feature #16688: Core work 2019Q3 → 2019Q4: User experience added

#7 Updated by sajolida 2019-11-21 18:49:29

  • related to deleted (Feature #16688: Core work 2019Q3 → 2019Q4: User experience)

#8 Updated by sajolida 2019-11-21 18:49:37

  • blocks Feature #16688: Core work 2019Q3 → 2019Q4: User experience added

#9 Updated by sajolida 2019-11-21 18:54:43

  • Assignee set to sajolida
  • Target version set to Tails_4.2

#10 Updated by sajolida 2019-12-11 18:42:02

  • File confirm.png added
  • Tracker changed from Bug to Feature
  • Status changed from Confirmed to In Progress
  • Assignee deleted (sajolida)
  • Target version deleted (Tails_4.2)
  • Type of work changed from User interface design to Code

It could look like this:

On top of this, it would be awesome to have some GNOME way of highlighting the passphrase field or something like that. I couldn’t find easily how to do this in Gtk but if there’s already a predefined way of doing these things, we should do it. Otherwise forget it.

#11 Updated by sajolida 2019-12-18 11:43:35

  • blocked by deleted (Feature #16688: Core work 2019Q3 → 2019Q4: User experience)

#12 Updated by sajolida 2019-12-18 11:43:40

The next step is not UX work anymore.

#13 Updated by intrigeri 2020-02-23 11:07:34

Alan says it should be simple for him to implement.

#14 Updated by intrigeri 2020-04-15 06:02:17

  • Affected tool changed from Greeter to Welcome Screen