Project

General

Profile

Bug #15550

Feature #14568: Additional Software Packages

Feature #14594: Code & integration into Tails: Additional Software Packages GUI

Feature #14595: Code for Additional Software Packages GUI: Persistence Setup

Attempting to delete an unlocked persistent volume does not tell the user anything useful

Added by alant about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Persistence
Target version:
Start date:
04/22/2018
Due date:
% Done:

100%

Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Affected tool:
Additional Software Packages

Description

In nightly ISO, "Delete Persistent Volume" is broken.

tails-persistence-delete.desktop[10550]: In fun get_variable_from_file: parameter 1 ($file): Reference bless( ["/var/lib/live/config/tails.persistence","/var/lib/l...) did not pass type constraint "Str" at /usr/share/perl5/Tails/Persistence/Setup.pm line 758.

Associated revisions

Revision 0326d2b6 (diff)
Added by intrigeri about 1 year ago

Update tails-persistence-setup to its current feature/14594-asp-gui branch (Closes: #15550).

… at commit 41252b861b2d3366a794d8d22808a067f9c1f19e.

History

#1 Updated by sajolida about 1 year ago

  • Parent task set to #14592

#2 Updated by sajolida about 1 year ago

  • Affected tool set to Additional Software Packages

#3 Updated by intrigeri about 1 year ago

  • Category set to Persistence
  • Target version set to Tails_3.7

#4 Updated by intrigeri about 1 year ago

  • Parent task changed from #14592 to #14595

(AFAIK and according to Redmine, user testing did not happen yet and it's blocked by the doc anyway.)

#5 Updated by intrigeri about 1 year ago

  • Subject changed from Delete persistent volume is broken to Deleting an unlocked persistent volume is broken

#6 Updated by intrigeri about 1 year ago

  • Subject changed from Deleting an unlocked persistent volume is broken to Attempting to delete an unlocked persistent volume does not tell the user anything useful

#7 Updated by intrigeri about 1 year ago

  • Status changed from Confirmed to Resolved
  • Assignee deleted (intrigeri)
  • % Done changed from 0 to 100

Fixed on the topic branch.

Post mortem: I did not notice this bug earlier as our automated test suite only exercises deleting a persistent volume that hasn't been unlocked (which works fine) and I did not think about trying this out manually myself. The fallout of that bug (had Alan not noticed it) would have been poor UX when a user tries to do that. If such a user had submitted a bug report, presumably help desk would have noticed that they were trying to delete an unlocked persistent volume and told them it's not supported.

Also available in: Atom PDF