Bug 115800 - Using Ctrl+A with a "filter" enabled select all processes, and not only the processes shown
Summary: Using Ctrl+A with a "filter" enabled select all processes, and not only the p...
Status: RESOLVED FIXED
Alias: None
Product: ksysguard
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR major
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-06 17:43 UTC by pierre
Modified: 2006-12-04 03:29 UTC (History)
0 users

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description pierre 2005-11-06 17:43:44 UTC 
Version:           1.2.0 (using KDE 3.4.92 (beta2, >= 20051010), Kubuntu Package 4:3.4.92-0ubuntu2 )
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.12-9-k7

Hi

I'd like to kill a list of processes. So I opened Ksysguard, and I filtered the list with a name. I then pressed Ctrl+A to select all processes, and clicked on Kill.
But hopefully, the dialog showed my that all my processes were going to be killed !
I expected it to select only the shown processes...
Comment 1 Tim Harper 2006-03-27 21:29:53 UTC 
I've also ran into this trouble a while ago.  Just recently, I filtered down to a list, and tried to batch kill (using ctrl-a), and ended up killing my entire system.  Not the behavior I expected, naturally :)

Would this be a difficult change?
Comment 2 John Tapsell 2006-05-17 04:34:50 UTC 
Fixed in trunk.
Comment 3 Philip Rodrigues 2006-09-26 12:36:35 UTC 
John, a user is reporting that this problem is still present (see bug 134361). I can't get ksysguard running here to test. Did the fix also go into the branch?
Comment 4 Greg Martyn 2006-09-26 15:31:29 UTC 
Reopening due to feedback
Comment 5 John Tapsell 2006-12-04 03:29:03 UTC 
Now fixed in kde 3.5 as well :-)

Well it's fixed in 98% of cases.  There's a fundamental design flaw in 3.5 that I cannot work around.  But it's hard to hit the cases where it doesn't work