Bug 510007

Summary:	GPU always shows 100% usage even on idle
Product:	[Applications] plasma-systemmonitor	Reporter:	theeaglecorps
Component:	general	Assignee:	KSysGuard Developers <ksysguard-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	ahiemstra, kdedev, plasma-bugs-null
Priority:	NOR
Version First Reported In:	6.4.5
Target Milestone:	---
Platform:	Neon
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=488440
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Side-by-side screenshot of system monitor vs. radeontop

Description theeaglecorps 2025-09-27 20:25:32 UTC

SUMMARY
Running kde neon plasma CE on a hp g4 405 mini pc with amd ryzen and Vega graphics. When I open system monitor gpu is always 100%, despite cpu being less than 10% utilization. I checked with a different program and actual gpu usage is closer to 10-15%. Idk what is going on as
 All other parts of system monitor are working.

STEPS TO REPRODUCE
1. Open system monitor on this type of computer
2. 
3. 

OBSERVED RESULT
Gpu always 100% in system monitor regardless of windows and at idle

EXPECTED RESULT
Should be showing real time output accurately (closer to 10%)

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: neon
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

Comment 1 TraceyC 2025-09-29 19:23:38 UTC

Thanks for the bug report. So that we have more details to understand what's happening with the System Monitor, can I ask you for screenshots of
- The Overview page of System Monitor, showing the GPU usage at 100% and
- The output of top or the tool of your choice showing the actual GPU usage?

Thanks!

This may be a duplicate of bug 488440

Comment 2 theeaglecorps 2025-09-30 20:03:19 UTC

Created attachment 185409 [details]
Side-by-side screenshot of system monitor vs. radeontop

Comment 3 TraceyC 2025-10-01 14:57:37 UTC

Thanks for the screenshot, that's helpful. This does look like the same bug as 488440, so I'll merge this report in with that one.

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

Comment 4 theeaglecorps 2025-10-01 15:05:36 UTC

Understood, looking through the duplicate bug there doesn't seem to be a solution or have I missed it somewhere?

Comment 5 TraceyC 2025-10-01 16:12:01 UTC

(In reply to theeaglecorps from comment #4)
> Understood, looking through the duplicate bug there doesn't seem to be a
> solution or have I missed it somewhere?

You're reading it correctly. It's been confirmed, and is waiting on someone to have the time and knowledge to look into it.