On Wednesday, December 14, 2011 09:24:39 AM todd rme wrote:
On Wed, Dec 14, 2011 at 3:36 AM, Rajko M. <rmatov101@charter.net> wrote:
On Monday, December 05, 2011 06:11:05 PM Roger Luedecke wrote:
The policy kit modult for System Settings is broken. I wanted to change the packagekit permissions so it wouldn't need root to do updates or install software. Can we get this fixed? Its a pretty important thing to have working, not to mention its rather sloppy to have an unusable module.> Are you shure that you want that?
Enabling plain user to install stuff in system area is not allowed even in Windows.
You would still need administrator access to change anything you don't have permissions for. The problem is that changing things you do have permissions for, changing things with administrator access, or even running the kcm module as root, any change you make to the settings fails silently. There is not even a warning that the settings will not take affect, it shows the settings being changed, but they really aren't, and if you leave the kcm module and come back the settings have reverted.
If the kcm module shouldn't exist, then it should be removed. I personally think it is essential given the reliance on policykit in so many areas right now. But having a kcm module that acts like it works but doesn't seems like a bad solution to me.
-Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.orge Precisely. Regardless of however I may like to set things, a broken module is sloppy at best. If the module supplied the ability to authenticate based on the presence of falafel I should be able to set that if the module is there and provides the function. -- Roger Luedecke openSUSE Ambassador Riverside, California ***Looking for C++ Mentor*** -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org