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

[Angel Blue01]

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





--- Comment #15 from Angel Blue01 <angel_blue_co2004 yahoo com>  2009-03-15 00:25:33 ---
(In reply to comment #14)
> a)  Ksystemlog. 
> 
> 1.Kgrubeditor and kernel. You see in kgrubeditor wich kernel is active as a
> booting one and then in ksystemlog you monitor it's logs because of your system
>  hung or you want to check kernel logs and you can check in kgrubeditor witch
> kernel is booted as you prefer.
> 2.Samba - you set samba shares trough system-settings, not working, view logs
> trough ksyslog then repair samba.
Logs should have a quick way to start the application that coud be used to fix
the error, Samba's a good example.
> b).Ksysguard. 
> 
> 1.Sometimes your kde services runing in the kde4's background are crashing, you
> can check in system-settings services manager which kde services are set to run
> then run ksysguard to check are they are present or crashed.
And KDE already has a service manager in systemsettings, conveniently nearby
from ksysguard if they are both in systemsettings.

> c).Kinfocenter .
> 
> 1.Your graphic card is not working, no kwin 3d effects, you can check in
> kinfocenter opengl info - is it installed and present there. Then install
> drivers and set kwin working after X restart.
> 2.Audio settings problem, you are newbie, you don't know how to get your sound
> card info via command line, you open kinfocenter get there info about sound
> card or graphic card, check out forum then install for example oss or fglrx
> then configure it trough system-setting
> 
Even better would be if distros put their hardware management tools in
systemsettings, so it's just another click to get to the right program to
configure them.

systemsettings already has a display manager, but kinfocenter provides the big
picture of your whole system -it might be that your BIOS settings needs to be
changed (in CMOS setup of course) to give more RAM to video memory usage (if
you have an onboard video card).

> a) Has to know how to read (READ WORDS) not has to know about system logs, but
> if earlier the newbie will discover system logs - better for him, don't you
> think so?
Yes! And there wouldn't be a need to go anywhere unfamiliar to find the logs,
by sharing systemsettings as the starting point, that's one less barrier to
getting the user into a part of the system's configuration that might be new to
them.
> b) Know about System processes - yes, alt control delete in windows and
> intelligent people can do with windows taskmanager.exe tabs? So by the analogy
> lets find something familiar to taskmanager.exe in linux the newbie thinks.
Windows doesn't have taskmngr.exe in its Control Panel, but as a Windows admin
I've sometimes wished it was, next to all the other system tools.
> You are wrong ksysguard was one of the first application I started to find when
> I first installed Mandrake 10.0 few years ago (my first was Red hat 9 with
> gnome ;-) - I miss the hat by the way ;)
It was mine too when I started using Linux a year and a half ago, programs
crash in all OSs, task manager is the type of program that needs to be easy to
find.
> You are talking about weekend users. Weekend users use windows. They are
> frightened when I call linux ;-). If you start with linux - you have two ways
> fight with small system problems ;-) or give it away. If you stay with linux
> sooner or later you will have to use ksysguard, then kinfocenter and then
> ksyslog. Ksyslog I think at the end of the list, why at the end, because newbie
> doesn't know that there is such a thing as ksyslog. If ksyslog will be visible
> in system-settings the newbie may start to be interested with this, discovering
> after some time how useful tool it is, even without options to set settings!
> ;-)
Exactly, as I said above, having them all together is one less barrier to
discovering these tools. It definitly helped me when I first used Windows 2000
that the Windows log viewer was right next to the service manager and the task
scheduler (equivalent to cron).
> 
> > Assuming partitionmanager is a kcm: while you do real partition work (eg
> > resizing, creation, etc), you cannot do any other configuration from the
> > same application. IMHO this should really bad.
> 
> I meant in my post that there is no system-settings entry for partitionmanager.
> It is installed on my system. 
And this one too is also found next to the log viewer and other system tools in
Windows.

To reiterate there should be one place to go for all the system utility needs.
There's another wishlist item here on bugs.kde.org for make systemsettings more
of a shortcuts based system where applications can put shortcuts to themselves
right where the user expects to find them.

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