It seems like the proposed solution is a workaround for a policykit bug. With the proposed solution, if NetworkManager adds new permission controls, unity-greeter will use the default access rights until we notice, right? Seems bad.
Could we look into fixing it at the policykit level? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1048522 Title: unity-greeter .pkla file does not work consistenly on all the systems Status in Unity Greeter: Confirmed Status in “unity-greeter” package in Ubuntu: Triaged Bug description: The current .pkla file does not work properly on all system. It seems that policykit handles localauthority files with action wildcards somewhat nondeterministically. AFAICT the file is specified according to policykit documentation, but still the file does not work as expected on all of the systems. In fact on systems where the file does not work switching the rules around has desired effect, but this breaks the systems where the original file already works. To get the file to work reliably on all the systems the wild card needs to be removed and all permissions for each action has to be specified explicitly. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-greeter/+bug/1048522/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp