This bug was fixed in the package plymouth - 0.9.4git20190712-0ubuntu4.1
---
plymouth (0.9.4git20190712-0ubuntu4.1) eoan; urgency=medium
* debian/patches/misc-changes.patch: fix an Ubuntu-specific bug in
handling plymouth ask-for-password with a --command option that results
I've confirmed that after upgrade to plymouth from unstable, the
testcase passes (and zfs initramfs decryption works now in Ubuntu
19.10).
** Tags removed: verification-needed verification-needed-eoan
** Tags added: verification-done-eoan
--
You received this bug notification because you are a
** Tags removed: verification-failed-eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810154
Title:
ply_boot_client_process_incoming_replies: Assertion `request_node !=
NULL' failed
To manage
** Changed in: plymouth (Ubuntu Eoan)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810154
Title:
ply_boot_client_process_incoming_replies: Assertion `request_node
Hello Andreas, or anyone else affected,
Accepted plymouth into eoan-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/plymouth/0.9.4git20190712-0ubuntu4.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
This bug was fixed in the package plymouth - 0.9.4git20190712-0ubuntu5
---
plymouth (0.9.4git20190712-0ubuntu5) focal; urgency=medium
* debian/patches/misc-changes.patch: fix an Ubuntu-specific bug in
handling plymouth ask-for-password with a --command option that results
** Description changed:
+ [SRU Justification]
+ An Ubuntu-specific patch causes a crash in plymouth that does not occur
upstream and breaks one of the standard use cases of the plymouth client, to
prompt for passwords. While the specific error does not affect password
prompting for LUKS due
To clarify, as those questions were asked on IRC:
1. I'm the author of the patch.
2. The bug exists only in Ubuntu, not in upstream version of plymouth - it's
caused by the changes included in "misc-changes.patch" (that I'm not touching
with at 30 foot pole).
--
You received this bug
** Changed in: plymouth (Ubuntu)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810154
Title:
ply_boot_client_process_incoming_replies: Assertion `request_node !=
** Changed in: plymouth (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810154
Title:
ply_boot_client_process_incoming_replies: Assertion `request_node !=
The attachment "cached-password-fix.patch" seems to be a patch. If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
There's a bug in processing cached password replies from plymouthd which
causes this assertion, the attached patch fixes this issue (it happens
e.g. when using ZFS with native encryption).
** Patch added: "cached-password-fix.patch"
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: plymouth (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810154
Title:
13 matches
Mail list logo
