Bug 157178

Summary:	"Detect" option of Window Behavior settings module cannot be disabled and is persistent
Product:	[Plasma] kwin	Reporter:	David Benjamin <davidben>
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	andrey
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description David Benjamin 2008-02-05 00:20:28 UTC

Version:            (using KDE 4.0.0)
Installed from:    Ubuntu Packages
OS:                Linux

Steps to Reproduce:
1. Open System Settings
2. Select "Window Behavior"
3. Under "Window-Specific", select "New..."
4. Press "Detect".
5. Hit Esc a few times.

Results:
Pressing Esc does not cause the Detect entry to disappear, and further Esc's that leave that control panel module fail to remove the crosshairs. If one clicks after that mode has been left, the dialog is confusing given the context.

Comment 1 Andrey 2008-02-18 20:03:22 UTC

I have the same problem. KDE trunk is compiled from Gentoo overlay, kdebase and kdelibs revisions are quiet recent.

Comment 2 Andrey 2008-02-18 20:06:54 UTC

Oh.. This bug may be a duplicate of bug #156872

Comment 3 David Benjamin 2008-02-18 22:21:20 UTC

Is it?

I think they're slightly different, although poking around, I suspect they are reasonably related. #156872's problem appears to be that clicking the cross-hair doesn't actually do anything, as opposed to inability to cancel the detect mode.

Interestingly, it seems that when canceling the first dialog, the crosshairs begin to work, however it becomes pointless since the dialog is gone. (Save for retyping or pasting the data.)

Comment 4 Lubos Lunak 2008-02-24 13:10:20 UTC


*** This bug has been marked as a duplicate of 156872 ***

Comment 5 Martin Flöser 2012-04-13 19:24:38 UTC

Bulk change: move all KWin kcm bugs to product kwin