Bug #15100

Drop obsolete "USB stick cannot start after interrupting persistence wizard" warning

Added by sajolida 2017-12-25 22:11:28 . Updated 2018-01-23 17:28:34 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Persistence
Target version:
Start date:
2017-12-25
Due date:
% Done:

0%

Feature Branch:
Type of work:
End-user documentation
Blueprint:

Starter:
Affected tool:
Installation Assistant
Deliverable for:

Description

Or at least we have something pretending this in our installation instructions:

If you close the assistant before the creation finishes, you might not be able to start Tails from this USB stick anymore.

I did some tests and couldn’t reproduce this so at least it means that it doesn’t happen all the time.

Help desk: Do you remember seeing that in the last year or so?
Foundations: Do you think this bug could still occurs?

Subtasks

History

#1 Updated by sajolida 2017-12-25 22:13:21

#2 Updated by emmapeel 2017-12-26 15:29:08

  • Assignee changed from emmapeel to goupille

I haven’t heard users complain about that.

#3 Updated by mercedes508 2017-12-26 16:09:36

emmapeel wrote:
> I haven’t heard users complain about that.

Me neither. But if needed I can try to reproduce.

#4 Updated by intrigeri 2017-12-26 16:20:36

  • Assignee changed from goupille to intrigeri

Thanks! I’ll take it from here then: I’ll check what made me/us add this warning in the first place.

#5 Updated by goupille 2017-12-26 16:37:11

I don’t remember any reports about that either

#6 Updated by intrigeri 2018-01-02 14:09:53

  • Subject changed from USB stick cannot start after interrupting persistence wizard to Drop obsolete "USB stick cannot start after interrupting persistence wizard" warning
  • Status changed from New to Confirmed
  • Assignee changed from intrigeri to sajolida
  • Type of work changed from Research to End-user documentation

tl;dr: I believe that this warning can safely be removed.

Wow, archeology time! This warning has been here since the first version of the persistence doc. The explanation for this warning seems to be Feature #5564 aka. https://bugs.freedesktop.org/show_bug.cgi?id=49524 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673042. This was a bug in libparted, that we used to workaround in tails-persistence-setup initially, in a way that would only work if the persistent volume creation was not interrupted, hence this warning; and then we shipped a libparted with the bugfix backported from Wheezy (in Tails 0.17.2) and dropped the workaround in tails-persistence-setup.

#7 Updated by cbrownstein 2018-01-03 00:51:26

  • Status changed from Confirmed to In Progress
  • Assignee changed from sajolida to cbrownstein

#8 Updated by cbrownstein 2018-01-03 01:20:50

  • Assignee changed from cbrownstein to sajolida
  • QA Check set to Ready for QA

I deleted the warning in my branch. I also fixed the list numbering.

https://github.com/cbrownstein/tails/tree/doc/15100-obsolete-usb-cannot-start

#9 Updated by sajolida 2018-01-23 17:28:35

  • Status changed from In Progress to Resolved
  • Assignee deleted (sajolida)
  • QA Check deleted (Ready for QA)

Merging as well.

Note that the numbering is automatic in Markdown so cd9c0e5935 was superfluous (didn’t test though).

I usually only number steps with “1., 1., 1.” in order to avoid broken numbering even in the source code :)