[Bug 154878] Re: LiveCD integrity check doesn't say which file failed

[Brian Murray]

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", checkfile);
      failed++;


** Changed in: casper (Ubuntu)
       Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to casper in Ubuntu.
https://bugs.launchpad.net/bugs/154878

Title:
  LiveCD integrity check doesn't say which file failed

Status in “casper” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: casper

  (Apologies if "casper" is not the right place for this.  I googled for
  similar reports and this seemed like the closest match.  I think I
  roughly know who Casper is.)

  I burned the 7.10 i386 desktop/live CD, booted it up to the first
  screen, and picked the "Check CD for defects" option.

  -rw-r--r-- 1 era era 729608192 2007-10-20 14:25
  ubuntu-7.10-desktop-i386.iso

  It ran for a while, then stopped with the following message visible:

  [Ubuntu logo and sort-of-not-at-all-a-progress-bar]

  Checking integrity, this may take some time
  Check finished: errors found in 1 files!
  Press any key to reboot your system

  Grammar and punctuation gripes notwithstanding, shouldn't it indicate
  how to find out which file or files failed the integrity check?  Is
  it, like, critical, like the kernel, or less critical, like maybe the
  Albanian help file for the geyes applet?

  Being a knowledgeable 1337 h4x0r, I pressed ctrl-alt-fn on the
  assumption that there might be a log or something on one of the
  virtual terminals, but alas, no; and, after doing that, I could not
  figure out how to get back to the graphical screen.  It was certainly
  not on vt7.  On vt1 I see "Loading, please wait ..." but that's it.
  Pressing enter on vt8 initiated a restart, with a message, even, but
  no indication before I pressed enter that this might work better than
  pressing enter on any other random virtual terminal.

  Feel free to split this into two separate bugs, one about the lack of
  information from a failed integrity check, and the other about the
  inability to recover after a failed check.  (Dunno, it might also be
  impossible when it doesn't fail.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/154878/+subscriptions