[kde-linux] Another KDE 4.x print problem?

James Tyrer jrtyrer at earthlink.net
Wed Nov 4 21:26:41 UTC 2009

Duncan wrote:
> (b) tafka-ksysguard won't let you configure your own worksheet as the
>  default worksheet started at launch.  (IIRC, ksysguard didn't either
> tho I'm not sure on that, but in any case the ksysguard kicker applet
> used its own separate config, which the user could setup as desired,
> and wonder of wonders, the thing actually /obeyed/ the user
> configuration!) While I was still using it, I had to rename the
> hard-coded tasklist sheet, replacing it with my own sheet of
> plotters, so I'd get the plotter sheet displayed at each launch and
> could thus monitor my system.
This worked for me in KDE-3.5.  I added an additional worksheet.  In
KDE-4, I replaced the SystemLoad sheet and that works, but it will not
load additional sheets.


> (d) Possibly due to the same root issue, tafka-ksysguard in auto mode
>  defaults to a 1.0 max when there's zero or very low activity (fine
> so far, but...), but when the value goes above one, the plotter won't
> change the (automatic) max until it hits 2.0.  Thus, the plot is off
> the graph between the ranges of 1.0 and 2.0, until it reaches 2.0, at
> which point the plotter starts auto-ranging as it should.  The place
> this was most noticed was on my load average graphs.  Normal system
> load-average is well under 1.0, typically 0.05 to 0.3 on my system.
> When I started a multi-job compile or something else that increased
> load average, I was flying blind as it headed over 1.0, until it hit
> 2.0 at which point things worked as they should.
The "Load Average" problem is fairly simple.  It reads the file, sets 
the values in the file, then changes them to 0 - 1.0.  The code was 
simply written wrong.

I have to wonder, does anybody do any basic TQM testing.  Or, do they 
just write the code, commit it, and wait for bugs?

James Tyrer

Linux (mostly) From Scratch

More information about the kde-linux mailing list