From owner-freebsd-questions Mon Sep 18 12:37:51 2000 Delivered-To: freebsd-questions@freebsd.org Received: from smtp.intop.net (smtp.intop.net [206.156.254.80]) by hub.freebsd.org (Postfix) with ESMTP id A788D37B422 for ; Mon, 18 Sep 2000 12:37:47 -0700 (PDT) Received: from charlie (iwkcpe.intop.net [208.149.79.30]) by smtp.intop.net (8.9.3/8.9.3) with ESMTP id OAA24477; Mon, 18 Sep 2000 14:28:22 -0500 Message-Id: <200009181928.OAA24477@smtp.intop.net> From: "Charlie Schloemer" To: Stephen Krauth , Chris Hill Date: Mon, 18 Sep 2000 14:43:12 -0500 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: fvwm2 gets buggy after a while... Cc: freebsd-questions@FreeBSD.ORG References: In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.12a) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14 Sep 00, at 21:49, 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. I've experienced some strangenesses from fvwm2 that have to do with the focus. When I set .fvwm2rc to ClickToFocus, sometimes there will be a window that's reluctant to give up its focus, even if I click on another window. I have noticed this problem with Netscape Navigator/Communicator more than with Acrobat, but seem to remember problems with both. Closing the offending app causes focus to change to another window, and it, then, is reluctant to relinquish its focus. BTW, did anyone figure out with the 'F' stood for? :-) -Charlie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message