Created attachment 167265 [details] screenshot showing the bug SUMMARY This bug only happens on my laptop, for whatever reason. Every so often (perhaps 1 out of 7 times I log in), the memory monitor widget's blue circle will be stuck at 100% for the entire session. It does show the correct usage percentage number, however. Logging out and back in usually resolves the issue. See attached screenshot. This bug has been happening for a while, even on Plasma 5, and it happens in both X11 and Wayland sessions. STEPS TO REPRODUCE 1. Add the system monitor memory usage widget to the desktop, as seen in the screenshot. I am using the following settings: * Appearance - Display Style: Pie Chart - Minimum Time Between Updates: No Limit * Pie Chart Details - Show Sensors Legend: Yes - Start from Angle: -180° - Total Pie Angle: 180° - Rounded Lines: Yes - Automatic Data Range: Yes * Sensors Details - Total Sensors: [Used Physical Memory Percentage] - Sensors: [Used Physical Memory] - Text-Only Sensors: [Total Physical Memory] 2. Have just the right hardware configuration, apparently. 3. Boot your computer normally over the course of several days. OBSERVED RESULT Occasionally the blue circle is stuck at 100%. EXPECTED RESULT The blue circle should always represent the actual memory usage. SOFTWARE/OS VERSIONS Linux: KDE neon 6.0 User Edition KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Laptop: HP Pavilion m6-1035dx CPU/GPU: AMD A10-4600M 2.3 GHz quad-core APU with Trinity [Radeon HD 7660G] Graphics (using radeon driver) RAM: 8GB DDR3 (2x 4GB PC3-12800 1600 MHz), 7.2GB usable
This sounds like it might not have the proper maximum value and thus it ends up just filling the entire area since it doesn't have a range. The next time this happens, can you share the output of "kstatsviewer --details memory/physical/used" and also the same output from when it doesn't happen?
(In reply to Arjen Hiemstra from comment #1) > This sounds like it might not have the proper maximum value and thus it ends > up just filling the entire area since it doesn't have a range. The next time > this happens, can you share the output of "kstatsviewer --details > memory/physical/used" and also the same output from when it doesn't happen? I get the same output in both cases: Name: Used Physical Memory Short Name: Used Description: Unit: B Minimum: 0 Maximum: 7.75892e+09
*** This bug has been marked as a duplicate of bug 477983 ***
(In reply to Nate Graham from comment #3) > > *** This bug has been marked as a duplicate of bug 477983 *** Nate, I don't think these are the same bugs. In bug #477983, it is the sensor data that is incorrect. In my bug, the reported value is correct, but the graphical representation (circle) is occasionally stuck at 100%. Also, in my original report, I had said this only happens on my laptop. I finally had it happen for the first time on my desktop just the other day. I wonder if system speed is a factor? My laptop is quite old and slow compared to my much faster desktop and has the bug happen much more frequently.