Bug #9234

Abort boot when any live-config hook fails

Added by anonym 2015-04-15 07:20:54 . Updated 2018-08-18 14:46:06 .

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2015-04-15
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Currently, if any of our live-config hooks fail, Tails still boots without reporting an error (at least not in a way that’s obvious to the user), and without running any of the subsequent live-hooks and we get stuff like Bug #9149. We should instead abort booting + writing an appropriate error message. It’s also worth considering to allow continue the boot process (without aborting subsequent live-config hooks) upon user confirmation.

Unfortunately I believe achieving any of the above will require modifying live-config. Perhaps there are other reasons to start using something else, like making them into systemd unit files?

Subtasks

Related issues

Related to Tails - Bug #9149: Random Pidgin nicknames are not generated on boot when the system clock is wrong Resolved 2015-04-01
Related to Tails - Feature #6766: Display an error message when boot fails Confirmed 2014-02-25

History

#1 Updated by BitingBird 2015-04-15 14:47:52

  • related to Bug #9149: Random Pidgin nicknames are not generated on boot when the system clock is wrong added

#2 Updated by Anonymous 2018-08-18 12:15:25

  • QA Check set to Info Needed

Is this still a thing to consider?

#3 Updated by intrigeri 2018-08-18 14:46:06

  • QA Check deleted (Info Needed)

Yes.

#4 Updated by Anonymous 2018-08-19 07:03:05

  • related to Feature #6766: Display an error message when boot fails added