Comment 2 for bug 2047676

Revision history for this message
Chris Guiver (guiverc) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

I suspect the issue relates to the linux kernel; rather than calamares.

The version of calamares initially used in Lubuntu 22.04 LTS was packaged as 3.2.41.1-0ubuntu4 (https://packages.ubuntu.com/jammy/calamares) but was updated to 3.2.61-0ubuntu0.1 (https://packages.ubuntu.com/jammy-updates/calamares) for later ISOs, due to install problems reported.

The kernel stack on 22.04(.4) ISOs will soon change from
- linux-image-generic-hwe-22.04 | 6.2.0.39.40~22.04.16 | jammy-security | amd64, arm64, armhf, ppc64el, s390x
to
- linux-image-generic-hwe-22.04 | 6.5.0.14.14~22.04.7 | jammy-proposed | amd64, arm64, armhf, ppc64el, s390x
which may alter the issue, but no change to calamares is expected.

The current version of calamares being modified is
- calamares | 3.3.0.0-0ubuntu4 | noble/universe | source, amd64, arm64, armhf, ppc64el, riscv64, s390x
which is available for test with the Lubuntu noble ISO, if problems are encountered with that, changes will be made. Current noble ISOs are using the 6.5 kernel, so you could test with that (if easily tested on your hardware), but 24.04 will not be released with the current 6.5 kernel (which I believe is what is causing your issue).

For this bug to be valuable, `apport-collect` should be run, but I won't suggest it, as I believe your issue is kernel (or more precisely kernel module - aka video driver) related, and not the installer code itself.

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.