** Changed in: partman-crypto (Ubuntu Xenial)
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/1759732
Title:
[Lubuntu] Having zram support means that encrypted LVM
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.
--
You received
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
The same issue exists in 16.04 and 16.04.4 so definitely not a
regression.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759732
Title:
[Lubuntu] Having zram support means that encrypted LVM
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?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: partman-crypto (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759732
Title:
[Lubuntu] Having zram support means that
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759732
Title:
[Lubuntu] Having
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.
** Patch added: "1-86ubuntu1-to-86ubuntu1.1.debdiff"
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
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
On Thu, Apr 05, 2018 at 08:02:44PM -, 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
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
--
You received this bug notification because you are a member of
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
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
** Changed in: partman-crypto (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: partman-crypto (Ubuntu)
Milestone: None => ubuntu-18.03
** Changed in: partman-crypto (Ubuntu)
Milestone: ubuntu-18.03 => ubuntu-18.04-beta
--
You received this bug notification because you
Actually, Steve has a patch.
** Changed in: partman-crypto (Ubuntu)
Assignee: (unassigned) => Steve Langasek (vorlon)
** Changed in: partman-crypto (Ubuntu)
Milestone: later => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
https://git.launchpad.net/~lubuntu-dev/ubuntu-
seeds/+git/lubuntu/commit/?id=62fb253b7fcc41dcc299fde40fff80e8bcd0f5b9
This can be addressed later.
** Changed in: partman-crypto (Ubuntu Bionic)
Milestone: ubuntu-18.03 => None
** No longer affects: partman-crypto (Ubuntu Bionic)
** Changed
** Package changed: partman-auto-crypto (Ubuntu Bionic) => partman-
crypto (Ubuntu Bionic)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759732
Title:
[Lubuntu] Having zram support means that
> 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
** Tags added: id-5abd10a030762b57e1db728a
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759732
Title:
[Lubuntu] Having zram support means that encrypted LVM installs don't
work
To manage
** Also affects: partman-auto-crypto (Ubuntu Bionic)
Importance: Critical
Status: Confirmed
** Tags removed: rls-bb-incoming
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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?)
--
You received this bug notification because you are
22 matches
Mail list logo
