Searched refs:NameOwnerChanged (Results 1 – 4 of 4) sorted by relevance
4 Subject: [PATCH] Connect to NameOwnerChanged signal when setting callback7 we could have already missed the NameOwnerChanged signal if we get a value from8 UpdateNameOwnerAndBlock. This means NameOwnerChanged callbacks will19 current name owner of the service, this means the NameOwnerChanged signal22 3. As a result, ObjectManager::NameOwnerChanged is never called while37 connecting to the NameOwnerChanged signal right away in ObjectManager39 both NameOwnerChanged (on origin thread) and SetupMatchRuleAndFilter (on64 + // NameOwnerChanged signals.89 void ObjectManager::NameOwnerChanged(const std::string& old_owner,105 void NameOwnerChanged(const std::string& old_owner,[all …]
42 Connect-to-NameOwnerChanged-signal-when-setting-call.patch
315 void NameOwnerChanged(const std::string& old_owner,
47 base::Bind(&ObjectManager::NameOwnerChanged, in ObjectManager()502 void ObjectManager::NameOwnerChanged(const std::string& old_owner, in NameOwnerChanged() function in dbus::ObjectManager