On Wed, Dec 14, 2011 at 3:36 AM, Rajko M. 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.org

On Wednesday, December 14, 2011 09:42:27 AM Will Stephenson wrote:

On Wednesday 14 December 2011 09:24:39 todd rme wrote:

...

On Wed, Dec 14, 2011 at 3:36 AM, Rajko M. 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.

Agreed. Making it work should be a feature for 12.2 at the latest. I haven't looked at how it works in order to see if it's a simple fix for 12.1 updates.

Will

-- Will Stephenson, KDE Developer, openSUSE Boosters Team SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org I frankly consider it a critical bug since it makes policykit based administration essentially non-functional for any but the highly technical user. And once again, providing a module that doesn't work is very ugly.

Frankly 12.1 has so many issues that I am looking for a more suitable distro for my clients. And I have been placed in an ugly situation. My roommate is also one of my clients. He is an Apple fan, and I had nearly had him convinced to switch to Linux when his Mac keeled over and I backed up and integrated all his data onto a spare tower I had laying around. Unfortunately that tower is running 12.1. Though there are indeed many improvements to a variety of applications and such, it is buggy enough that he runs into them with some uncomfortable frequency. Now, besides that I'm a FOSS evangelist, transitioning him to Linux would offer innumerable advantages to him and to me in the ability for me to support the machines. If he goes and gets an iMac... I'm in a sticky situation since they are rather difficult to work on when something goes wrong. I hate having to tell my Mac clients to take their machines back to Apple. I have considered SLED, but I have already trained him up within KDE and there are no enterprise level distributions offering KDE, and SLED doesn't have a good number of the software solutions he needs or is accustomed to. /rantover -- 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