> I don't know whether or not this is a common problem, but I notice that,
> apparently arbitrarily, the fvwm key bindings set up by my .fvwm2rc file
> stop working at some point after the X session has been started.
> Mouse bindings, however, are fine.
It evidently is. Refer to the thread: ``fvwm2 buttons stop working''
here in c.o.l.x to learn that you have company.
Quote:> This happens pretty much always, but I can't 'repeat' the phenomena, so to
> speak, on demand, so I haven't the vaguest idea why. Does anyone have any
> idea what might be causing this? Is there any way to get them back,
> without having to restart fvwm (though actually I think I have to restart
> X to really get them back!)?
A search on Dejanews reveals that this is problem dating back a few
years. A number of suggestions have been posted including (but not
- Make sure scroll/caps/num lock isn't on.
- Get the latest 2.0.46-12 rpm of fvwm2.
- Don't (or alternately do) link xterm against Xa3wd.
- Change your video card.
All of the above have been exercises in futility for me (likewise for
many of the Dejanews posters). About the only suggestion that may be
worthwhile pursuing is to change from "ClickrToFocus" to the default
``Those who don't understand UNIX are condemned to reinvent it, poorly.''