fwupd taking 100% CPU

Bug #1698468 reported by Greg d'Eon
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
fwupd (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

After I boot into Ubuntu, top shows me a fwupd process taking 100% CPU. The log file /var/log/syslog has several highlighted messages like

Jun 13 18:11:23 opal gnome-session[1487]: (gnome-software:1660): Gs-WARNING **: failed to call gs_plugin_add_updates_historical on fwupd: failed to start fwupd: Error calling StartServiceByName for org.freedesktop.fwupd: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.fwupd': timed out

Jun 13 18:11:26 opal gnome-session[1487]: (gnome-software:1660): Gs-WARNING **: failed to call gs_plugin_refine on appstream: Error opening file: Permission denied

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-78-generic 4.4.0-78.99
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: greg 1620 F.... pulseaudio
 /dev/snd/controlC1: greg 1620 F.... pulseaudio
CurrentDesktop: Unity
Date: Fri Jun 16 19:00:37 2017
HibernationDevice: RESUME=UUID=c05e0556-350a-4c17-8558-c475f250ccbf
InstallationDate: Installed on 2016-04-28 (414 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: TOSHIBA Satellite S50-B
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed root=UUID=9200f944-2d22-4f9b-8c44-e1498370470d ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-78-generic N/A
 linux-backports-modules-4.4.0-78-generic N/A
 linux-firmware 1.157.11
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/05/2014
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.40
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name1
dmi.board.vendor: Type2 - Board Vendor Name1
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis ManuFacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: dmi:bvnINSYDECorp.:bvr1.40:bd05/05/2014:svnTOSHIBA:pnSatelliteS50-B:pvrPSPQ6C-020001:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite S50-B
dmi.product.version: PSPQ6C-020001
dmi.sys.vendor: TOSHIBA

Revision history for this message
Greg d'Eon (gregdeon) wrote :
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc5

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Greg d'Eon (gregdeon) wrote :

I don't remember any big changes that caused this.

I tried using the 4.12-rc5 kernel - the bug still occurs with the same log messages.

tags: added: kernel-bug-exists-upstream
Revision history for this message
Greg d'Eon (gregdeon) wrote :

It looks like I fixed it. I tried a couple of things yesterday, but I didn't think any of them solved this problem... so I'm not sure what exactly I did to fix this.

I _think_ the solution was
sudo apt-get autoremove gnome-software
sudo apt-get install gnome-software
as in this bug: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1591868/comments/40

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in fwupd (Ubuntu):
status: New → Confirmed
Revision history for this message
Mario Limonciello (superm1) wrote :

Closing as reported fixed by user. If you can reproduce it again please re-open.

no longer affects: linux (Ubuntu)
Changed in fwupd (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.