https://bugs.kde.org/show_bug.cgi?id=444585
mac...@chavis.us changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mac...@chavis.us
--- Comment #1 from mac...@chavis.us ---
(In reply to john Terragon from comment #0)
> SUMMARY
> This affects both the plasma system-monitor app and the plasma widget. I've
> got a 16C/32T machine so when I use the "Individual core usage" preset I
> should see 32 bars (duh). Instead no bars are displayed. That seems to be
> caused by the fact that bars now do not have a minimum width (whereas the
> widget as a whole seems to have a maximum width). So if you start from one
> core sensors (or any other sensor) and you keep adding up the other cores
> one by one you'll see that the bars look fine initially. But then, as you
> add cores, they get thinner and thinner until they get under one pixel width
> an then they become invisible.
>
> It used to work in 5.21. But I can't say anything about 5.22 since I use
> debian and we went from 5.21 to 5.23 directly.
>
>
> STEPS TO REPRODUCE
> 1. Simplest way is to use "Individual core usage" widget (or preset) with a
> machine with 16c/32t
> 2. Otherwise just start adding sensors (any sensor) to the widget until you
> get to about 20 and then you'll see non bars anymore.
> 3.
>
> OBSERVED RESULT
> With a high number of sensors the bars get under one pixel width and
> therefore they become invisible
>
>
> EXPECTED RESULT
> Bars with a minimum width even with a high number of sensors.
>
> SOFTWARE/OS VERSIONS
> Windows:
> macOS:
> Linux/KDE Plasma: Debian unstable
> (available in About System)
> KDE Plasma Version: 5.23.0
> KDE Frameworks Version: 5.86
> Qt Version: 5.15.2
>
> ADDITIONAL INFORMATION
I am currently experiencing the exact same behavior in KDE Neon 5.23 User
Edition (Plasma v 5.23.2). I can get a maximum of 19 sensor bars to visibly
show in "Bar Chart" mode no matter how wide I stretch the widget. At 20+ sensor
bars the bars are no longer visible. The issue has definitely been present in
all of the 5.23 releases, and I believe the issue was also present in some of
the later 5.22 releases if i remember correctly.
--
You are receiving this mail because:
You are watching all bug changes.
