This issue lasts for a long time, maybe from openSUSE 11.3, at least on my laptop.
If you click to open YaST2 (Administrator Settings or Install Software), it will lag for 5 minutes with a refreshing icon on your task manager bar for about 30 seconds. Then shows a kdesu window to input password. After filling in, the kdesu window freeze there for about 2 minutes, then disappear. After a long time, while you almost forgot you had done those procedures, YaST window turns out. The interval might be as long as 10 to 15 minutes.
So does NetworkManager. You can’t modify system connection because at first it’ll show you a kdesu window, but after you input password it’ll lag to timeout. You also can’t save after modifying a system connection ( In a few chances you can survive the first kdesu), because the second kdesu window there will certainly lag long enough to “timeout” system policy.
For YaST2, I have to be quick enough to click and open TWO YaST2 instances at the same time. while the first lags as it should, the second will be normal. Almost when the second yast2 show you a submenu main window like Install Software, the first kdesu just turns out, then you can close the 1st YaST there.
for NetworkManager, you have to manually delete it under /etc/NetworkManager/system connections using root acco ( you can’t delete it in NetworkManagement Plasmoid for the same kdesu reason) and add a same-but-not-system-connection connection.
I would like to know why this happen, and how can I get out from this. it seems to be a policykit or sudoers thing, anyway it must be a privileges’ problem.
PS: if your normal user is enough password protected, why not YaST implements a Privileges Center which may be placed under Security Center, to enable users decide which system-wide (root) action is guaranteed and away from root password input every time or a long enough period like one month, in a user friendly manner like “open YaST2: on/off”, instead of modify /etc/polkit-default-privs.standard or sudoers in a coder-centralized “org.freedesktop.NetworkManager.enable-disable-network: auth-admin” way?