unity-greeter .pkla file does not work consistenly on all the systems
Bug #1048522 reported by
Antti Kaijanmäki
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity-greeter (Ubuntu) |
Fix Released
|
High
|
Antti Kaijanmäki |
Bug Description
The current .pkla file does not work properly on all system.
It seems that policykit handles localauthority files with action wildcards somewhat nondeterministi
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.
Related branches
lp:~bikini-atoll-squad/unity-greeter/lp1048522
- Michael Terry: Approve
-
Diff: 56 lines (+38/-8)1 file modifieddebian/unity-greeter.pkla (+38/-8)
Changed in network-manager-applet (Ubuntu): | |
status: | New → Confirmed |
assignee: | nobody → Antti Kaijanmäki (kaijanmaki) |
tags: | added: quantal |
Changed in network-manager-applet (Ubuntu): | |
status: | Confirmed → Triaged |
importance: | Undecided → High |
affects: | network-manager-applet (Ubuntu) → unity-greeter (Ubuntu) |
tags: | added: network-manager |
description: | updated |
summary: |
- 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 |
Changed in unity-greeter: | |
status: | New → Confirmed |
no longer affects: | unity-greeter |
To post a comment you must log in.
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?