Just a quick update on my debugging. I've verified that the NM bearer plugin's qnetworkmanagerengine class is receiving the 'AccessPointRemoved', is matching them correctly in it's saved list, and is called delete on the QNetworkManagerInterfaceAccessPoint instance. The associated destructor is called, and my new disconnect() method is called, which succeeds.
All that aside, the rules are still piling up, so something else is wrong. I took a quick look at the DBusConnection code, and it looks like the signal matches are reference counted, so it's possible that the count is never reaching zero, so the rule isn't actually released... ( see qdbusconnection.cpp and qdbusintegrator.cpp ). -- 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: 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
