[Bug 187154] Add kuser, ksystemlog, kinfocenter and ksysguard as kcm modules to be accessible via KDE4 system-settings

[Christophe Giboudeaux]

https://bugs.kde.org/show_bug.cgi?id=187154


Christophe Giboudeaux <cgiboudeaux at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cgiboudeaux at gmail.com




--- Comment #21 from Christophe Giboudeaux <cgiboudeaux gmail com>  2009-03-15 16:16:32 ---
- KDM belongs to KDE
- Samba affects the way the kio_smb will work
- The power manager kcm will tweak KDE performances depending on the battery
state (don't just look at the icons, also read the text). These settings only
affect the user.

How does Kuser affects the KDE usage ? The answer is quite simple, it doesn't.

Also note that adding a user, group, changing the groups a user belongs to, his
home directory or login shell is _not_ something a novice user should do.
KUser won't change anything, a novice user has the same risk to become unable
to open a session.

> I think the most important thing is in this matter is that it is useful to have them in system-settings. 

and I guess you never heard about usability.

system Monitoring has nothing to do in KDE System Settings.

Ask your distribution to provide such tools or choose one which already
provides such tools (eg. OpenSuse).

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.