On Sat, 7 Aug 2021, Sven Geuer wrote:
I tried to reproduce your observation using tightvncserver 1:1.3.10-3
but didn't encounter any key mapping issues.
Can you provide me with instuctions how to verify this bugs still
persists?
I've been continuing with TigerVNC for the nearly 5 years since this
bug, so it's quite possible ... something ... changed and it's not
broken any more :)
FWIW, my setup hasn't really changed much, however. The vnc server runs
my ~/.xsession which:
1. xscreensver &
2. xset s off
3. osdsh
4. echo "Xft.dpi: $(xdpyinfo | sed -nre
'/^[[:space:]]*resolution:[[:space:]]*([0-9]+)x([0-9]+) dots per inch.*/{s/^.*x([0-9]+)
dots .*/\1/;p}')" | xrdb -
(I've no idea why this is in there ... parts of this .xsession script
are literally 20 years old. I think this is maybe a workaround for
some issues with weird font sizes under VNC)
5. exec wmaker
--
-- Matt
"Reality is that which, when you stop believing in it, doesn't go away".
-- Philip K. Dick
GPG fingerprint: 0061 15DF D282 D4A9 57CE 77C5 16AF 1460 4A3C C4E9
