Right now if you set a property on a system user, it will be saved in a cachefile. But those cachefiles are never loaded. That seems needlessly inconsistent. In daemon.c, when a new user object has to be made (i.e. if a system user object path is requested), we should load the cachefile like we do on startup for normal users.
orginally the idea was that ListCachedUsers would return the users used to show on the login screen. Of course, that didn't really pan out. We needed to show a more exhaustive list in control-center (e.g. locked accounts), and the login screen needs to filter out system users explicitly anyway because a user can always be brought into the fold with an explicit get_user call. That's a long winded way of saying, I think I agree with you. We'll have to try removing the offending code and make sure it doesn't cause any regressions, though.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/accountsservice/accountsservice/issues/29.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.