> 2. Once it is up and running, starting the firmware-updater.firmware-notifier > service produced this message: > 15:55:12.499 FuPluginLinuxLockdown failed to ensure attribute fix flags: > missing executable grubby in PATH
This message is to be expected; Ubuntu doesn't use grubby. > 1. For some reason the fwupd program needs 20 minutes to recognize the TPM module in my computer: OK; if it's narrowed down to TPM then you can experiment with disabling the TPM plugin for fwupd. You can see about the DisabledPlugins key in this: https://fwupd.github.io/libfwupdplugin/fwupd.conf.html#daemon-parameters If this helps, I feel we need to turn on some of the TPM library debugging to characterize, we can follow up with the environment variables that do this after we see if disabling the TPM plugin helps. ** Also affects: fwupd (Ubuntu) Importance: Undecided Status: New ** Summary changed: - DPCD accesses with nouveau fail; leading to other problems + fwupd daemon hangs for a while during TPM access -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2098668 Title: fwupd daemon hangs for a while during TPM access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2098668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
