Oooh, good catch. That *is* a bug that we should fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064909
Title:
Lubuntu and Kubuntu 24.04 fail to decrypt on boot when installed on
encrypted
So I came across this bug because I was *trying* to use a separate
unencrypted boot partition, but then calamares yelled at me with:
A separate boot partition was set up together with an encrypted root
partition, but the boot partition is not encrypted.
There are security concerns with this kind
Thank YOU for all the effort. Had this been an actual bug the extent to
which you went would have made a big difference.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064909
Title:
Lubuntu and
Ah, that makes sense now. I avoided the erase disk option before,
because if I remember correctly, it didn't work with my multi-boot setup
in 22.04. But it seems to work fine in 24.04 (OS switching with BIOS
boot menu, or rEFInd). So no need for me to mess with luks1 and
potential security issues.
** Changed in: calamares (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064909
Title:
Lubuntu and Kubuntu 24.04 fail to decrypt on boot when installed on
It looks like you don't have a separate /boot partition being created?
All Ubuntu flavors use Canonical's build of GRUB (naturally), and
Canonical explicitly **does not support /boot being located on an
encrypted partition.** It actually creates additional security risks to
do so as Canonical
Thanks for the additional testing.
The erase disk & install using encryption gets more QA
(https://discourse.lubuntu.me/t/testing-checklist-noble/4809 shows six
QA tests for that), and whilst there are some manual partitioning
install tests, no encryption is mandated there.
--
You received this
UPDATE: I tried selecting the erase whole drive option (instead of
manual partitioning) and encrypt from there, and that seems to be
working. I tried both Kubuntu 24.04 and Lubuntu 24.04 in VirtualBox, and
they both seem to be working as expected. So the problem might be with
manual partitioning
Thanks. I followed your instructions and hopefully did things right. I
ran a fresh install of Lubuntu 24.04 in VirtualBox again, and at the end
unchecked the reboot box and clicked done. It took me to the live
desktop. I opened the terminal, ran the "apport-collect 2064909"
command, authorized
apport information
** Tags added: apport-collected noble
** Description changed:
Test hardware 1 (Lubuntu 24.04 and Kubuntu 24.04):
VirtualBox, 2 CPUs, 8192 MB RAM, 128 MB VRAM, EFI disabled, Host I/O cache
disabled.
Test hardware 2 (Kubuntu 24.04):
Intel Core i5 7400, 32 GB DDR4
Thanks for responding, AND asking for further help!
Sorry I didn't think thru my wording clear enough... To be useful the
`apport-collect` has to be run AFTER a failed install, however to confirm it
failed (by your already provided description) you need to reboot & thus the
report I want
Sorry, I'm new to launchpad. I'm a bit unsure about where to run the
apport-collect command. The installation completes normally and asks me
to reboot as usual. The problem occurs after the reboot, at which point
I no longer have access to a terminal except the grub rescue shell (as
the system
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
If possible, can you boot your system (using 24.04 media you tried to
install) and try the install again, assuming it fails again, please
follow the following instructions AFTER the error has [re-]occurred.
13 matches
Mail list logo
