Bug #5677

Tails Installer should not break emergency shutdown

Added by Tails 2013-07-18 07:44:25 . Updated 2017-05-23 09:02:54 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Installation
Target version:
Tails_3.0~rc1
Start date:
Due date:
% Done:

100%

Feature Branch:
bugfix/12354-drop-kexec-memory-wipe
Type of work:
Test
Blueprint:

Starter:
0
Affected tool:
Installer
Deliverable for:

Description

sajolida reports:

  • it seems to happen after using the liveusb-creator
  • it happened on both Tails 0.10.1 and Tails experimental
  • sometimes it happens while doing:
    • boot Tails experimental on a isohybrid
    • "Clone Tails" onto another stick
    • unplug the running Tails
  • sometimes the screen turns black with a cursor on the top-left corner and nothing else
  • sometimes the screen stays the same, the system is still somehow responsive but doesn’t shutdown
  • once I couldn’t even shutdown with the red button or by doing sudo halt in a terminal once I reached this weird state
  • once I checked and udev-watchdog was still running on the right device but the emergency shutdown still didn’t work

intrigeri confirms: On VT1, when unplugging my boot USB stick, I see various lines about sdb3, sdb2 and sdb1 being removed, followed by "Bus error". Nothing more happens, and the udev watchdog process is not there anymore.

research

Subtasks

Related issues

Related to Tails - Feature #7194: Check the status of #5447 and #5677 and update /doc/first_steps/shutdown/ accordingly Resolved

History

#1 Updated by anonym 2013-08-01 04:24:14

  • QA Check set to Info Needed
  • Starter set to No

For the record, I haven’t been able to reproduce this for a year or so on any of my hardware. Is any one else still experiencing this?

#2 Updated by intrigeri 2013-08-01 05:54:30

> For the record, I haven’t been able to reproduce this for a year or so on any of my
> hardware. Is any one else still experiencing this?

Yes, I do.

#3 Updated by intrigeri 2013-08-01 06:09:16

  • Tracker changed from Feature to Bug
  • QA Check changed from Info Needed to Dev Needed
  • Type of work changed from Research to Code

#4 Updated by intrigeri 2014-05-10 01:51:05

  • related to Feature #7194: Check the status of #5447 and #5677 and update /doc/first_steps/shutdown/ accordingly added

#5 Updated by intrigeri 2014-05-26 04:25:05

Still reproducible, as reported on Feature #7194, in a build very close to Tails 1.1~rc1.

#6 Updated by BitingBird 2014-06-09 10:09:34

  • Subject changed from liveusb-creator should not break emergency shutdown to Liveusb-creator should not break emergency shutdown

#7 Updated by BitingBird 2014-06-09 15:30:32

  • Subject changed from Liveusb-creator should not break emergency shutdown to liveusb-creator should not break emergency shutdown

#8 Updated by sajolida 2014-06-29 14:21:04

  • Category set to Installation

#9 Updated by BitingBird 2015-01-04 19:06:11

  • Affected tool set to Installer

#10 Updated by BitingBird 2015-04-10 15:08:22

  • QA Check deleted (Dev Needed)

#11 Updated by intrigeri 2016-01-11 17:27:26

  • Subject changed from liveusb-creator should not break emergency shutdown to Tails Installer should not break emergency shutdown

#12 Updated by BitingBird 2016-06-26 11:09:46

  • Type of work changed from Code to Test

Should be tested again with a 2.x

#13 Updated by intrigeri 2017-05-18 09:06:44

  • Status changed from Confirmed to In Progress
  • Assignee set to anonym
  • Target version set to Tails_3.0~rc1
  • QA Check set to Ready for QA
  • Feature Branch set to bugfix/12354-drop-kexec-memory-wipe

I can’t reproduce this on my branch for Bug #12354 (not tested on earlier 3.0~betaN though):

  1. start Tails from a USB stick installed with Tails Installer
  2. plug a 2nd USB stick
  3. Clone and Install to that 2nd USB stick
  4. unplug the boot device
  5. Tails successfully shuts down

#14 Updated by anonym 2017-05-18 14:58:03

  • % Done changed from 0 to 100

FYI I haven’t been able to reproduce this for years on any of my systems (or in VMs).

See Bug #12354 for the review (no blockers found). Please close when you merge!

#15 Updated by anonym 2017-05-18 15:15:00

  • Assignee changed from anonym to intrigeri
  • QA Check changed from Ready for QA to Pass

#16 Updated by intrigeri 2017-05-18 15:38:34

  • Status changed from In Progress to Fix committed
  • Assignee deleted (intrigeri)

#17 Updated by intrigeri 2017-05-23 09:02:54

  • Status changed from Fix committed to Resolved