This seems to have been fixed during the transition from usplash to
plymouth. Here is the relevant bit of code:
if (strncmp(hex_output, checksum, strlen(hex_output)) == 0) {
plymouth_success(client, "%s: OK", checkfile);
} else {
plymouth_failure(client, "%s: mismatch", checkf
** Changed in: casper (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/154878
Title:
LiveCD integrity check doesn't say which file failed
To manage notifications
As a matter of fact, I don't think it would be hard to make it less
opaque in the standard scenario, without necessarily losing market share
among the technological pants-wetters. For instance, displaying raw
output on a separate virtual terminal might be all it really takes.
--
LiveCD integrity
Nevertheless, I think this is something that should be considered, not
as a standard use case, but if a user wishes to know what file(s) are
incorrect.
** Changed in: casper (Ubuntu)
Importance: Undecided => Wishlist
--
LiveCD integrity check doesn't say which file failed
https://bugs.launchp
The md5sum of the downloaded image didn't match the official md5sum
d2334dbba7313e9abc8c7c072d2af09c. Downloaded anew and got an image with
the correct MD5. This should teach me to not trust a sucky USB stick
for carrying around any useful data ...
Loop-mounting the .iso and running md5sum revea
