← Back to team overview

desktop-packages team mailing list archive

[Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices



Just wanted to confirm that we don't need any more investigation re:
your comment #131 ( I think that may be the largest comment # I've seen
in a LP bug ), as your latest update to bug #1524133 indicated that
you'd isolated the problem to a SIM with an expired data plan?


We should probably close this bug out when OTA8.5 is released, and then
push another update to the PPA that contains the updated patch with the
desktop crash fix ( bug #1523975 ).  I've attached yet another of the
version of the patch which just includes the additional wiredDevice NULL
check from Lorn's latest patch.


Thanks again for all the help.  Again, once the OTA8.5 update has been released, we can focus on transitioning to the connectivity API based bearer plugin for our next update.

** Patch added: "yet another update to our bearer-mgmt networkmanager patch"

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.

  Access points' "PropertiesChanged" dbus signals freeze UI on mobile

Status in Canonical System Image:
  Fix Committed
Status in Unity 8:
Status in dbus-cpp package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
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:

Bug description:
  Krillin, rc-proposed, r83

  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:

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

  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: