On 3/29/22 11:41, Gordon Messmer wrote:
In Fedora 35, I am able to use the tpm2 device to automatically unlock
a LUKS volume on boot. Dracut 055 has a bug in the tpm2-tss module,
requiring either applying
https://github.com/dracutdevs/dracut/commit/8b17105bed69ed90582a13d97d95ee19e6581365
and
No missing expected images.
Failed openQA tests: 6/229 (x86_64), 6/161 (aarch64)
New failures (same test not failed in Fedora-36-20220328.n.0):
ID: 1202569 Test: x86_64 Server-dvd-iso anaconda_help
URL: https://openqa.fedoraproject.org/tests/1202569
ID: 1202672 Test: x86_64 Silverblue-dv
OLD: Fedora-36-20220328.n.0
NEW: Fedora-36-20220329.n.1
= SUMMARY =
Added images:0
Dropped images: 0
Added packages: 4
Dropped packages:0
Upgraded packages: 161
Downgraded packages: 1
Size of added packages: 814.09 KiB
Size of dropped packages:0 B
Size of
On 3/29/22 11:41, Gordon Messmer wrote:
Does anyone have suggestions for debugging this issue?
I've booted into a dracut shell and confirmed that the tpm device nodes
are present...
Trying to manually attach the LUKS volume prints no error messages, but
prompts for a passphrase rather than
Hi testers,
At the Workstation working group meeting, today we learned about the
following bugs:
Cannot print except when rebooting computer after upgrade from F35 ->
after recommended manual intervention, now cannot print except after
turning off printer and then printing a blank page in LibreOf
In Fedora 35, I am able to use the tpm2 device to automatically unlock a
LUKS volume on boot. Dracut 055 has a bug in the tpm2-tss module,
requiring either applying
https://github.com/dracutdevs/dracut/commit/8b17105bed69ed90582a13d97d95ee19e6581365
and then including the tpm2-tss module in dr
No missing expected images.
Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64)
(Tests completed, but using a workaround for a known bug)
Old soft failures (same test soft failed in Fedora-Cloud-35-20220327.0):
ID: 1202012 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://op
