On 10/12/2010 11:41 AM, kanenas@hawaii.rr.com wrote:
WHY is something as basic as this so contorted and so difficult to accomplish? And, the really maddening shtuff, WHY is the apparent straightforward process still allowed to proceed without error messages, thus giving one the false security that the task has actually been accomplished? at the absolute very minimum, let the default be such that only if one changes it and then tries to change it back the issue arises. sometimes even when things are not right, simple common sense can still avoid problems. all, please do *not* build on this another kde4 basher thread. all i tried to do is point something that is too general for a bug report, yet it needs fixing asap. d.
Well first, I think there are two problems here. One is lack of documentation. Two is the installation of tools like this by default on accounts that can't use them. I don't think this second bit is entirely a KDE4 issue. But consider that Opensuse (and kde in general) has no way of knowing which users are to be eligible to use these tools, and at what level (Notify only, silent install, or download but don't install). There is no why to know in advance which users have roots password tucked away in their head. The vast majority of linux installs have exactly ONE user anyway. Ubuntu assumes the first user account should be added to the sudoers list to manage the machine. (This can be over-ridden, and many argue that the assumption is a trap for the unwary, but there it is anyway). Unless or Until OpenSuse embraces sudo as the normal way of doing system tasks and integrates this into the normal installation and requires that each new user added to the system is explicitly added to the sudo list, there doesn't seem to be an easy way out. In the absence of consistent use of the sudo, and sudoers, there is no way for KDE to know which users should or should not be allowed to run updater or file manager super user mode, or konsole super users mode. So I don't think you can blame KDE entirely when it has no method of determining which passwords a user might hold. You might want to suggest a multi-user install option with some mechanism for KDE to hook into when start up options and menus are constructed. Perhaps management of this type of install could be better integrated into yast. -- _____________________________________ At one time I had a Real Sig. Its been downsized. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org