Bug 143055 - Click to focus not working on inner window
Summary: Click to focus not working on inner window
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-16 12:21 UTC by S. Bryant
Modified: 2010-10-15 10:24 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description S. Bryant 2007-03-16 12:21:51 UTC
Version:            (using KDE KDE 3.5.6)
Installed from:    SuSE RPMs
Compiler:          gcc version 4.1.2 20061115 (prerelease) (SUSE Linux) 
OS:                Linux

When I click inside a non-active window, the window is not activated or raised.  I can click on and use menus and other widgets in the non-active window, so the mouse clicks are being passed through.  This also affects non-KDE apps (eg: XEmacs) in exactly the same way, so it seems to be a KWin problem.

Clicking on the root window used to deactivate the active window without activating a new one, but this no longer works (nothing happens).

Possibly related: using ALT + left-click (in inner window) to move a window no longer works.  The ALT key on its own still activates the menu as normal.

Mouse actions in the window frame or title bar work correctly, including those with the modifier.  It's the actions inside the window which are not working.

I rechecked my settings, tried alternative ones and the tried setting them back, but to no avail.  I'm using click to focus with "click raise active window" activated.  My left button for the inactive inner window is set to "Activate, Raise & Pass Click", but only the "Pass Click" part happens.

I've been experiencing this behaviour since my update from KDE 3.5.5 to 3.5.6.

I'm using OpenSUSE 10.2 (32bit), with the RPMs from their repository; I'm using the NVidia drivers and TwinView with 2 monitors.  This problem affects other users on the same machine in exactly the same way. 

I disabled window translucency and shadows etc, logged out and in, but the behaviour was the same.  I have not yet tried disabling composite support in xorg.conf.  I did update to the latest NVidia drivers, but that made no difference.

A VM I have with the same OS and KDE level does not exhibit this problem.  The VM has no multi-screen or compositing support configured.

-- Steve
Comment 1 S. Bryant 2007-03-16 19:14:08 UTC
I managed to get this working again, but I have no idea why.  Here's what I did:

1. Set option "Composite" to "false" (xorg.conf, "Extensions" section), restarted X.  No change.

2. Set option "DamageEvents" to "false" (xorg.conf, "Device" section), restarted X.  No change initially, and then it suddenly started behaving properly, after I moved some windows between the screens.  Eh?

3. Set "DamageEvents" back to "true", restarted X - still works.

4. Set "Composite" back to "true", restarted X - still works.

5. Enabled translucency and shadows in the control panel.  That had no effect until I restarted X again.  The focus behaviour still works properly, as does ALT + left-click to move windows.  No other settings in the control panel were changed.

I'm now not sure if this is really a KWin bug or an X.Org bug.

-- Steve
Comment 2 Lubos Lunak 2007-03-23 15:29:49 UTC
Looks like X.org or NVidia problem to me. Can you reproduce the problem without using the nvidia driver?
Comment 3 S. Bryant 2007-03-23 23:15:46 UTC
Hi Lubos...

I'm not sure if I can reproduce this even with the NVidia driver!  If I manage, I'll switch the driver to the from "nvidia" to "nv" and report the results.

-- Steve
Comment 4 Ave 2007-04-21 22:51:30 UTC
Hello,

I've came across the same problem lately. I'm not sure how did it start, though I'm quite sure I wasn't upgrading any program. I just lost the ability to activate or raise a non active window with clicking it inside (i have to click the top toolbar), just like Steve has written above. 
I work on Kubuntu distribution, and have recently installed Feisty Fawn. I have now KDE 3.5.6, qt 3.5.6, although the problems started at 3.5.5. I use "nv" drivers for my nvidia graphic card.

-- Ave
Comment 5 John Miller 2007-05-28 13:35:38 UTC
I'm having this problem also, with KDE 3.5.7, Qt 3.3.8, and Nvidia 100.14.06 drivers. Apps that use GTK2 like GIMP, Firefox, and Avidemux seem to not be affected by this bug and will raise and focus with a click anywhere on their window while KDE apps will only raise and focus if you click on the titlebar or window frame.
Comment 6 shattered 2008-05-11 18:48:11 UTC
This happens (very infrequently) to me, too.  KDE 3.5.8,  X.org server 1.3.0.0, xf86-input-mouse-1.2.3, NetBSD/i386 4.0.  

Sometimes my optical mouse misbehaves and mouse pointer jumps across the screen; this seems to trigger the bug.
Comment 7 John Miller 2008-08-17 13:43:36 UTC
I'm now experiencing this bug in trunk, svn revision 847799. Sometimes logging out and back in will fix it, but not always.
Comment 8 KoYz 2009-05-28 00:42:50 UTC
ATI fglrx : Catalyst 9.4
Qt: 4.5.1
KDE: 4.2.86 (KDE 4.2.86 (KDE 4.3 >= 20090514)) "release 125"
KWin: 4.2.86 (KDE 4.2.86 (KDE 4.3 >= 20090514)) "release 125"

I need to click on the windows title to set the focus, except with firefox.
This bug isn't obvious when you use alt+tab or the task bar to swich windows focus but this is very uncomfortable when working on 2 screen with one windows on each screen.
Comment 9 FiNeX 2010-10-10 14:40:27 UTC
I'm not able to reproduce this bug with KDE 4.5.2, Qt 4.7 and nvidia driver 256.53.

What is the exact configuration of KWin?

@KoYz, @John, @Sergey, @Steve: are you still experiencing this bug on a recent KDE version? Did you tested with a clean user account?
Comment 10 shattered 2010-10-10 15:17:13 UTC
I have switched from wireless to wired mouse and didn't have this problem since.  Those large changes in pointer coordinates seemed to trigger this bug.

Still using KDE 3.5.10, modular-xorg-server 1.6.3, xf86-input-mouse 1.4.0.
Comment 11 FiNeX 2010-10-10 17:04:18 UTC
Thanks for the feedback Sergey.
Comment 12 S. Bryant 2010-10-14 20:05:06 UTC
As the original reporter, I am unable to reproduce this bug on OpenSUSE 11.3 (x86_64), KDE 4.5.2, XOrg 7.5, NVidia 256.53. I haven't tested KDE 3.5.x.

I recall having other (unrelated) problems with the 'nv' driver at the time, and never got those resolved.  I think this bug disappeared after an update or a reinstall somewhere along the way.

Steve
Comment 13 FiNeX 2010-10-15 10:24:01 UTC
Thanks Steve