Bug 259954 - Sorting by cpu usage in process table doesn't work
Summary: Sorting by cpu usage in process table doesn't work
Status: RESOLVED WORKSFORME
Alias: None
Product: ksysguard
Classification: Unmaintained
Component: ksysguard (show other bugs)
Version: 4.9.2
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-15 14:11 UTC by karaluh
Modified: 2019-04-11 04:33 UTC (History)
1 user (show)

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


Attachments
Screenshot of ksysguard with incorrect sort order (107.72 KB, image/png)
2012-11-05 13:11 UTC, karaluh
Details

Note You need to log in before you can comment on or make changes to this bug.
Description karaluh 2010-12-15 14:11:41 UTC
Version:           0.1
OS:                Linux

As in summary. When sorted by the highest usage on top from time to time proceses with higher usage are placed below the ones with lower.

Reproducible: Didn't try




OS: Linux (i686) release 2.6.35-24-generic
Compiler: cc
Comment 1 Jekyll Wu 2012-11-05 11:59:54 UTC
Can't reproduce it using KDE SC 4.9.x. Is it still a problem for the reporter in recent versions?
Comment 2 karaluh 2012-11-05 12:17:26 UTC
(In reply to comment #1)
> Can't reproduce it using KDE SC 4.9.x. Is it still a problem for the
> reporter in recent versions?

Yup, still happens in 4.9.2. Would you like a screenshot?
Comment 3 Jekyll Wu 2012-11-05 12:19:19 UTC
(In reply to comment #2)
> (In reply to comment #1)
> > Can't reproduce it using KDE SC 4.9.x. Is it still a problem for the
> > reporter in recent versions?
> 
> Yup, still happens in 4.9.2. Would you like a screenshot?

Nobody hates a screenshot :)
Comment 4 karaluh 2012-11-05 13:11:43 UTC
Created attachment 75027 [details]
Screenshot of ksysguard with incorrect sort order
Comment 5 Andrew Crouthamel 2018-11-09 01:09:28 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 6 Andrew Crouthamel 2018-11-20 04:03:22 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 7 Richard Llom 2019-03-12 20:51:21 UTC
Can you reproduce this issue with the current version of ksysguard?
Comment 8 Bug Janitor Service 2019-03-27 04:33:11 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 9 Bug Janitor Service 2019-04-11 04:33:13 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!