[Bug 1637024] Re: fwupd consuming very high cpu after startup/login

2018-06-30 Thread Mathew Hodson
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, 22 Dec 2016 20:10:42 +0100

** Changed in: appstream-glib (Ubuntu)
   Status: Confirmed => Fix Released

-- 
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

[Bug 1637024] Re: fwupd consuming very high cpu after startup/login

2018-03-06 Thread Robert Ancell
** 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 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

[Bug 1637024] Re: fwupd consuming very high cpu after startup/login

2017-07-15 Thread Mathew Hodson
** 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 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


[Bug 1637024] Re: fwupd consuming very high cpu after startup/login

2017-07-15 Thread Mathew Hodson
** 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 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


[Bug 1637024] Re: fwupd consuming very high cpu after startup/login

2017-02-20 Thread Ubuntu Foundations Team Bug Bot
** 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.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


[Bug 1637024] Re: fwupd consuming very high cpu after startup/login

2017-02-20 Thread Robert Ancell
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 instead
of a YAML file).

I'd prefer to try this patch first rather than do a full update to the
latest.

[1] https://github.com/hughsie/appstream-
glib/commit/538da2d8e078de3ec7f38b56e4ddadd1da401c4d

-- 
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


[Bug 1637024] Re: fwupd consuming very high cpu after startup/login

2017-02-20 Thread Robert Ancell
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 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


[Bug 1637024] Re: fwupd consuming very high cpu after startup/login

2017-02-20 Thread Iain Lane
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 too and not all the fixes come
with LP bug reports of course. But see linked bug report on github -
it's a fair point that providing QA on random release + patches is not
that fun a task for an upstream to do.

** Changed in: appstream-glib (Ubuntu)
 Assignee: Canonical Desktop Team (canonical-desktop-team) => Robert Ancell 
(robert-ancell)

-- 
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


[Bug 1637024] Re: fwupd consuming very high cpu after startup/login

2017-02-17 Thread Brian Murray
** 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 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


[Bug 1637024] Re: fwupd consuming very high cpu after startup/login

2017-02-16 Thread Graham Mitchell
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/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


[Bug 1637024] Re: fwupd consuming very high cpu after startup/login

2017-02-16 Thread Launchpad Bug Tracker
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

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


[Bug 1637024] Re: fwupd consuming very high cpu after startup/login

2016-11-16 Thread Mario Limonciello
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 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


[Bug 1637024] Re: fwupd consuming very high cpu after startup/login

2016-10-27 Thread Mario Limonciello
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