Comment 8 for bug 1858376

Revision history for this message
Cubic PPA (cubic-wizard) wrote :

Sometimes vmlinuz or initrd are simlinks to the actual files. Cubic presents these simlinks on the Boot Kernels tab, because the simlink names may be more recognizable to a user than the actual file names.

The issue occurs because Cubic copies the simlinks but does not copy the target files. This is not an issue if the user selects a row listing the actual target files on the Boot Kernels tab, because Cubic these files successfully.

For example "vmlinuz" may be a simlink to "vmlinuz-5.3.0-26-generic" and "initrd.img" may be a simlink to "initrd.img-5.3.0-26-generic".

If the user selects the boot kernel row that has both "vmlinuz-5.3.0-26-generic" and "initrd.img-5.3.0-26-generic", the boot kernel files will be copied successfully. However, if the use selects a boot kernel row that has either "vmlinuz" or "initrd.img", then the copy step fails at 50%.

A couple of options are available to fix this issue:
1. Always copy the actual target files instead of the simlink. (The files are renamed when they are copied, anyway).
2. Do not show simlinks in the boot kernels list. This option will reduce the number of kernels shown, making the UI less confusing. The user doesn’t necessarily have to recognize the file names, because the kernel versions are listed anyway.