Bug 300821 - ksysguard fails to format CPU list with many CPUs
Summary: ksysguard fails to format CPU list with many CPUs
Status: RESOLVED WORKSFORME
Alias: None
Product: ksysguard
Classification: Unmaintained
Component: ksysguard (other bugs)
Version First Reported In: 4.8
Platform: openSUSE Linux
: NOR minor
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-29 16:26 UTC by meyerm
Modified: 2019-04-11 04:33 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description meyerm 2012-05-29 16:26:14 UTC
Using ksysguard (4.8.3) on my local notebook to connect to a ksysguardd on a westmere  based server (40 physical cores, 80 logical cores) shows the CPUs in an inconsitent way. It reformats all CPUs from cpu0 to cpu31 into CPU 1 to CPU 32 and the rest is shown in the "native way" (cpu32 to cpu79). To make it clearer, you do have two CPUs with the number 32 in the list (CPU 32 which is cpu31 and cpu32 with actually is cpu32).

Couldn't we switch off the reformatting?

Reproducible: Always

Steps to Reproduce:
1. copy ksysguardd to a computer with more than 32 CPUs
2. connect with ksysguard
Actual Results:  
Wrongly formatted list of CPUs

Expected Results:  
Correctly (or even better not at all) formatted list of CPUs
Comment 1 Andrew Crouthamel 2018-11-09 00:58:00 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-18 03:36:45 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Richard Llom 2019-03-12 17:23:57 UTC
I' dont have such a system at hand...

Can you test if this issue is also happening with the current version of ksysguard and qt?
Comment 4 Bug Janitor Service 2019-03-27 04:33:12 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2019-04-11 04:33:14 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!