Control: retitle -1 tightvncserver: XKeyboard extension not available
Control: tags -1 = wontfix
Hi Matthew,
On Fri, 2021-08-13 at 23:15 -0400, Matthew Gabeler-Lee wrote:
> [...]
> 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
>
Thanks for providing your .xsession file. I was able to reproduce your
observations in some way, even without any explicit .xsession file.
With xkeycaps, for example pressing the '1' key a KeySym of '1' is
reported while the KeyCode is '9'. That's the other way around than you
described it originally, what may have happened erroneously.
bitcoin-qt doesn't even start up, it aborts complaining
qt.qpa.xcb: XKeyboard extension not present on the X server
And indeed, the X server incorporated in tightvncserver does not
provide the XKeyboard extension, xdpyinfo does not list it. It is
available from the source, but the build instructions explicitly
disable it for whatever reason.
This is an upstream related issue therefore, but upstream does not
maintain Thightvnc on Linux any more. Thus, do not expect the XKeyboard
extension to be implemented in tightvncserver going forward.
Sorry for the bad news!
Sven
--
GPG Fingerprint
3DF5 E8AA 43FC 9FDF D086 F195 ADF5 0EDA F8AD D585
Attachment:
signature.asc
Description: This is a digitally signed message part