It shows I will need to revert the tss group membership patch. The upstream sealing is indeed broken, so exposing the device was a mistake. Fixing the sealing will be more work than reverting the patch, so I will do that.
I suspect the reporter has manually exposed /dev/tpm* to gnome-remote- desktop on 26.04? This behaviour comes on by default in Stonking after 2161032, it shouldn't by default on Resolute. mrunaltmeshram: Please can you run, id gnome-remote-desktop ls -l /dev/tpm* The drop-in is the right workaround for now. ** Bug watch added: github.com/parallaxsecond/parsec/issues #504 https://github.com/parallaxsecond/parsec/issues/504 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2164534 Title: Remote Login stops working after every reboot on TPM-equipped machines: "Couldn't retrieve RDP credentials: Esys_ContextLoad failed: tpm:parameter(1):integrity check failed" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-remote-desktop/+bug/2164534/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
