Fixed in Zesty and later with package appstream-glib 0.6.6-1
---
appstream-glib (0.6.6-1) unstable; urgency=medium
* New upstream version: 0.6.6
* scan-metainfo.patch: Scan for data in /usr/share/metainfo
when composing collection data
* Update symbols file
-- Matthias Klumpp Thu, 2
** Changed in: appstream-glib (Ubuntu)
Assignee: Robert Ancell (robert-ancell) => (unassigned)
--
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 s
** Tags removed: regression-update
** Tags added: patch-accepted-upstream
--
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 no
** No longer affects: fwupd (Ubuntu)
** Changed in: appstream-glib (Ubuntu)
Importance: Undecided => Medium
--
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
** Tags added: patch
--
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.launch
The upstream comments suggest that this is likely fixed in 0.6.6 [1].
This seems like an obvious fix, but I don't know how to reproduce the
existing problem.
This change is a general fix to handle invalid YAML files, with a likely
cause being using a captive portal (so it returns an HTML page inst
Can someone who can reproduce this bug try this and see if it works?
** Patch added: "appsteam-glib-invalid-yaml.debdiff"
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1637024/+attachment/4822967/+files/appsteam-glib-invalid-yaml.debdiff
--
You received this bug notification because y
Robert, do you reckon you could look at this?
If it's possible (e.g. with build-dep versions) and acceptable to the
SRU team then I would be quite happy with moving to 0.6.8 in yakkety as
there are loads of random fixes - it's quite a fast moving project. The
problem is that there are new features
** Changed in: appstream-glib (Ubuntu)
Assignee: (unassigned) => Canonical Desktop Team (canonical-desktop-team)
--
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 ver
I'm seeing the same behavior after a reboot. Two fwupd processes
consuming 100% CPU each.
--
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/log
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: appstream-glib (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1637024
Titl
This was confirmed upstream to be caused by a problem in appstream-glib.
16.10 will need to either move to 0.6.4 or backport a handful of
patches.
https://github.com/hughsie/fwupd/issues/70
** Changed in: fwupd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because
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 sim
13 matches
Mail list logo
