Doesn't check SupportedLocationFeatures for Can_Set
@wjt
Submitted by Will Thompson Link to original bug (#651776)
Description
Today for some reason Empathy decided it had nothing better to do than call SetLocation on all of my accounts every 5 seconds. I couldn't see why—it stopped happening before I could get much useful information. But I noticed that it doesn't check the connection's SupportedLocationFeatures at any point: it just blindly calls SetLocation().
When I looked at EmpathyLocationManager I kind of boggled because it calls tp_account_manager_prepare_async() every time it wants to update the published location, even though tp_account_manager_prepare_async() is called in _init(). I can't see why it would do this. It doesn't, however, ensure the connection objects are prepared in any way. (Does TpAccountManager ensure that at least CONNECTION_FEATURE_CORE is prepared? I can never remember.)
I guess we could grow TP_CONNECTION_FEATURE_LOCATION which would grab all the properties and monitor them for changes … heh, LocationAccessControl is rw but doesn't have change notification.
Version: 3.1.x