fwupd consuming very high cpu after startup/login
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
appstream-glib (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
I believe this may be a regression (relapse of Bug #1591868 ). I upgraded to yakkety the other day without major incident and have all "updates" checked in the Software and Sources GUI. But after booting and logging in just now, I see fwupd consuming two full cores without letup.
In kern.log I see this line:
fwupd[6242]: Failed to coldplug: UEFI firmware updating not supported
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: fwupd 0.7.2-0ubuntu1
ProcVersionSign
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Oct 26 19:49:20 2016
InstallationDate: Installed on 2016-07-03 (115 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: fwupd
UpgradeStatus: Upgraded to yakkety on 2016-10-25 (1 days ago)
Changed in appstream-glib (Ubuntu): | |
assignee: | nobody → Canonical Desktop Team (canonical-desktop-team) |
tags: | added: patch |
no longer affects: | fwupd (Ubuntu) |
Changed in appstream-glib (Ubuntu): | |
importance: | Undecided → Medium |
tags: |
added: patch-accepted-upstream removed: regression-update |
Changed in appstream-glib (Ubuntu): | |
assignee: | Robert Ancell (robert-ancell) → nobody |
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: /github. com/hughsie/ fwupd/issues/ 70
https:/
It has not yet been debugged.
If you are technical enough, can you please follow the same steps mentioned in that bug? /github. com/hughsie/ fwupd/issues/ 70#issuecomment -254816591
https:/
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.