[Lubuntu] Having zram support means that encrypted LVM installs don't work

I agree. I think it is sane for partman-auto-crypto to unmount zram or skip the checks for it.

Is zram still in use, in the installed systems too? Does it affect encryption at rest? (e.g. does zram memory remain unencrypted upon hybernate?)

> I agree. I think it is sane for partman-auto-crypto to unmount zram or skip the checks for it.

I remember briefly looking into this and seeing a conditional with one exception in there so far, so adding this might be trivial. That's probably the solution here.

> Is zram still in use, in the installed systems too?

No, just on the live system.

> Does it affect encryption at rest? (e.g. does zram memory remain unencrypted upon hybernate?)

No, because it isn't in the default install (and the live image is not encrypted).

https://git.launchpad.net/~lubuntu-dev/ubuntu-seeds/+git/lubuntu/commit/?id=62fb253b7fcc41dcc299fde40fff80e8bcd0f5b9

This can be addressed later.

Actually, Steve has a patch.

Hello Simon, or anyone else affected,

Accepted partman-crypto into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/partman-crypto/86ubuntu2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Kubuntu 18.04 daily 2018-04-04.
reproduceable on AMD64 and i386 (downloads SAH256 checked)
i hit this also on a previous daily-build some days before

steps to reproduce:

While booting Live-USB and install Kubuntu via UI
at the point
- Disk Setup
with the option
- Guided - use entire disk and set up encrypted LVM

a message appears:

"Configuration of encrypted volumes failed
An error occurred while configuring encrypted volumes.
The configuration have been aborted."

After trying multiple times to install with encrypted LVM with the error message coming again and again i startet without encryption. than there have been the errormessage written above that stopped the installation. fter klicking back a partition was created with about half of my disksize without advising to do so. Crash with message like "volume has not enough space" resulting in black screen and reboot.

now the USB-Stick is not anymore in the bootable devices and booting my harddrive let me see a blinking _ underline on a black screen

Not sure if i am right place here; It was not possible for me to create a new empty bugreport. Failed installtaion made my system unbootable so i can not report out of the damaged system. Please be so kind to put this in the right place if necessary. Sorry im not at all expirienced with debugging or such. It is a new Laptop with PCI-Express SSD and Intel Core i3-7100U. "Acer Swift 3 SF314-52-385X"

three pictures hitting the bug (screen-photos)
- http://fs1.directupload.net/images/180405/qqsncezm.jpg
- http://fs1.directupload.net/images/180405/dsl9i7n8.jpg
- http://fs1.directupload.net/images/180405/vfdxrri6.jpg
thanky

On Thu, Apr 05, 2018 at 08:02:44PM -0000, Do Re wrote:
> three pictures hitting the bug (screen-photos)
> - http://fs1.directupload.net/images/180405/qqsncezm.jpg
> - http://fs1.directupload.net/images/180405/dsl9i7n8.jpg
> - http://fs1.directupload.net/images/180405/vfdxrri6.jpg

Sorry, this is definitely unrelated. You will need to file a separate bug
report.

This bug was fixed in the package partman-crypto - 86ubuntu2

---------------
partman-crypto (86ubuntu2) bionic; urgency=medium

  * lib/crypto-base.sh: don't regard zram devices as "unsafe", since we
    know these are entirely RAM-backed. LP: #1759732.

 -- Steve Langasek <email address hidden> Wed, 04 Apr 2018 17:07:27 -0700

This is still an issue on the Lubuntu Xenial dailies, and wearing my Lubuntu Release Manager hat, this is absolutely release-critical for 16.04.5.

Subscribing Łukasz Zemczak, who is driving this point release.

Here's a debdiff.

I tested this by modifying the script where it's installed in the live system of the latest Xenial daily and it works.

I don't see how it's reasonable to consider this release-critical for 16.04.5 unless it was a regression since 16.04.4.

Following up on what Steve said, what is the state of this bug in .4? Seeing that the bug has been filled after .4 release, does this mean it's not a .5 regression?

The same issue exists in 16.04 and 16.04.4 so definitely not a regression.

If what Jean-Baptiste (and Steve) confirmed is true and the issue is not a regression from .4, I do not feel that we should re-spin just to include this fix. If it was there in the previous point-release and we did not block on it then, not sure we should right now. Not to mention there has been almost 4 months to get this fixed.

What I can propose is that we pull in this fix *if* we re-spin for some other reasons.

Regardless if it's a regression, it's enough of a critical bug that I'm not confident marking Lubuntu 16.04.5 as ready until it's fixed.

Yes, unfortunately it took this long for someone to realize that this is still an issue, but it's not too late to get it in the point release.