Bug 514363 - Name the GPUs like they are in KInfoCenter
Summary: Name the GPUs like they are in KInfoCenter
Status: RESOLVED DUPLICATE of bug 503082
Alias: None
Product: plasma-systemmonitor
Classification: Applications
Component: general (other bugs)
Version First Reported In: 6.5.4
Platform: CachyOS Linux
: NOR wishlist
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2026-01-09 10:48 UTC by Fernando Marcelino Muniz
Modified: 2026-01-12 11:39 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Issue on Plasma 6.5.4 (725.46 KB, video/x-matroska)
2026-01-09 11:03 UTC, Fernando Marcelino Muniz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Fernando Marcelino Muniz 2026-01-09 10:48:23 UTC
STEPS TO REPRODUCE
Open system monitor and look at the multiple GPUs.

OBSERVED RESULT
They are identified by numbers.

EXPECTED RESULT
They should be identified by their actual names, just like they are in KInfoCenter.

SOFTWARE/OS VERSIONS
Operating System: CachyOS Linux 
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1
Kernel Version: 6.18.3-2-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i5-11300H @ 3.10GHz
Memory: 9 GB of RAM (8.1 GB usable)
Graphics Processor 1: Intel® Iris® Xe Graphics
Graphics Processor 2: NVIDIA GeForce GTX 1650
Manufacturer: LENOVO
Product Name: 82MG
System Version: IdeaPad Gaming 3 15IHU6
Comment 1 Fernando Marcelino Muniz 2026-01-09 11:03:05 UTC
Created attachment 188349 [details]
Issue on Plasma 6.5.4

I hope I will get to figure out what is this third GPU that I've just found out that I have.
Comment 2 Arjen Hiemstra 2026-01-12 11:39:55 UTC
You have two GPUs, so one of the GPUs you're seeing is the integrated chip and the other the dedicacted one. The problem is that the underlying library we use doesn't index from 0 but potentially starts at some other number, which is an issue we're already tracking in a different bugreport.

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