Option (Ctrl-C) not shown to disable ISO verification

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1870018

I've noted the same using today's Lubuntu 20.04 daily.
There was no message to skip was the big 'new' difference I saw.

I have only achieved the 'skip' once using Lubuntu's daily since it was introduced, but I've tried multiple times with today's daily and I 'waited' for it at least 3 times today.

Status changed to 'Confirmed' because the bug affects multiple users.

I also noticed this today testing Lubuntu 20.04 daily but assumed it was by design and not a bug.(as the S skip option was not displayed)

The keybinding was recently changed to ctrl-C
https://launchpad.net/ubuntu/+source/casper/1.442

Also it changed slightly the protocol to be fsckd compatible but maybe those flavor themes don't handle that well? (the message is showing the ubuntu iso with spinner)

Using Xubuntu (20200331) I also don't see the option to skip but Ctrl-C does work as it should. However, the space in which I would expect to see the skip prompt is taken up by the file check messages which are displayed on five lines. That is, previous messages are not being over-written correctly. New messages are being displayed below the previous one.

Could you add a screenshot of the issue?

It looks like maybe the xubuntu plymouth theme needs some fixing...

I think this is a casper regression with old themes compat.

Screenshot of Xubuntu 20.04 file check

There is a bug in the ubuntu-logo theme script which eats the Ctrl+C message. Meaning, it was never shown correctly during on-boot fsck with systemd-fckd.

And also it was copied across into all the derivatives of the plymouth theme.

I could send an "old" style keys: message that should work in casper, but that needs some kind of a detection if the theme supports new messages or not.

It would be nice to fix all the themes properly though.

Any hints about what should be changed to resolve this please? Any sort of example code would be most appreciated.

This bug was fixed in the package casper - 1.443

---------------
casper (1.443) focal; urgency=medium

  * Make fsckd under spinner/logo themes produce consistent output
  * Make plymouth-less progress output less bad
  * Use theme-specific keys: or fsckd-cancel-msg: for Ctrl+C message LP:
    #1870018
  * Add fsck.mode=skip sensitivity to casper-md5check
  * ubuntu-server: skip mounting swap (as hacked by livecd-rootfs currently)
  * Leave fsck result as a json /run/casper-md5check.json file.
  * ubuntu-server: adapt runtime netplan into cloud-config cloud.cfg
  * Fix cmdline parsing, it was always broken

 -- Dimitri John Ledkov <email address hidden> Fri, 03 Apr 2020 13:04:38 +0100