Steps to reproduce the issue:

pkcheck --action-id org.freedesktop.network-manager-settings.system.modify --process 1863 --allow-user-interaction

(use some pid of your process there instead of 1863) and instead of typing in the password, run that command again in another terminal.

Actual result: second pkcheck command fails with "not authorized"

Expected result: second pkcheck command blocks until the authorization from the first pkcheck command completes, then returns the same result as the first command


Basically, if there's an authorization request already in progress for a specific privilege, it's pretty inconvenient for subsequent requests for that same privilege to actually return before the authorization is done and before the first auth request completes.  That means the client application has to serialize all authorization calls for the same privilege internally.  Which is icky; I guess I had expected polkit to do that for me...

Is having polkit internally serialize the auth requests an acceptable proposal for polkit behavior?  Makes it a lot easier on the app writers.