desktop-packages team mailing list archive

[Pat McGowan <pat.mcgowan@xxxxxxxxxxxxx>]

** Changed in: canonical-devices-system-image
       Status: New => Confirmed

** Changed in: canonical-devices-system-image
    Milestone: None => backlog

** Changed in: canonical-devices-system-image
     Assignee: (unassigned) => Pat McGowan (pat-mcgowan)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1537668

Title:
  upower charge history doesn't update when device resumes from suspend

Status in Canonical System Image:
  Confirmed
Status in upower package in Ubuntu:
  New

Bug description:
  mako rc-proposed/ubunut 348

  Possible one reason of the symptoms observed in bug 1471913

  In some cases, apparently when the state of the device changes and the
  device is immediately suspended, upower history stops being updated
  and results in graphs like the one attached (ignore the sudden drop
  then jump between 5:00AM and 10:00AM, investigation is still ongoing)

  In the history file attached, the history stops on Sun, 24 Jan 2016
  09:36:50 GMT (1453628210) It corresponds to the state change of the
  device (charging -> discharging) around the same time (1453628284 -
  Sun, 24 Jan 2016 09:38:04 GMT in power.20160124-103548.csv)

  Then if you plug the device to a charger and unplug it but don't
  suspend it the update of the history resumes normally (around
  10:00PM). The graph shows the charge decreasing linearly (which is
  wrong, it should look like the graph history-from-sysfs.png which is
  based on battery/capacity sysfs entry)

  The attached screenshot shows the network 4G data is available but
  doesn't connect as shown in the indicator.

  Possible Test Case:
  1. Disable main sources of wakeup (bt, wifi, location, set airplane mode on)
  2. plug it to a charger for a short time (15min or so), but don't fully charge it
  3. unplug the DUT and press the power button to suspend it
  4. wait several hours without waking up the device.

  Actual Result
  The history is not updating anymore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1537668/+subscriptions