← Back to team overview

desktop-packages team mailing list archive

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


> I also began to see the Shutdown menu displayed every so often when
> I let the screen go off, and then woke via the power button.

That specific behavior is bug 1508563, whose fix just landed and will be
in the next rc-proposed.  It happened if unity8 was too being too slow
(because the system was loaded).

That is all great news!  I will confirm today in my neighborhood and
jump for joy if no UI freezes occur (I had tried those steps before but
was watching CPU, where spikes still happened -- which I guess is the
"slightest tick" you saw in the UI -- when a scan occurs).

I'll note that xenial has dbus 1.10, so it should have GetAllMatches if
anyone wants to try Tony's scripts without actually patching dbus.  Just
install devel-proposed instead of rc-proposed.  Of course, that will
change a lot of other things on your system.

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:
Status in indicator-network package in Ubuntu:
Status in network-manager package in Ubuntu:
Status in location-service package in Ubuntu RTM:
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: