Description of problem: It's not a good approach to let system config tool runn under superuser account - it's a security risk. Instead each tools which needs users privileges should be divided to two parts - one which serves as privileged backend running on demand and user interface that can ask for privileged action over message bus (and ask password if needed). Once action is approved by PolicyKit, it can be processed. Every tool should be ported to use PolicyKit. How reproducible: Steps to Reproduce Actual results: System config tool has to be run under superuser account. Expected results System config tool is not runned under superuser account and asks for privileged access. Additional info Look at https://fedorahosted.org/python-slip/
Changing to block the polkit tracker directly instead of the intermediate system-config-tools cleanup tracker (which has been dead for years, so I'm closing it).