Bug 188932

Summary: System monitoring plasmoid problem when plasmoids are locked
Product: [Unmaintained] plasma4 Reporter: Yann Ciret <yann.ciret>
Component: widget-systemmonitorAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: jwheaton, kde, martin.girard5
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Mandriva RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Yann Ciret 2009-04-06 01:33:42 UTC 
Version:            (using KDE 4.2.2)
OS:                Linux
Installed from:    Mandriva RPMs

Description of problem:
In System monitor plasmoid, sensors could be misplaced when plasmoids are locked

Version-Release number of selected component (if applicable):
plasma-applet-system-monitor-cpu-4.2.2-10mdv2009.1
plasma-applet-system-monitor-temperature-4.2.2-10mdv2009.1
plasma-applet-system-monitor-hwinfo-4.2.2-10mdv2009.1
lib64plasma_applet_system_monitor4-4.2.2-10mdv2009.1
plasma-applet-system-monitor-hdd-4.2.2-10mdv2009.1
plasma-applet-system-monitor-net-4.2.2-10mdv2009.1

Steps to Reproduce:
1. Add System-Monitor plasmoid to desktop
2. Activate CPU sensor
3. Activate DiskSpace
4. Resize applet if necessary
5. Lock the plasmoids
6. Logout
7. Login
At this step, Disk Space sensor go to the top of Plasmoid et is over the CPU sensor.
8. Unlock the plasmoids
9. Pass the mouse cursor over System Monitor plasmoid. The Disk Space sensor go back to its bottom position.
Comment 1 Petri Damstén 2009-04-09 07:24:55 UTC 
SVN commit 951378 by pdamsten:

Allow position change for applet when it is inside system-monitor main applet even if widgets are locked.
BUG:185923
BUG:188932

 M  +10 -0     applet.cpp  
 M  +1 -0      applet.h  


WebSVN link: http://websvn.kde.org/?view=rev&revision=951378
Comment 2 Petri Damstén 2009-04-09 10:00:30 UTC 
*** Bug 185923 has been marked as a duplicate of this bug. ***
Comment 3 Aaron J. Seigo 2009-05-07 02:51:58 UTC 
*** Bug 191866 has been marked as a duplicate of this bug. ***