Hendrik Tews <hendrik.t...@fireeye.com> writes: > Dear all, > > [sorry for crossposting - but I would like to connect different > sources about this problem] > > The problem is that fvwm does not install any keybindings when > started inside a vncserver, see Debian bug #784328 or Raphael's > post "Understanding why Key bindings are not installed" on the > fvwm mailing list on March 2, 2015. I have this problem with fvwm > 2.6.5 from Debian stable and vnc4server 4.1.1 and tightvncserver > 1.3.9. To reproduce the problem, start vncserver on your local > machine and start fvwm without any configuration inside that vnc > X xerver. Then open the FvwmCommand console and do PrintInfo > bindings there. > > The work around that I found is using the tigervncserver, in > there, fvwm installs the key bindings as expected. There are deb > packages of tigervncserver (follow releases -> the binary link on > bintray -> Files). They don't install right away on Debian > stable, but when you unpack them (dpkg -x) and make some > symlinks, you can run run the binaries. > > However, for me, tigervnc shows the Ctrl-space problem, i.e., > Ctrl-space is not transmitted correctly to applications inside > vnc, making it quite difficult to work with emacs inside > tigervnc. I am therefore still interested in a solution to the > fvwm key bindings problem. > > If anybody has a idea about how to convince fvwm to install key > bindings inside fvwm, please follow up on this email.
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. -- Dan Espen
