Bug 510369

Summary: Battery Graphs in the Energy panel do not show
Product: [Applications] kinfocenter Reporter: kirthikmanicka
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: sitter
Priority: NOR    
Version First Reported In: 6.3.6   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: An image showing the 'Energy' section of the Info Center

Description kirthikmanicka 2025-10-08 00:37:48 UTC
Created attachment 185591 [details]
An image showing the 'Energy' section of the Info Center

SUMMARY
The graphs for 'Charge Percentage' and 'Energy consumption do not show up

STEPS TO REPRODUCE
1. open Info Center
2. go to the 'Energy' tab
3. 

OBSERVED RESULT
The 'Charge Percentage' and 'Energy Consumption' graphs do not show

EXPECTED RESULT
I see the normal battery stats in addition to the graphs

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian 13
KDE Plasma Version: 6.3.6
KDE Frameworks Version: 6.13.0
Qt Version: 6.8.2

ADDITIONAL INFORMATION
Comment 1 kirthikmanicka 2025-10-08 00:44:24 UTC
I could see the graphs in Plasma 5, but they disappeared when I upgraded to Plasma 6.

Output of running kinfocenter in the terminal

qt.qml.typeregistration: Invalid QML element name "Hint"; value type names should begin with a lowercase letter
Physical device 0: 'Intel(R) Iris(R) Xe Graphics (TGL GT2)' 25.0.7 (api 1.4.305 vendor 0x8086 device 0x9A49 type 1)
Physical device 0: 'llvmpipe (LLVM 19.1.7, 256 bits)' 0.0.1 (api 1.4.305 vendor 0x10005 device 0x0 type 4)
excess llvmpipe detected, ignoring
qrc:/kcm/kcm_energyinfo/main.qml:250:13: Unable to assign [undefined] to bool
Comment 2 Harald Sitter 2025-10-08 11:40:37 UTC
Thank you for your bug report!
Debian advises users to not submit bugs upstream (https://www.debian.org/Bugs/Reporting), as this version of the KDE software no longer receives updates or maintenance from KDE, and so it's possible that the bug exists only in Debian at this point.
Could you report the bug to Debian using the report bug utility (https://packages.debian.org/stable/utils/reportbug)? If necessary, the maintainer of the package will forward the bug upstream.
Thanks for understanding!