I'm unable to reproduce this issue at home. It could be that it has to do with the sheer number of access-points in your location, which obviously would cause more updates to LastSeen timestamp for each accesspoint, and more AP changes signals.
Is NetworkManager itself spinning? It would be useful to have an excerpt of top; as well as a full debug log for NetworkManager when this happens. A strace of NetworkManager could be useful too, since dbus- daemon speaks to a lot more applications. To enable debugging in NetworkManager, edit the /etc/init/network-manager.conf file and add to the exec NetworkManager line: --log-level=debug --log-domains=CORE,WIFI,WIFI_SCAN -- 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/1394204 Title: dbus daemon spinning with NM AP properties change event Status in “network-manager” package in Ubuntu: Incomplete Bug description: I am consistently seeing this in the Bluefin office this week Mako running 133 Phone gets warm in pocket, wake up the phone and attach top shows dbus-daemon at 100%+ cpu and network-manager next at 10-20% It never quiets own, at least not for over 5 mins 3g data is turned off Cellular is roaming to local carrier fwiw Seems to happen whenever I leave the AP coverage, whether I return or not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1394204/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
