Hello, Although it's possible it's a relapse/regression, the more likely situation is another corner case that causes similar symptoms.
The mention in kern.log about failing to coldplug UEFI isn't the cause of this, that's expected if your manufacturer doesn't support UEFI capsule updates. A similar bug with Ubuntu 16.10 was just reported upstream here: https://github.com/hughsie/fwupd/issues/70 It has not yet been debugged. If you are technical enough, can you please follow the same steps mentioned in that bug? https://github.com/hughsie/fwupd/issues/70#issuecomment-254816591 That combination of artifacts and steps should hopefully help to narrow down what's going on. Also, please immediately back up the contents of /var/lib/app-info/yaml (and make sure you follow symlinks) as if it's caused by transient metadata in that directory it may clear up on it's own the next day and be hard to reproduce. ** Bug watch added: github.com/hughsie/fwupd/issues #70 https://github.com/hughsie/fwupd/issues/70 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637024 Title: fwupd consuming very high cpu after startup/login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1637024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
