Project

General

Profile

Bug #9234

Abort boot when any live-config hook fails

Added by anonym almost 4 years ago. Updated 6 months ago.

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

0%

QA Check:
Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Affected tool:

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 #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?


Related issues

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

History

#1 Updated by BitingBird almost 4 years ago

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

#2 Updated by u 6 months ago

  • QA Check set to Info Needed

Is this still a thing to consider?

#3 Updated by intrigeri 6 months ago

  • QA Check deleted (Info Needed)

Yes.

#4 Updated by u 6 months ago

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

Also available in: Atom PDF