← Back to team overview

desktop-packages team mailing list archive

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


In parallel there has been some discussions on bug #1404188 about
dropping the usage of network manager backend, even though unlikely in
vivid-overlay unless seen as a bullet proof option.

If you want to try out how that would look like, install the silo 032 on
rc-proposed but _without_ upgrading the ubuntu-touch-session there. Or
if you upgrade ubuntu-touch-session, just move
/etc/profile.d/qt_networkmanager_bearer.sh away and reboot. The silo
includes also some networking bug fixes besides making the bearer
selectable but that's not relevant to this bug.

The reason for keeping network manager bearer has been that with that Qt
knows about switching between 3G and WiFi. If you use only generic
plugin, have both wifi and 3g enabled and disable wifi, QNAM:s fall
dead. Or if you use 3G only and enable wifi, 3G might be continued to be
used. If those problems could be resolved on lower levels for example
(or if they already are, the NM bearer enabling was done over a year
ago), we could switch to the generic plugin.

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 Unity 8:
Status in indicator-network package in Ubuntu:
Status in network-manager package in Ubuntu:
Status in qtbase-opensource-src package in Ubuntu:
Status in buteo-syncfw package in Ubuntu RTM:
Status in location-service package in Ubuntu RTM:
Status in maliit-framework package in Ubuntu RTM:
Status in network-manager package in Ubuntu RTM:
Status in sync-monitor 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: