Bug#814959: Keyboard mapping broken with Qt5 apps in TightVNC, possibly due to missing XKEYBOARD extension
¡Hola! El 2016-10-21 a las 08:43 -0300, Lisandro Damián Nicanor Pérez Meyer escribió: So I'm afraid this is not a Qt5 bug, but lack of proper support for XKEYBOARD (and thus Qt5 apps) in VNC servers/clients. Aparentely turbovnc [1], (which started as a tightvnc fork) has added the missing RANDR and XKEYBOARD extensions. Disclaimer: this is not packaged, I haven't tested it, nor I've checked it's openness. But if anyone has the time to work on this, please consider retitling #700517. [1]: https://sourceforge.net/projects/turbovnc/ Happy hacking, -- "There are only two things wrong with C++: The initial concept and the implementation." -- Bertrand Meyer Saludos /\/\ /\ >< `/ signature.asc Description: PGP signature
Bug#814959: Keyboard mapping broken with Qt5 apps in TightVNC, possibly due to missing XKEYBOARD extension
forcemerge 814959 818232 forwarded 814959 https://bugreports.qt.io/browse/QTBUG-44938 tag 814959 wontfix thanks On jueves, 20 de octubre de 2016 1:59:01 A. M. ART Linus Lüssing wrote: [snip] > Noticeably, on TightVNC and RealVNC, I get this error message, > while on TigerVNC I don't: > > "Qt: XKEYBOARD extension not present on the X server." > > So looks like James initial investigations lead to the right > direction. > > Unfortunately, this report on the Qt bugtracker indicates that it > was closed and deemed "out of scope" and that VNC servers should > implement this XKEYBOARD extension :-( : > > https://bugreports.qt.io/browse/QTBUG-44938 > > This ticket also has some nice explanations why Qt5 has this issue > and Qt4 doesn't (e.g. the preference of libxkbcommon over xlib in > Qt5). So I'm afraid this is not a Qt5 bug, but lack of proper support for XKEYBOARD (and thus Qt5 apps) in VNC servers/clients. I'm marking this as wontfix because it will never get "fixed" from the Qt side. I suggest you to open the proper bugs to your VNC servers/clients. Kinds regards, Lisandro. -- Lo que me sorprende de las mujeres es que se arrancan los pelos desde la raíz con cera caliente y aún así le temen a las arañas. Jerry Seinfeld lis: comentario sobre tu frase yo soy mujer, yo me arranco los pelos y VOS le tenes miedo a las arañas María Luján Pérez Meyer (mi hermana) Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#814959: Keyboard mapping broken with Qt5 apps in TightVNC, possibly due to missing XKEYBOARD extension
I stumbled over this issue with various Qt5 applications on Debian Sid, too, and had initially reported my issue here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818232 Switching the VNC viewer does not seem to help, I tried xtightvncviewer and krdc. Not only the TightVNC server, but also the RealVNC one (vnc4server package) seem to be affected. TigerVNC on the other hand works like a charm (which is my current workaround for this issue for now). Noticeably, on TightVNC and RealVNC, I get this error message, while on TigerVNC I don't: "Qt: XKEYBOARD extension not present on the X server." So looks like James initial investigations lead to the right direction. Unfortunately, this report on the Qt bugtracker indicates that it was closed and deemed "out of scope" and that VNC servers should implement this XKEYBOARD extension :-( : https://bugreports.qt.io/browse/QTBUG-44938 This ticket also has some nice explanations why Qt5 has this issue and Qt4 doesn't (e.g. the preference of libxkbcommon over xlib in Qt5). Regards, Linus
Bug#814959: Keyboard mapping broken with Qt5 apps in TightVNC, possibly due to missing XKEYBOARD extension
Hi, I can reproduce this with both the versions of Qt 5 in testing and unstable (libqt5gui5 versions 5.5.1+dfsg-13 and 5.5.1+dfsg-14 respectively). tightvncserver has version 1.3.9-7 on this installation of testing. Best, James On 17/02/2016 2:41 AM, Lisandro Damián Nicanor Pérez Meyer wrote: > Control: tag -1 moreinfo > > Can you test if it also happens with testing's qt5? If it doesn't I can > submit a bug upstream, if it does work we would need to isolate the > patches that fixed that. > > -- > Lisandro Damián Nicanor Pérez Meyer > http://perezmeyer.com.ar/ > http://perezmeyer.blogspot.com/ > signature.asc Description: OpenPGP digital signature
Bug#814959: Keyboard mapping broken with Qt5 apps in TightVNC, possibly due to missing XKEYBOARD extension
Control: tag -1 moreinfo Can you test if it also happens with testing's qt5? If it doesn't I can submit a bug upstream, if it does work we would need to isolate the patches that fixed that. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
Bug#814959: Keyboard mapping broken with Qt5 apps in TightVNC, possibly due to missing XKEYBOARD extension
Source: qtbase-opensource-src Version: 5.3.2+dfsg-4+deb8u1 Severity: important Justification: makes keyboard usage impossible in apps using Qt5 Dear maintainers, Using Openbox via TightVNC on a Debian Jessie server, I've been running into a strange issue where the keyboard mapping in Qt5 apps is all wrong. For example, "asdf" on a US keyboard gets mapped to "abfh", and "qwerty" comes out as "c.gvn". I've looked online to find solutions or workarounds, and found only some similar issues and no real fix. Searching "asdf abfh vnc" brought me to https://bbs.archlinux.org/viewtopic.php?id=81427, though that only shows a workaround for GNOME. Other sources point to missing XKEYBOARD extension in VNC implementations as a cause for breakage, though the workaround with XKB_DEFAULT_RULES=base hasn't worked for me: https://bugreports.qt.io/browse/QTBUG-44938 Strangely enough, this only affects apps using Qt5 (Qt designer, Transmission-qt, various PyQt5 programs). In programs using GTK2/3 or Qt4 (qtconfig, VLC), I can type just fine. For reference, my installed tightvncserver version is 1.3.9-6.5, and my client is running Windows 7 with the TightVNC Java client, version 2.7.2. Best, James signature.asc Description: OpenPGP digital signature
