desktop-packages team mailing list archive

[Tony Espy <1480877@xxxxxxxxxxxxxxxxxx>]

And some more details, by adding 'env QDBUS_DEBUG=1' to the unity8
upstart job, I'm getting a lot more detail without having to further
modify the code.

I'm seeing "Adding rule" log statements produced by
QDBusConnectionPrivate, but no corresponding "Removing rule" logs, so
sounds like my previous theory is on track ( ie. that reference counting
may be the cause ).  That said, I'll need to add some more logging and
rebuild...

Also, while examining the DBus log, it looks like every time the plugin
sees a 'PropertiesChanged' message from the AccessPoint, it calls
"GetAll", which is pointless as all the changed properties are
transmitted with the signal...

-- 
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:
  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:
  Confirmed
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