Created attachment 166554 [details] Black horizontal bars SUMMARY I have some horizontal bar gadgets in my panel and after updating to Plasma 6.0.1, they are turned black. I've attached a video to show how this happens. STEPS TO REPRODUCE 1. Use a dark theme like breeze Dark 2. Add a system monitor widget to panel 3. Set chart type as horizontal bar OBSERVED RESULT Horizontal bar is only black EXPECTED RESULT Horizontal bar should show blue color as system resource is utilized. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.8-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 20 × Intel® Core™ i9-10900 CPU @ 2.80GHz Memory: 62.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1650/PCIe/SSE2 Manufacturer: ASUS ADDITIONAL INFORMATION N/A
Experiencing exactly the same problem after updating from Plasma 5 to 6.0.1. Tried removing ~/.config/plasma-org.kde.plasma.desktop-appletsrc, but it did not help, unfortunately.
Forgot to mention that in my case, I am running X11 with properietary NVIDIA drivers 470.239.06 (since my GTX 760 GPU is old and is not supported by newer drivers), with Linux 6.6.20-1-lts kernel.
Cannot reproduce with an Intel 10th gen iGPU. Maybe an NVIDIA rendering bug?
Works correctly on Git master BUT can confirm on Arch stable (Wayland, AMD) Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.8-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 7950X 16-Core Processor Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XTX
Looks like this was fixed by https://invent.kde.org/plasma/libksysguard/-/merge_requests/327 for Frameworks 6.1, which is unreleased.
(In reply to Nate Graham from comment #5) > Looks like this was fixed by > https://invent.kde.org/plasma/libksysguard/-/merge_requests/327 for > Frameworks 6.1, which is unreleased. Happy to see this fixed. Thanks.
*** Bug 482960 has been marked as a duplicate of this bug. ***