Feature #5470

Should refuse to edit persistence config when persistence is enabled read-only

Added by Tails 2013-07-18 07:41:33 . Updated 2017-08-30 17:13:01 .

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Persistence
Target version:
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

To reproduce this bug

  • setup persistence;
  • reboot and activate it read-only;
  • start tails-persistence-setup.

Result

tails-prsistence-setup then allows you to modify settings of the persistence, but doesn’t actually save them.

Desired result

Actually save the modification, of refuse to launch the assistant with an explicit message.

Subtasks

History

#1 Updated by intrigeri 2013-10-04 08:11:58

  • Subject changed from tails-persistence-setup behaves incoherently when persistence is ro to Refuse to edit persistence config when persistence is enabled read-only
  • Category set to Persistence
  • Starter set to No

#2 Updated by intrigeri 2013-10-04 08:12:12

  • Subject changed from Refuse to edit persistence config when persistence is enabled read-only to Should refuse to edit persistence config when persistence is enabled read-only

#3 Updated by BitingBird 2015-04-10 16:01:50

This is elevated since over a year. Should this become a hole in the roof?

#4 Updated by intrigeri 2015-04-11 09:59:49

  • Assignee set to intrigeri
  • Priority changed from Elevated to Normal
  • Target version set to Hole in the Roof

#5 Updated by intrigeri 2017-05-26 10:43:44

  • Status changed from Confirmed to Rejected
  • Assignee deleted (intrigeri)

We don’t support read-only persistence anymore.

#6 Updated by BitingBird 2017-08-30 17:13:01

  • Target version deleted (Hole in the Roof)