Service cache doesn't update as services change

[Alberto Mardegan]

libaccounts-glib caches the list of current services inside its SQLite database, along with some basic information about the service (including the provider ID).
However, if a .service file changes its <provider> element, libaccounts-glib does not detect the change and still keeps the outdated information in its DB.

One possible solution for this is to add a function like ag_account_manager_rebuild_cache() which re-reads all the .service files, and invoke this function from our "account-service" hook program.

[Thomas Strehl (strehl-t)]

Even worse, it seems a malicious app could ship a broken service file and with that corrupt the database.

[Thomas Strehl (strehl-t)]

It'll only break for the one app that ships the broken service file, so it shouldn't impact the db on a global level. Still, this is extremely annoying for devs.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Robert Schroll (rschroll)]

Note that this can cause confusion for apps that ship with a .service file. A fix may not take effect, or a breakage may not be noticed, since the old, working configuration persisted. (This latter case bit me.)