Programs not accepting input?
Greg 'groggy' Lehey
grog at FreeBSD.org
Fri Jul 21 03:13:10 UTC 2006
On Thursday, 20 July 2006 at 6:31:08 -0500, Sergey Babkin wrote:
>> From: Peter Jeremy <peterjeremy at optushome.com.au>
>> To resurrect a fairly old thread...
>> On Mon, 2006-Mar-27 11:23:42 +1030, Greg 'groggy' Lehey wrote:
>>> On Sunday, 26 March 2006 at 19:17:19 +1100, Peter Jeremy wrote:
>>>> My work system runs separate X servers on two heads (rather than
>>>> ximerama) and I have problems with windows occasionally refusing to
>>>> accept focus after I move the pointer from screen to screen (though
>>>> I can get an alternative window to accept focus and then switch back
>>>> to the window I originally wanted). This started after an X.org
>>>> upgrade but I'm not sure which one.
>>> Interesting. I've seen this one too: my mail window is at the left of
>>> the right-hand monitor on wantadilla (:0.1). Frequently when I move
>>> from :0.0 to 0:1, the window manager will highlight the window on
>>> :0.1, but focus remains with some window on :0.0. If I move further
>>> right and then back again, focus catches up with the correct window.
>> I've been keeping a closer eye on my problem. I'm using fvwm1 with
>> click-to-focus and lose-focus-on-screen-switch. If I move from one
>> screen to another and quickly click on a window, the border changes
>> colour to indicate that it has focus but keyboard input is ignored.
> This is likely an fvwm1 problem. I use it too (without
> 2 monitors) and after some time something gets broken in
> its focus handling, and the windows stop getting focus.
> Restarting fvwm clears up the problem.
In my case, it's erratic. I suppose I could try restarting the window
manager next time a window freezes.
>>> That's mainly irritating; the problem I describe above is annoying.
>> Did you get anywhere in debugging it?
> BTW, I've promised Greg a script to dump the X protocol
> from binary log, then I was busy and and forgot about it.
> Is there still any interest in this tool?
I'd certainly be interested. It would still be a challenge to catch
the event that causes the freeze, though. Are you thinking of
anything that ethereal can't do?
See complete headers for address and phone numbers.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20060721/5157aabb/attachment.pgp
More information about the freebsd-hackers