** Description changed:
- When a mobile broadband connection is stored system wide with a pin code
- the user is not able to activate the connection from the greeter even
- though the user has network-control permission.
+ The current .pkla file does not work properly on all system.
- [expected result]
- The user is able to active the system wide mobile broadband connection.
+ 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.
- [actual result]
- Upon activation an error dialog is shown: "Not authorized to control
networking."
+ 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.
** Summary changed:
- the user is not able to activate system wide mobile broadband connection
inside the greeter
+ unity-greeter .pkla file does not work consistenly on all the systems
** Also affects: unity-greeter
Importance: Undecided
Status: New
** Changed in: unity-greeter
Status: New => Confirmed
** Branch linked: lp:~bikini-atoll-squad/unity-greeter/lp1048522
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048522
Title:
unity-greeter .pkla file does not work consistenly on all the systems
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-greeter/+bug/1048522/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
