Hendrik Tews <hendrik.t...@fireeye.com> writes: > Dan Espen <des...@verizon.net> writes: > >> On the Debian list they say: >> >> So after all, this bug may have been triggered by a change in VNC >> rather than in FVWM. >> >> I don't see how Fvwm can help. >> Try the VNC folks. > > I agree that it looks like the problem is outside fvwm. However, > I expect there are only a few circumstances that can cause > PrintInfo Bindings to not output the default builtin F1 > keybinding on fvwm started without configuration. I would have > hoped that the fvwm developers could provide some information > about these circumstances, for instance about presence or absence > of certain X server extensions that can trigger that behavior.
Good point. Current Fvwm is from CVS on the 2_6 branch. I don't know if there have been changes that affect key bindings but I can take a look. Since I'll be looking at current CVS it would be helpful to know whether the problem exists there. -- Dan Espen
