Bug 190523

Summary: System Monitor plasmoid can't remember its size and config
Product: [Unmaintained] plasma4 Reporter: Nicolas Bigaouette <nbigaouette>
Component: widget-systemmonitorAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: redm
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Nicolas Bigaouette 2009-04-24 16:45:06 UTC 
Version:            (using KDE 4.2.2)
Compiler:          gcc 4.3.3 x86_64-unknown-linux-gnu ./configure --prefix=/usr --enable-shared --enable-languages=c,c++,fortran,objc,obj-c++,treelang --enable-threads=posix --mandir=/usr/share/man --infodir=/usr/share/info --enable-__cxa_atexit --disable-multilib --libdir=/usr/lib --libexecdir=/usr/lib --enable-clocale=gnu --disable-libstdcxx-pch --with-tune=generic
OS:                Linux
Installed from:    Unspecified Linux

I've put System Monitor plasmoid on my desktop. I set it to show cpu (usage and temperature) and disk space. I then lock the widgets and logout. On login back, the widget lost its specific size I set it to and its configuration for disk (I don't want to display _all_ partitions, only some main ones).
Comment 1 Aaron J. Seigo 2009-05-07 02:42:22 UTC 
SVN commit 964625 by aseigo:

forward signals, get the saving correct
BUG:190523


 M  +15 -3     system-monitor.cpp  
 M  +1 -0      system-monitor.h  


WebSVN link: http://websvn.kde.org/?view=rev&revision=964625
Comment 2 Petri Damstén 2009-06-04 08:36:52 UTC 
*** Bug 195132 has been marked as a duplicate of this bug. ***
Comment 3 Michael Reiher 2009-07-05 19:56:44 UTC 
This is still or again broken in 4.3rc1 (Kubuntu Jaunty packages).

Btw. with 4.2.4 I noticed a difference when logging out of KDE with or without widgets being locked. In the former case settings were saved, but not in the latter. Now in neither case settings are saved.

This applies at least to the Hard Disc part of System Monitor.

I guess this should be reopened ... I just don't know how ...