Dan Espen <[email protected]> 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. Best regards, Hendrik This email and any attachments thereto may contain private, confidential, and/or privileged material for the sole use of the intended recipient. Any review, copying, or distribution of this email (or any attachments thereto) by others is strictly prohibited. If you are not the intended recipient, please contact the sender immediately and permanently delete the original and any copies of this email and any attachments thereto.
