https://bugs.kde.org/show_bug.cgi?id=481815
--- Comment #7 from Arjen Hiemstra <ahiems...@heimr.nl> --- (In reply to Jonathan Croteau-Dicaire from comment #5) > I cloned the project on my desktop and compiled it. > I see that there is three project kstatsviewer, ksystemstats and > ksystemstatstest. If I want to investigate why my GPU got the name GPU 2 > which one should I use (and with which argument) and do you have pointer or > advice on how to set up my environment to investigate and understand why > this is happening? Generally I'd recommend setting up an environment following https://community.kde.org/Get_Involved/development so that you can build all dependencies as well. That said, if you already managed to build ksystemstats that's probably fine as well, it doesn't necessarily depend on the latest version of everything. If you have a build, there is a "prefix.sh" script in the build dir that, when sourced, sets up the right environment variables so the installed application should run correctly. >ksystemstats seems to have a replace option that could be useful to redo the >discovery phase of the sensor, I assume. For development, I generally run with "--replace --remain", replace for replacing any running instance, remain so it doesn't quit when you don't have anything using it. Starting ksystemstats will actually redo any discovery and initialization that it needs to do for its sensors, there is no cached data. -- You are receiving this mail because: You are watching all bug changes.
