Mailinglist Archive: opensuse-factory (883 mails)

[Ilya Chernykh <anixxsus@xxxxxxxxx>]

On Thursday 03 May 2012 12:03:43 Stefan Brüns wrote:
>

> > ===
> > kdebase4-workspace-ksysguardd should be used by KDE 3 too.  It is 
> > maintained, backwards-compatible with KDE 3 clients and does not have any 
> > external dependencies.  Due to a packaging error, ksysguard is currently in 
> > the kdebase4-workspace-ksysguardd package but I will get this removed now.
> > ===
> >
> > But this is NOT true! KDE3 is not compatible with KDE4's ksysguardd, and 
> > the process table in system monitor
> > is not displayed properly when KDE4's ksysguardd is running. At the same 
> > time, both KDE4 and KDE3 work
> > well with KDE3's ksysguardd.
>
> In general both versions of ksysguardd are compatible, and while ksgdd4 has 
> gained some additional columns in the process table, the parser should read 
> the column headings and ignore any unknown columns.
>
> There is one caveat though: ksgdd4 uses number of ticks to report the runtime 
> (sys/user..) of the process, and the frontend has to do the math to get the 
> load per process, whereas v3 reports the load directly. This was changed, as 
> the corresponding code was broken in v3,

Works here well.

> and the maintainers decided it is cleaner to do this in the frontend. 
>
> So there are two possibilities:
> 1) stick with kde3s version - Implications: broken load reporting for all 
> clients, missing information for newer clients

Where can I see the broken load reporting?

> 2) use kde4s version - Implications: Load reporting on ksysguard3 does not 
> work without forward porting.
>
> I strongly prefer the second approach.

With KDE4 ksysguardd KDE3's process table SIMPLY DOES NOT WORK! It just 
flickers at 10 times per second,
similarly to what happens when no ksysguardd installed at all.

--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx