Version: 1.0 Using KDE 4.1.96 (KDE 4.1.96 (KDE 4.2 RC1)) (using Devel) OS: Linux Installed from: Compiled sources System Monitor Plasmoid doesn't load settings I set in last sessions. I logged out and login, I see Systemmonitor Plasmoid run with default setting(all of Temperature, CPU, Network...). I'm not sure, settings may be not saved.
I can confirm this is still the case in kde 4.2. Very frustrating with the network settings as every time I logout it defaults to showing all my interfaces (even the vmnet ones).
I see the same problem. The spesialized versions, "System Monitor - CPU", "System Montor - Network", etc, does however save their settings, so a good workaround is to use those instead. Plasma also prints the following warning for each monitor embeded in the System Monitor plasmoid: plasma(7621)/libplasma Plasma::AppletPrivate::mainConfigGroup: requesting config for "System Monitor - Network" without a containment! I don't see this message if I have "System Monitor - Network" directly on the desktop, but only when it's embedded in System Monitor.
(In reply to comment #0) > Version: 1.0 Using KDE 4.1.96 (KDE 4.1.96 (KDE 4.2 RC1)) (using > Devel) > OS: Linux > Installed from: Compiled sources > > System Monitor Plasmoid doesn't load settings I set in last sessions. > > I logged out and login, I see Systemmonitor Plasmoid run with default > setting(all of Temperature, CPU, Network...). > > I'm not sure, settings may be not saved. > In KDE 4.2 on FreeBSD, I am seeing the CPU system monitor show up blank when I log in. If I remove the widget and re-add it, it works fine. It seems there is a race condition where an underlying system that this uses to find the CPU's isn't started by the time this is ready to find the CPU's.
SVN commit 930441 by pdamsten: Fix config. BUG:181378 M +1 -16 applet.cpp M +0 -5 applet.h M +6 -5 hdd.cpp M +7 -6 temperature.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=930441
*** Bug 186775 has been marked as a duplicate of this bug. ***
*** Bug 188974 has been marked as a duplicate of this bug. ***