Why this bug is still open against policykit? Yes, it was caused by some confusion about policykit design, but I think devs will be informed other way :)
I think it can be marked as 'invalid' for policykit, because bug was really in s-t-b.
Why this bug is still open against policykit? Yes, it was caused by some confusion about policykit design, but I think devs will be informed other way :)
I think it can be marked as 'invalid' for policykit, because bug was really in s-t-b.