[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#814959: marked as done (Keyboard mapping broken with Qt5 apps in TightVNC, possibly due to missing XKEYBOARD extension)

Your message dated Fri, 26 Apr 2019 11:32:58 +0300
with message-id <20190426083258.GA18461@mitya57.me>
and subject line Re: Not fixable until 5.11
has caused the Debian Bug report #814959,
regarding Keyboard mapping broken with Qt5 apps in TightVNC, possibly due to missing XKEYBOARD extension
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
814959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814959
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message --- 
Version: 5.11.0~rc1+dfsg-1

On Sat, Mar 17, 2018 at 03:35:56PM -0300, Lisandro Damián Nicanor Pérez Meyer wrote:
> reopen 814959
> reopen 818232
> thanks
>
> As shown by qtbase 5.10.1+dfsg-3 the patch is not straightforward, so
> I'm reopening the bugs which should be closed in 5.11.

We have Qt 5.11 for a while now (which includes the fix [1]), so I am
closing these bugs back.

[1]: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=3edcd9420e3ad661

--
Dmitry Shachnev

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: