On Thu, 2014-10-02 at 12:52 +0300, Alberto Mardegan wrote: > By default, all our plugins add "unconfined" to the account's ACL as > soon as the account is created, in order to allow all unconfined > processes to use the account. But the UbuntuOne plugin was not doing that.
But how would adding "unconfined" on new account creation solve the problem who already have accounts on the system? There's no way for us to show an appropriate error message to the user, asking them to delete their account and create a new one, because there's no way to differentiate this error from a general system permissions problem. Why can't the extension treat "unconfined" as the same as an empty ACL here? It seems like this would be the best immediate solution, to me. -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
