tails-debugging-info crashes if any of the commands it runs fails
As previously noted e.g. in commit f5d604be, tails-debugging-info
crashes if any of the commands it runs returns a non-zero exit code. Since this can happen for a number of non-pathological reasons (see e.g. below), tails-debugging-info
should instead be able to report that the command failed, or at least make it so that the command fails silently.
Context: In my arm64 developer previews of Tails, specifically on Apple Silicon, WhisperBack fails to start due to dmidecode
and df
exiting with non-zero exit codes when run by tails-debugging-info
. While in the latter case the non-zero exit code is probably due to some kind of bug in how Debian's df
interacts with Apple Silicon's lack of UEFI variables, in the former it is expected: SMBIOS is not there at all, so dmidecode
can't find the information it is looking for. In both these cases, the non-zero exit codes are not pathological to Tails per se, but rather they reflect how those programs interact with that platform. Thus tails-debugging-info
would have no reason to crash (quite the opposite, it should report the output!). I understand I am giving you two examples that only hold for a platform which is not supported by Tails, but I believe tails-debugging-info
not crashing on non-zero exit codes should hold regardless. And this also happens on x86_64, as shown by f5d604be.