[Kernel-packages] [Bug 1698468] Re: fwupd taking 100% CPU

2018-01-05 Thread Mario Limonciello
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 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to

[Kernel-packages] [Bug 1698468] Re: fwupd taking 100% CPU

2017-08-01 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fwupd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1698468

[Kernel-packages] [Bug 1698468] Re: fwupd taking 100% CPU

2017-06-22 Thread Greg d'Eon
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:

[Kernel-packages] [Bug 1698468] Re: fwupd taking 100% CPU

2017-06-20 Thread Kai-Heng Feng
** Also affects: fwupd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1698468 Title: fwupd taking 100% CPU Status in fwupd package

[Kernel-packages] [Bug 1698468] Re: fwupd taking 100% CPU

2017-06-20 Thread Greg d'Eon
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 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in

[Kernel-packages] [Bug 1698468] Re: fwupd taking 100% CPU

2017-06-19 Thread Joseph Salisbury
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