desktop-packages team mailing list archive

[Thomas Voß <1480877@xxxxxxxxxxxxxxxxxx>]

Thanks for the graphs. One thing that stands out is the time that the
system stays active when occasionally waking up from deep sleep (right
hand side of the graph).
Do you have the raw data producing those graphs handy?

Thanks,

  Thomas

On Wed, Dec 9, 2015 at 1:23 AM, Selene Scriven
<selene.scriven@xxxxxxxxxxxxx> wrote:
> Is it possible that this fix might cause a phone to wake up more often,
> or to stay awake longer?  I'm seeing weird idle power behavior ever
> since this fix landed in krillin rc-proposed 196.
>
> Before: ~9 mA
> http://people.canonical.com/~platform-qa/power-results/2015-12-08_03:19:30-krillin-195-power_usage_idle/graph.png
>
> After: ~35 mA
> http://people.canonical.com/~platform-qa/power-results/2015-12-08_07:36:16-krillin-196-power_usage_idle/graph.png
>
> Here's the commit log for 196:
>
> http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-
> proposed/196.commitlog
>
> Arale results look fine.  I don't know why krillin is different, but I'm
> only seeing this behavior on krillin when wifi is connected...  and this
> bug fix is a likely suspect.  I don't see additional forks or crashes in
> the test logs, which suggests the issue is probably caused by a long-
> running process.
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1480877
>
> Title:
>   Access points' "PropertiesChanged" dbus signals freeze UI on mobile
>   devices
>
> Status in Canonical System Image:
>   Fix Committed
> Status in Unity 8:
>   New
> Status in dbus-cpp package in Ubuntu:
>   In Progress
> Status in network-manager package in Ubuntu:
>   Incomplete
> Status in qtbase-opensource-src package in Ubuntu:
>   Fix Committed
> Status in dbus-cpp package in Ubuntu RTM:
>   Fix Released
> Status in location-service package in Ubuntu RTM:
>   Fix Released
> Status in network-manager package in Ubuntu RTM:
>   Incomplete
>
> Bug description:
>   Krillin, rc-proposed, r83
>
>
>   DESCRIPTION:
>   I've been trying to track down the cause of the occasional UI freezes on my Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I get a burst of "PropertiesChanged" signals in dbus-monitor
>
>   Here's a log of what's shown in dbus-monitor:
>   http://pastebin.ubuntu.com/11992322/
>
>   I'd guess the problem is in the code that actually catches the signals
>   and acts accordingly.
>
>   HOW TO REPRODUCE:
>   1) Move to a place where many wifi hotspots are available
>   2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
>   3) Use the device while keeping an eye on dbus-monitor output
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions

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

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Fix Committed
Status in Unity 8:
  New
Status in dbus-cpp package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Fix Committed
Status in dbus-cpp package in Ubuntu RTM:
  Fix Released
Status in location-service package in Ubuntu RTM:
  Fix Released
Status in network-manager package in Ubuntu RTM:
  Incomplete

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

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