I upgraded to polkit-0.116 and then was not able to use NetworkManager's nmappet : attempts to connect to wifi resulted in the error "Not authorized to control networking". System logs (/var/log/messages) are full of: May 21 00:29:46 teres polkitd[12089]: Started polkitd version 0.116 May 21 00:29:46 teres polkitd[12089]: Loading rules from directory /etc/polkit-1/rules.d May 21 00:29:46 teres polkitd[12089]: Loading rules from directory /usr/share/polkit-1/rules.d May 21 00:29:46 teres polkitd[12089]: Finished loading, compiling and executing 5 rules May 21 23:29:46 teres dbus-daemon[1772]: [system] Successfully activated service 'org.freedesktop.PolicyKit1' May 21 23:29:47 teres dbus-daemon[1772]: [system] Activating service name='org.freedesktop.PolicyKit1' requested by ':1.2' (uid=0 pid=1844 comm="/usr/sbin/NetworkManager --pid-file /run/NetworkMa") (using servicehelper) May 21 00:29:47 teres polkitd[12101]: Started polkitd version 0.116 May 21 00:29:47 teres polkitd[12101]: Loading rules from directory /etc/polkit-1/rules.d May 21 00:29:47 teres polkitd[12101]: Loading rules from directory /usr/share/polkit-1/rules.d May 21 00:29:47 teres polkitd[12101]: Finished loading, compiling and executing 5 rules May 21 00:29:47 teres dbus-daemon[1772]: [system] Successfully activated service 'org.freedesktop.PolicyKit1' May 21 00:29:47 teres dbus-daemon[1772]: [system] Activating service name='org.freedesktop.PolicyKit1' requested by ':1.2' (uid=0 pid=1844 comm="/usr/sbin/NetworkManager --pid-file /run/NetworkMa") (using servicehelper) repeating every second. Downgrading to polkit-0.115-r3 solved the problem right away. Polkit was built with USE="consolekit introspection nls pam -elogind -examples -gtk -jit -kde (-selinux) -systemd -test". I am on arm64 laptop, use openrc. It is not quite clear to me how to debug this, but I would be happy to provide additional information.
Created attachment 577438 [details] emerge --info
are you still hitting this with 0.116-r1 and an updated system?
Hi. I updated the system, switched to systemd, and I do not observe this bug any more. I'm marking it as resolved.