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.
** Changed in: libaccounts-glib (Ubuntu) Importance: Critical => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libaccounts-glib in Ubuntu. https://bugs.launchpad.net/bugs/1393470 Title: Service cache doesn't update as services change Status in “libaccounts-glib” package in Ubuntu: New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libaccounts-glib/+bug/1393470/+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