Date: Mon, 27 Mar 2006 10:49:38 -0600 From: "Rick C. Petty" <rick-freebsd@kiwi-computer.com> To: "Frank B. Scholl" <frank.b.scholl@web.de> Cc: freebsd-hackers@freebsd.org Subject: Re: Programs not accepting input? Message-ID: <20060327164938.GA30787@megan.kiwi-computer.com> In-Reply-To: <20060327112153.2aa6bf65.frank.b.scholl@web.de> References: <20060326072009.GL25392@wantadilla.lemis.com> <20060326081719.GB753@turion.vk2pj.dyndns.org> <20060327005342.GX25392@wantadilla.lemis.com> <20060327112153.2aa6bf65.frank.b.scholl@web.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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 and having a running instance of firefox, it every once in a while refuses keyboard input. i have had this with other gtk apps, too, for example sylpheed. > > to circumvent the problem and getting your application back to accept further keyboard input, i just switch workspaces back and forth and thats it, I've tried everything from switching desktops to killing fvwm2. This is how I know it's not window-manager related. As I said before, I can have two rxvts side-by-side. I focus over the left one, type, nothing appears. I focus over the right one, type, keyboard works. Focus back over the left one, nothing. Rinse, repeat. The problem happens more often with GTK apps than a plain rxvt. It's difficult to reproduce the problem, so it's nearly impossible to test. If it were more repeatable, I would have written a test client. Next time it happens, I'll try xev. But I haven't had the problem since I stopped using x11vnc. I only use the nVidia drivers and x.org. -- Rick C. Petty
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060327164938.GA30787>