Bug 221916

Summary:	Kill Process can't be clicked
Product:	[Applications] ksysguard	Reporter:	Martin Koller <kollix>
Component:	Process Controller - krunner part	Assignee:	KSysGuard Developers <ksysguard-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	arno, johnflux, vit.gorbunov
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	Updated for 64bit

Description Martin Koller 2010-01-09 14:07:26 UTC

Version:           unknown (using 4.3.90 (KDE 4.3.90 (KDE 4.4 RC1)) "release 209", KDE:KDE4:Factory:Desktop / openSUSE_11.2)
Compiler:          gcc
OS:                Linux (i686) release 2.6.31.5-0.1-desktop

Bringing up the Process windows by "Ctrl+Esc" shows in the left top corner a "Kill Process..." button.
However, the button has a weird behaviour:
It can not be clicked; it even does not react on mouse over and also does not show a tooltip and using the plastik style does not change the top/bottom color of it while over it, EXCEPT while over the area inside the button which shows the "..." after the word "Process".

Other pushbuttons, which have a similar look, work as expected (e.g. in konqueror's configure dialog/cookies, there is a "delete all" button which also has an icon to the left and some text.)

Comment 1 John Tapsell 2010-01-09 16:40:11 UTC

Just to confirm, you are pressing ctrl+esc and not doing anything else and the kill button is not drawn as disabled?

When you first bring up the dialog no processes are selected so the button should be disabled and so grayed out.

Comment 2 Martin Koller 2010-01-09 22:51:58 UTC

On Saturday 09 January 2010 16:40:15 John Tapsell wrote:

> --- Comment #1 from John Tapsell <johnflux gmail com>  2010-01-09 16:40:11 ---
> Just to confirm, you are pressing ctrl+esc and not doing anything else and the
> kill button is not drawn as disabled?

Of course I selected a process before I tried to kill it ...

> When you first bring up the dialog no processes are selected so the button
> should be disabled and so grayed out.

I know the difference between a disabled and an enabled button (I'm a Qt programmer).
This bug is about the enabled button.

Comment 3 John Tapsell 2010-01-10 04:52:45 UTC

(In reply to comment #2)
> I know the difference between a disabled and an enabled button (I'm a Qt
> programmer).
> This bug is about the enabled button.

I know - I was trying to work out if it was a disabled button that is being drawn as enabled, or an enabled button behaving as if it's disabled.

I can't reproduce myself, but two other people can.

Comment 4 John Tapsell 2010-01-10 11:57:45 UTC

*** Bug 222024 has been marked as a duplicate of this bug. ***

Comment 5 Arno Rehn 2010-01-10 13:57:01 UTC

I can confirm this, using trunk (r1067626). The button behaves normally after I move the mouse over the search field or the combobox. As soon as other widgets do the "highlight" effect, the pushbutton seems to work ok again. But if I just fire up ksysguard, click on a process and hover the button, it behaves as described above.

Comment 6 Martin Koller 2010-01-10 15:47:45 UTC

On Sunday 10 January 2010 13:57:02 Arno Rehn wrote:

> 
> The button behaves normally after I
> move the mouse over the search field or the combobox. As soon as other widgets
> do the "highlight" effect, the pushbutton seems to work ok again.

Not in my case. The button does never work.

Comment 7 Arno Rehn 2010-01-10 22:14:54 UTC

As it was noted on the mailing list, it's actually only a small part of the button which reacts to mouse events (regardless of the widgets that were highlighted before). The reactive part of the button seems to be on the right side.

Just for reference: http://lists.kde.org/?l=kde-core-devel&m=126315608221251&w=2

Comment 8 John Tapsell 2010-01-12 00:18:23 UTC

Created attachment 39796 [details]
Updated for 64bit

This copies some of the code from pinotree's patch to add 64bit support.

Comment 9 John Tapsell 2010-01-12 00:25:10 UTC

I'm an idiot.  Ignore last patch.

Comment 10 John Tapsell 2010-01-12 03:20:11 UTC

Aseigo fixed - thanks.