Bug 449313 - CPU core usage vertical bar chart doesn't show data
Summary: CPU core usage vertical bar chart doesn't show data
Status: RESOLVED DUPLICATE of bug 444585
Alias: None
Product: plasma-systemmonitor
Classification: Applications
Component: general (show other bugs)
Version: 5.23.5
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-29 11:09 UTC by darktori
Modified: 2022-01-31 11:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
No bars in vertical mode (57.75 KB, image/png)
2022-01-29 11:09 UTC, darktori
Details
Works OK in horizontal mode (89.20 KB, image/png)
2022-01-29 11:10 UTC, darktori
Details

Note You need to log in before you can comment on or make changes to this bug.
Description darktori 2022-01-29 11:09:59 UTC
Created attachment 146033 [details]
No bars in vertical mode

SUMMARY
I have the system monitor widget on the desktop, that's supposed to show usage of every core of my CPU. I have a 12 core / 24 thread CPU. When in horizontal mode, it shows fine, but in vertical mode it doesn't show the bars, only a pixel at the very bottom of where a bar was supposed to be.


STEPS TO REPRODUCE
1. Have a "Usage per core" widget, perhaps a CPU with a lot of cores.
2. Switch to the vertical bar mode
3. Observe no bars :(

OBSERVED RESULT
No bars :(

EXPECTED RESULT
Bars!

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20220126
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
Kernel Version: 5.16.2-1-default (64-bit)
Graphics Platform: X11
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 31.2 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 2060/PCIe/SSE2


ADDITIONAL INFORMATION
This is not a recent regression, it did use to work a year ago or so.
Comment 1 darktori 2022-01-29 11:10:31 UTC
Created attachment 146034 [details]
Works OK in horizontal mode
Comment 2 Arjen Hiemstra 2022-01-31 11:33:01 UTC

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