Created attachment 170699 [details] Bug showcase SUMMARY When using a top panel "Text Only" system monitor sensor widgets have dramatically reduced size compared to 6.0, and are offset to the top STEPS TO REPRODUCE 1. Create a top panel 2. Add a system monitor widget configured as "text only" to the panel OBSERVED RESULT The widget is very small and offset to the top EXPECTED RESULT The widget is sized to the panel appropriately and located in the vertical center of the panel SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS (available in About System) KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION Sensor widget was fine in 6.0. Additionally, the text for the "used memory" sensor is much smaller now compared to 6.0.
*** Bug 488951 has been marked as a duplicate of this bug. ***
*** Bug 488983 has been marked as a duplicate of this bug. ***
Created attachment 170822 [details] ss
Created attachment 170823 [details] sss
Maybe it's separate issues (and feel free to direct me there) but I think that widget rendering in panels is generally broken in 6.1, in that the size of the widgets don't match what they should be (or at least what they were in <= 6.0) making them mostly unusable now. For example, "Individual Core Usage" in bar graph mode (which is really just a bunch of sensors preconfigured one for each core) renders with the same width whether you ask it to show 1 core or 12, meaning with 1 core you get a nice graph, and with 12 cores you basically get nothing (since it's trying to squish them into a 20 pixel wide square). Weather widget doesn't display temperatures, just a bunch of cloud/sun.
Interesting, I don't have issues with other widgets I use. The default kde weather widget works normally on my end. Weird.
My apologies, I take back what I said about the CPU widget - I'm on Fedora and I may have had a mix of inconsistent versions of components from when I first upgraded. I updated again and CPU graphs now expand properly. Weather widget doesn't show temperature, so I'm thinking maybe that's unrelated (as opposed to a bigger widget rendering issue). When I use text only sensors look close to the "Bug showcase" screenshot (i.e. text is high up and not in the middle) but not cut off like ss and sss.
I can confirm the issue.
A possibly relevant merge request was started @ https://invent.kde.org/plasma/libksysguard/-/merge_requests/362
Git commit 8674b523e0417d3e92406812cd7f688b52182453 by Arjen Hiemstra. Committed on 16/07/2024 at 09:55. Pushed by ahiemstra into branch 'master'. faces/text: Use grid layout for compact representation This allows the compact rep to keep displaying multiple items, moving them to new columns (in horizontal mode) or rows (in vertical mode) as needed. Only if we can't even fit a full row/column of all the items do we switch to smaller text. M +58 -11 faces/facepackages/textonly/contents/ui/CompactRepresentation.qml https://invent.kde.org/plasma/libksysguard/-/commit/8674b523e0417d3e92406812cd7f688b52182453
*** Bug 489886 has been marked as a duplicate of this bug. ***
*** Bug 489767 has been marked as a duplicate of this bug. ***
Still messed up on my computer, which version did it fixed? Maybe I should do a manual update? My version: System Monitor 6.1.4
(In reply to Misaka17535 from comment #13) > Still messed up on my computer, which version did it fixed? Maybe I should > do a manual update? > My version: System Monitor 6.1.4 It was fixed for version 6.2, which is still in beta phase (6.2.0 official release is in three weeks) Please, reopen only if the same issue keeps happening after upgrading to that version or the beta
I reopened this issue because it still exists, it has always existed. Even if my panel height is 70, the system monitor widget font size does not change, it stay way to small. The text is also abbreviated although it should not
The bug is fixed in 6.2.0, not 6.1.x, therefore what you're seeing is expected.
Created attachment 174401 [details] Messed up system monitor widget Here is a screenshot to see what's the issue is
(In reply to Naxdy from comment #16) > The bug is fixed in 6.2.0, not 6.1.x, therefore what you're seeing is > expected. Oh, OK, i did not know that, thank you for your help :)