Project

General

Profile

Feature #15573

Ask for confirmation when starting without unlocking the persistent storage

Added by sajolida almost 2 years ago. Updated about 1 month ago.

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

0%

Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Affected tool:
Greeter

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.

confirm.png View (51.9 KB) sajolida, 12/11/2019 06:38 PM


Related issues

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

History

#1 Updated by sajolida almost 2 years ago

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

#2 Updated by sajolida almost 2 years ago

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

#3 Updated by sajolida 5 months ago

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

#4 Updated by sajolida 5 months ago

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

#5 Updated by sajolida 5 months ago

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

#6 Updated by sajolida 5 months ago

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

#7 Updated by sajolida 5 months ago

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

#8 Updated by sajolida 5 months ago

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

#9 Updated by sajolida 5 months ago

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

#10 Updated by sajolida 4 months ago

  • File confirm.png View 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 4 months ago

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

#12 Updated by sajolida 4 months ago

The next step is not UX work anymore.

#13 Updated by intrigeri about 1 month ago

Alan says it should be simple for him to implement.

Also available in: Atom PDF