Bug 315119 - "Memory Status" widget shows error on startup if "System Load Viewer" widget is active
Summary: "Memory Status" widget shows error on startup if "System Load Viewer" widget ...
Status: RESOLVED DUPLICATE of bug 318976
Alias: None
Product: plasma4
Classification: Unmaintained
Component: widget-systemmonitor (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-14 10:19 UTC by sparhawk
Modified: 2013-09-02 23:21 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description sparhawk 2013-02-14 10:19:14 UTC
If you have both the "Memory Status" widget and the "System Load Viewer" widget in a panel, the "Memory Status" widget will show an error on startup. There is no data shown on it, and it displays "no data". Attempting to configure the widget shows there is no RAM present. If I then delete the widget and re-add it, it works fine.

Alternatively, if I remove the "System Load Widget" then reboot, the "Memory Status" widget starts fine.

Reproducible: Always

Steps to Reproduce:
1. Put the "Memory Status" widget and the "System Load Viewer" widget in a panel.
2. Reboot
Actual Results:  
The "Memory Status" widget shows an error.

Expected Results:  
The "Memory Status" widget should work.

Another thread discussing the bug here: http://forum.kde.org/viewtopic.php?f=67&t=100807
Comment 1 Martin Kostolný 2013-09-01 08:01:46 UTC
I think this is a duplicate of this one: https://bugs.kde.org/show_bug.cgi?id=318976
Comment 2 sparhawk 2013-09-02 23:21:24 UTC
Yes, it does appear to be. Nice find, Martin.

To clarify, I'm attempting to put these widgets on a panel at the bottom of my screen (as opposed to the dashboard in the linked bug report). If I move the "Memory Status" widget to the left of the "System Load Viewer" widget, I now works fine.

*** This bug has been marked as a duplicate of bug 318976 ***