In the last month or two I've seen increasing occurrences of programs
refusing keyboard input after they've been running for a while
(between hours and days). They still respond to the mouse. At first
I thought it was hardware, but it happens on a number of different
machines, and only with certa
[ CC'd to hackers only ]
On Sun, Mar 26, 2006 at 05:50:09PM +1030, Greg 'groggy' Lehey wrote:
> In the last month or two I've seen increasing occurrences of programs
> refusing keyboard input after they've been running for a while
> (between hours and days). They still respond to the mouse. At f
Greg 'groggy' Lehey wrote:
In the last month or two I've seen increasing occurrences of programs
refusing keyboard input after they've been running for a while
(between hours and days). They still respond to the mouse. At first
I thought it was hardware, but it happens on a number of different
On Sun, 2006-Mar-26 17:50:09 +1030, Greg 'groggy' Lehey wrote:
>In the last month or two I've seen increasing occurrences of programs
>refusing keyboard input after they've been running for a while
>(between hours and days). They still respond to the mouse. At first
>I thought it was hardware, bu
On Sun, 26 Mar 2006, Peter Jeremy wrote:
On Sun, 2006-Mar-26 17:50:09 +1030, Greg 'groggy' Lehey wrote:
In the last month or two I've seen increasing occurrences of programs
refusing keyboard input after they've been running for a while
(between hours and days). They still respond to the mouse
On Sun, Mar 26, 2006 at 11:16:36AM +, Robert Watson wrote:
> On Sun, 26 Mar 2006, Peter Jeremy wrote:
> >On Sun, 2006-Mar-26 17:50:09 +1030, Greg 'groggy' Lehey wrote:
> >>In the last month or two I've seen increasing occurrences of programs
> >>refusing keyboard input after they've been runnin
On Sun, Mar 26, 2006 at 07:17:19PM +1100, Peter Jeremy wrote:
>
> Is the problem that the clients aren't taking focus or have focus
> but aren't accepting keyboard input?
My problem wasn't about focus. I know the window had input focus (my
settings change the border color for focused windows), b
On Sunday, 26 March 2006 at 19:17:19 +1100, Peter Jeremy wrote:
> On Sun, 2006-Mar-26 17:50:09 +1030, Greg 'groggy' Lehey wrote:
>> In the last month or two I've seen increasing occurrences of programs
>> refusing keyboard input after they've been running for a while
>> (between hours and days). T
On Sunday, 26 March 2006 at 1:36:57 -0600, Rick C. Petty wrote:
> On Sun, Mar 26, 2006 at 05:50:09PM +1030, Greg 'groggy' Lehey wrote:
>> In the last month or two I've seen increasing occurrences of programs
>> refusing keyboard input after they've been running for a while
>> (between hours and da
On Mon, 2006-Mar-27 11:29:15 +1030, Greg 'groggy' Lehey wrote:
>>> One thing that the machines have in common is that they all run x2x
Can you drop this and just use a single X server?
>Reminder: my final question was "how do I go about debugging this
>problem?".
X11 protocol tracing (eg xmon) a
hello,
i followed this discussion so far and wondered what your techniques are to have
your running programs accepting input again. in my case, this phenomenon
heavily depends on the windowmanager you chose. when being on fluxbox and
having a running instance of firefox, it every once in a whil
Greg 'groggy' Lehey wrote:
Same here. As mentioned in the original message, I can use the mouse
to open a new window under firefox. The new window will accept
keyboard input, the old one won't. It's almost as if it's deadlocking
on input.
Just a "me too". I used to get this with mozilla j
On Mon, Mar 27, 2006 at 11:21:53AM +0200, Frank B. Scholl wrote:
>
> i followed this discussion so far and wondered what your techniques are to
> have your running programs accepting input again. in my case, this phenomenon
> heavily depends on the windowmanager you chose. when being on fluxbox
Greg 'groggy' Lehey wrote:
>
> > The focus management and the highlighting of the window manager
> > decoration are not physically connected in any way, so a bug in the
> > window manager might cause it to do the highlighting but forget to
> > give the focus to the application.
>
> But mouse focu
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 refusin
On Thursday, 20 July 2006 at 18:37:08 +1000, Peter Jeremy wrote:
> 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 (rathe
On Friday 21 July 2006 23:02, Robert Watson wrote:
> I've occasionally also had weird focus problems with KDE. Among other
> things, it looks like occasionally the mouse release event is lost
> somewhere in the system (or something along these lines) -- I don't know if
> it's a driver problem, a m
On Friday, 21 July 2006 at 23:38:00 +0930, Daniel O'Connor wrote:
> On Friday 21 July 2006 23:02, Robert Watson wrote:
>> I've occasionally also had weird focus problems with KDE. Among other
>> things, it looks like occasionally the mouse release event is lost
>> somewhere in the system (or somet
On Sunday 23 July 2006 08:33, Greg 'groggy' Lehey wrote:
> > One thing that IS a KDE problem is having it manage 2 distinct desktops
> > (ie :0.0 [laptop LCD] and :0.1 [TV out]) - it occasionally decides to
> > give the other display focus after a dialog has been closed..
>
> Are you sure? This so
On 07/21/2006 08:32, Robert Watson wrote:
On Fri, 21 Jul 2006, Greg 'groggy' Lehey wrote:
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
On Monday, 27 March 2006 at 7:03:23 -0600, Sergey Babkin wrote:
>> Same here. As mentioned in the original message, I can use the mouse
>> to open a new window under firefox. The new window will accept
>> keyboard input, the old one won't. It's almost as if it's deadlocking
>> on input.
>>
>> R
In <[EMAIL PROTECTED]>, Greg 'groggy' Lehey <[EMAIL PROTECTED]> typed:
> > The focus management and the highlighting of the window manager
> > decoration are not physically connected in any way, so a bug in the
> > window manager might cause it to do the highlighting but forget to
> > give the focu
On Monday, 27 March 2006 at 20:30:52 -0500, Mike Meyer wrote:
> In <[EMAIL PROTECTED]>, Greg 'groggy' Lehey <[EMAIL PROTECTED]> typed:
>>> The focus management and the highlighting of the window manager
>>> decoration are not physically connected in any way, so a bug in the
>>> window manager might
>Same here. As mentioned in the original message, I can use the mouse
>to open a new window under firefox. The new window will accept
>keyboard input, the old one won't. It's almost as if it's deadlocking
>on input.
>
>Reminder: my final question was "how do I go about debugging this
>problem?".
On Thu, 2006-Jul-20 06:31:08 -0500, Sergey Babkin wrote:
>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.
I've seen that as well and I'm
>From: Peter Jeremy <[EMAIL PROTECTED]>
>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
On Thursday, 20 July 2006 at 6:31:08 -0500, Sergey Babkin wrote:
>> From: Peter Jeremy <[EMAIL PROTECTED]>
>
>> 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
On Fri, 21 Jul 2006, Greg 'groggy' Lehey wrote:
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
On Friday, 21 July 2006 at 14:32:04 +0100, Robert Watson wrote:
>
> On Fri, 21 Jul 2006, Greg 'groggy' Lehey wrote:
>
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
>From: Peter Jeremy <[EMAIL PROTECTED]>
>>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?
>
>What does your script do? I've used xmon in the (distant) past but
>it is designed to sit i
30 matches
Mail list logo
