Project

General

Profile

Bug #8690

tails-install-iuk's output is not forwarded to the Upgrader error reporting

Added by intrigeri almost 3 years ago. Updated over 2 years ago.

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

0%

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

Description

It might be that the autodie pragma may not play well with IPC::Run::run and/or IPC::Run::SafeHandles.


Related issues

Related to Tails - Feature #7431: Improve tails-iuk error reporting for developers Resolved 06/21/2014

History

#1 Updated by intrigeri almost 3 years ago

  • Related to Feature #7431: Improve tails-iuk error reporting for developers added

#2 Updated by intrigeri almost 3 years ago

  • Description updated (diff)
  • Target version changed from Tails_1.4 to Tails_1.3

#3 Updated by intrigeri almost 3 years ago

  • Target version changed from Tails_1.3 to Tails_1.3.2

Won't manage to rework this in time for 1.3, sorry.

#4 Updated by intrigeri over 2 years ago

  • Target version changed from Tails_1.3.2 to Tails_1.4

#5 Updated by intrigeri over 2 years ago

The way the code is supposed to work, such output should be forwarded by the fatal method, via its debugging_info parameter, to tails-upgrade-frontend's stdout, that is in /home/amnesia/.xsession-errors. I've verified that other output from tails-upgrade-frontend indeed lands in there, including debugging_info (I've forced get_upgrade_description to fail, it uses fatal_run_cmd, which successfully run the fatal method, and then in turn the expected debugging info was in .xsession-errors).

AFAICT the install_iuk method uses the exact same code to output debugging info whenever tails-install-iuk fails, so either there's actually no problem (and the debugging info actually lands in .xession-errors as intended), or the way we run tails-install-iuk fails to capture its output, or something.

#6 Updated by intrigeri over 2 years ago

  • Target version changed from Tails_1.4 to Hole in the Roof

Clearly I won't have time to complete this in time for 1.4, and anyway it's too late for the RM to have time to review'n'merge it. Four months ago, I've scheduled it to 1.3 so that it's on my radar, but it was postponed too many times already, so I won't try giving it an explicit target version another time. This problem is harmless 99.xx% of the time, but for the remaining cases, it makes debugging and bug reporting totally impossible, hence I'm calling it a Hole in the Roof.

Also available in: Atom PDF