Lets try testing with the Plasmoid viewer.

Code: Select all

plasmoidviewer sm_cpu

XiniX wrote:Whoops, sorry, I was utterly confused....

My _network_ plasmoid works OK. It is my _CPU_ plasmoid that does not work...

In Ksysguard, both CPU and Network work OK!

Sorry about that...

If you CPU plasmoid is the problem try this: "apt-get install lm-sensors" (solved this issue for my box). In addition I had to use "sensors-detect" to find the correct kernel-modules (and load them to get my temperature sensors to work in the temp plasmoid.

About the network plasmoid: that one worked out of the box

fejf wrote:If you CPU plasmoid is the problem try this: "apt-get install lm-sensors" (solved this issue for my box).

Hmm, it is already installed....

bcooksley wrote:Lets try testing with the Plasmoid viewer.

Code: Select all

plasmoidviewer sm_cpu

No different output whatsoever. Running 'plasmoidviewer sm_net' gives the same output (findServiceByDesktopPath not found), but the network plasmoid works for me, and the CPU plasmoid doesn't.

bcooksley wrote:Lets try testing with the Plasmoid viewer.

Code: Select all

plasmoidviewer sm_cpu

This opens a new window with a working CPU graph. When I try it wth sm_net, a window opens but the large net icon fills the window since there are no networks defined as far as it is concerned. If I open the configuration window, there are no networks listed just like the other way.

Lets try removing the KSysGuard configuration:

Code: Select all

rm -rf $KDEHOME/share/config/ksysguardrc
rm -rf $KDEHOME/share/apps/ksysguard

bcooksley wrote:Lets try removing the KSysGuard configuration:

Code: Select all

rm -rf $KDEHOME/share/config/ksysguardrc
rm -rf $KDEHOME/share/apps/ksysguard

Well, I think this helped point to a problem. I was getting error messages about the files not existing when I tried this. I was able to determine that KDEHOME is not defined. By searching various web sites I found other people commenting the same thing regarding Debian when trying to use KDE4. I have actually been using KDE4 since 4.0 first appeared in experimental. I have been upgrading occasionally since then. This makes me think Debian has something misconfigured with users trying to upgrade from kde3 to kde4 especially when carrying forward from early KDE4 packages.

Unfortunately, I was not able to solve the problem. I tried a few things that did not work.I have a .kde and.kde4 directory in my home folder and it looks like my installation of KDE uses both for writing files based on the time stamp.

I made a brand new user and logged in so the KDE configuration would be created using all of the defaults as Debian defined them in 4.2. I still get no working Network plasmoid or have network interfaces listed in the plasmoid configuration or the ksyguard sensor list.

I then defined KDEHOME to be ~/.kde4 in /etc/profile which seemed to be the common suggestion to solve the Debian issue. This did not help when logging in as the new user or as me.
I deleted both files you suggested and logged in to create them again. This did not help.
I defined KDEHOME to be ~/.kde in /etc/profile and this also did not help the network problem for either the new user or my account even after again removing the files you mentioned above and logging in again.

One problem was solved by defining KDEHOME to be ~/.kde. I was getting an error every time I logged in from Akonadi trying to migrate some old settings. I did not care much about this so had not tried to solve it. By defining KDEHOME to be ~/.kde this error went away when logging in. I doubt it is relevant to this network plasmoid problem, but thought I would mention it.

Any hints here that are useful to point to a problem?

By the sounds of it the ksysguard package is broken. Could you both please post the versions you have installed? ( hopes for different versions )

bcooksley wrote:By the sounds of it the ksysguard package is broken. Could you both please post the versions you have installed? ( hopes for different versions )

$ ksysguardd --version
ksysguardd 4
(c) 1999, 2000, 2001, 2002 Chris Schlaeger
(c) 2001 Tobias Koenig
(c) 2006-2008 Greg Martyn
This program is part of the KDE Project and licensed under
the GNU GPL version 2. See http://www.kde.org for details.
Usage: ksysguardd [-d] [-i] [-p port]

$ ksysguard --version
Qt: 4.4.3
KDE: 4.2.00 (KDE 4.2.0)
System Monitor: 4

My network monitor plasmoid is also not working. I have a connection via eth0, but I can't select it in the configuration dialog of the plasmoid: it's empty. In plasmaengineexplorer, no "network" data engine shows up.

I'm using Gentoo's KDE 4.1.2 packages.

Finally revisited this thread and found out what my problem was. Turns out ksysguardd version 3.5.9 was still installed. Replaced it with the KDE 4.2 version and now all is honky dory.....

I am still facing this problem. There are no entries in network monitor plasmoid.

Diagnosis info based on the entries so far
--
solid backend - Network Management

which ksysgaurd - /usr/bin
which plasma-desktop - /usr/bin

plasmoidviewer km_net WORKS CORRECTLY. and I can see the network graphs.

ksysgaurd does not show all interfaces sensors. eth0 and l0 are present but wlan0 is not present. Still the graph responds correctly to any activity on wlan0, Wierd!!

ksysguard and ksysguardd version both are version 4
kde version 4.3
Archlinux using kdemod packages.
----

Till now I have very little problems with kde 4.3. If anybody can help out with this issue, I would be grateful

Thanks
Narendra

If you create a new user, does the problem occur there?
If it does, please file a bug at bugs.kde.org

If it does not, please clear the contents of ~/.kde4/*-(hostname)/ outside of a KDE session.