Bug 371946

Summary:	System Load plasmoid can't display load for each separate CPU
Product:	[Plasma] kdeplasma-addons	Reporter:	t.schmittlauch
Component:	systemloadviewer	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	jghodd, t.schmittlauch
Priority:	NOR
Version:	5.8.2
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description t.schmittlauch 2016-11-01 14:00:43 UTC

The 'system load' plasmoid displays only blank bars when configured to show load for each CPU separately.

How to reproduce:
1. Insert 'system load' plasmoid into a panel
2. Open settings of that plasmoid
3. Choose the following settins:
  - Show: [x] CPU monitor, [x] CPUs separately
  - Monitor type: [x] compact bar
4. save the settings

Expected result: On my system 4 bars should be displayed, each one showing one CPU's load
Actual result: Only one bar is created which is always blank (height=0). The mouseover-tooltip reads 'CPU 0; 0% @ 0 MHz'

CPU worload for all CPUs (no 'CPUs separately') is displayed correctly though

Comment 1 Jeff Hodd 2016-11-02 07:27:30 UTC

I can confirm that this is still an issue in kdeplasma-addons-5.8.3. There appear to be a couple of separate errors now, one for an undefined variable - memApplication - in SystemLoadViewer.qml, and another that appears to be a failure to retrieve the correct data from systemmonitor.

Here are the relevant log file entries:

plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:225: ReferenceError: memApplication is not defined
plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:225: ReferenceError: memApplication is not defined
plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:225: ReferenceError: memApplication is not defined
plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:225: ReferenceError: memApplication is not defined
plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:246: TypeError: Cannot read property 'value' of undefined
plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:246: TypeError: Cannot read property 'value' of undefined
plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:246: TypeError: Cannot read property 'value' of undefined
plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:225: ReferenceError: memApplication is not defined
plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:225: ReferenceError: memApplication is not defined
plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:253: TypeError: Cannot read property 'value' of undefined
plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/CompactBarMonitor.qml:45:20: Unable to assign [undefined] to QColor

The "Cannot read property 'value' of undefined" errors are related to dataSource.memFree and dataSource.swapFree.

The workaround described by spiollinux@googlemail.com does seem to alleviate the "all CPUs" issue in the compact bar display itself (although unsatisfactorily), although the mouseover-tooltip now, in v5.8.3, shows nothing but "System load" without any data.

Comment 2 Jeff Hodd 2016-11-02 07:31:17 UTC

It's my guess that the last error message:

plasmashell[1205]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/CompactBarMonitor.qml:45:20: Unable to assign [undefined] to QColor

is at the root of the missing cpu display columns.

Comment 3 Christoph Feck 2016-12-13 01:25:33 UTC


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