But isn't this a sufficiently severe bug for a LTS release, considering that currenntly supported kernels cause this (so I would say it's a regression) and that when this happens the system battery is drained and the user may even hardly realise why?
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1721282 Title: upowerd/gnome-power-statistics crash; high CPU, memory consumption Status in upower package in Ubuntu: Fix Released Bug description: Not sure if necessary here since same bug is already on: https://bugzilla.redhat.com/show_bug.cgi?id=1427621 https://bugs.freedesktop.org/show_bug.cgi?id=100626 https://bugzilla.gnome.org/show_bug.cgi?id=781088 Tested on Ubuntu 16.04.3, 4.12.0-041200rc3-generic Steps to reproduce: 1. have a system with a recent kernel (4.10.x or later) 2. start gnome-power-statistics 3. go to Pprocessor tab 4. have a look at gnome-system-monitor or htop Result: - On Processor section, Wakeups tab: "Processor wakeups pers second: GDBus.Error:org.freedesktop.UPower.GeneralError: cannot enable timerstats." - High CPU usage of /usr/lib/upower/upowerd - Crash gnome-power-statistics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1721282/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
