Bug 425664 - Starting docker changes the sensors in CPU Usage monitor
Summary: Starting docker changes the sensors in CPU Usage monitor
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: System Monitor widgets (show other bugs)
Version: 5.19.4
Platform: Manjaro Linux
: NOR normal
Target Milestone: 1.0
Assignee: Marco Martin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-22 07:45 UTC by Mario Ray Mahardhika
Modified: 2020-08-23 09:17 UTC (History)
2 users (show)

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

Attachments
widget condition before docker is started (53.48 KB, image/png)
2020-08-22 07:55 UTC, Mario Ray Mahardhika 		Details
widget condition after docker is started (59.37 KB, image/png)
2020-08-22 07:56 UTC, Mario Ray Mahardhika 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Mario Ray Mahardhika 2020-08-22 07:45:35 UTC 
Initially, CPU Usage monitor widget is working normally, showing usage of each CPU cores. But right after starting docker service, the sensors get changed into docker network sensors.

STEPS TO REPRODUCE
1. Start KDE without docker service running
2. Ensure CPU monitor widget shows CPU cores usage
3. Start docker service
4. CPU monitor will show docker ones instead

OBSERVED RESULT
CPU monitor widget shows docker sensors values

EXPECTED RESULT
CPU monitor widget still shows CPU cores usage values

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaroi
KDE Plasma Version: 5.19.4
KDE Frameworks Version: 5.73.0
Qt Version: 5.15.0

ADDITIONAL INFORMATION
-
Comment 1 Mario Ray Mahardhika 2020-08-22 07:55:57 UTC 
Created attachment 131089 [details]
widget condition before docker is started
Comment 2 Mario Ray Mahardhika 2020-08-22 07:56:17 UTC 
Created attachment 131090 [details]
widget condition after docker is started
Comment 3 Mario Ray Mahardhika 2020-08-22 07:57:23 UTC 
Oh, stopping docker afterwards does not return the sensors back to what it should be. It sticks until reboot (relogin doesn't help).
Comment 4 David Edmundson 2020-08-22 17:34:08 UTC 
Should be fixed by a7d1b0d95c7ad22e0249e86d5e14092f06ca4299 in ksysguard
Comment 5 Mario Ray Mahardhika 2020-08-23 09:17:41 UTC 
(In reply to David Edmundson from comment #4)
> Should be fixed by a7d1b0d95c7ad22e0249e86d5e14092f06ca4299 in ksysguard

Has it been tagged to be released in the next version? i.e. 5.19.5 maybe?