touch-packages team mailing list archive

[Thomas Voß <1480877@xxxxxxxxxxxxxxxxxx>]

Quick update on silo 26: I'm rebuilding location-service to account
for a recent landing.
The one blocking issue is mediascanner2, which requires a rebuild,
too. It is however enabled for dual-landing
to both vivid and xenial, and we cannot easily do a vivid+o landing
with it right now. I'm working on the resolving that issue,
but it will likely take a day or two to complete.

On Mon, Nov 23, 2015 at 3:49 PM, Michael Terry
<michael.terry@xxxxxxxxxxxxx> wrote:
> I tested silo 26 + libqt5network5 from Tony's PPA and did my normal
> routine of walking out of range of my home network.
>
> It seems much better.  dbus-daemon CPU usage is down (only ~30% for a
> few seconds after initial switch to 3G and ~15% during scans after).
>
> But more importantly, stuttering is much better.  Only a couple tiny
> stutters on initial switch.  And none during scans.  I'm +100 on trying
> to land this.
>
> (My test was on a relatively-recently-rebooted phone, so maybe not the
> ideal test.  I'll try again later after a while of uptime to double
> confirm the results, but this looks good.  If I don't post again, assume
> it worked great.)
>
> --
> 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:
>   Confirmed
> Status in Unity 8:
>   New
> Status in dbus-cpp package in Ubuntu:
>   In Progress
> Status in indicator-network package in Ubuntu:
>   Incomplete
> Status in network-manager package in Ubuntu:
>   Incomplete
> Status in qtbase-opensource-src package in Ubuntu:
>   In Progress
> Status in buteo-syncfw package in Ubuntu RTM:
>   New
> Status in location-service package in Ubuntu RTM:
>   In Progress
> Status in maliit-framework package in Ubuntu RTM:
>   New
> Status in network-manager package in Ubuntu RTM:
>   Incomplete
> Status in sync-monitor package in Ubuntu RTM:
>   New
>
> 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 Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1480877

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

Status in Canonical System Image:
  Confirmed
Status in Unity 8:
  New
Status in dbus-cpp package in Ubuntu:
  In Progress
Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in buteo-syncfw package in Ubuntu RTM:
  New
Status in location-service package in Ubuntu RTM:
  In Progress
Status in maliit-framework package in Ubuntu RTM:
  New
Status in network-manager package in Ubuntu RTM:
  Incomplete
Status in sync-monitor package in Ubuntu RTM:
  New

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