From owner-freebsd-questions Thu Sep 14 23:57:53 2000 Delivered-To: freebsd-questions@freebsd.org Received: from outmail1.pacificnet.net (outmail1.pacificnet.net [207.171.0.246]) by hub.freebsd.org (Postfix) with ESMTP id D004F37B422 for ; Thu, 14 Sep 2000 23:57:45 -0700 (PDT) Received: from beelzebub.inside.killermartian.com (usr3-20.pacificnet.net [207.171.38.149]) by outmail1.pacificnet.net (8.9.3/8.9.3) with ESMTP id XAA01440; Thu, 14 Sep 2000 23:38:33 -0700 (PDT) Date: Thu, 14 Sep 2000 23:57:42 -0700 (PDT) From: Stephen Krauth X-Sender: stephenk@beelzebub.inside.killermartian.com To: Chris Hill Cc: freebsd-questions@FreeBSD.ORG Subject: Re: fvwm2 gets buggy after a while... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 14 Sep 2000, Chris Hill wrote: > On Tue, 12 Sep 2000, Stephen Krauth wrote: > > > After a while of being logged in (and maybe after exiting xlock, though I > > can't be sure if it always happens after an xlock) some parts of fvwm2 > > (current version 2.2.4 btw) suddenly stop working. Clicking on an > > 'iconman' icon will no longer de-iconify a window. All fvwm 'key' > > commands fail to be captured. For example, I have CTRL-SHIFT-[ARROWKEYS] > > bound to jump around in a virtual desktop, along with many others; now > > they are passed through to whichever terminal is focused. Doing an fvwm > > 'restart' doesn't fix the problem - only a logout. > > > > Anybody else seen this? > > I haven't seen the icon weirdness, but the CTRL-ARROW (which is how I > have it bound) behaves exactly as you describe; again, only after "a > while." It seems more likely to happen if I've been using acroread. To > make it work right again I don't have to log out, just get out of X and > "startx" again. > > I assumed this was because I'm running ancient software - fvwm-1.24r > under 3.1R - but evidently it's still a problem. Drag. > > -- > Chris Hill chris@monochrome.org > [1] Bus error netscape Well it turned out that my symtoms were exactly the same as if the NUM-LOCK key is pressed (after another reader mentioned it). Though I can't be POSITIVE I'd accidentally pressed that key everytime the problem happened, it's a good bet... Steve K. U.F.O. - "For the feeler gauge in you." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message