keyboard mapping wrong only in specific applications under TightVNC
Clash Royale CLAN TAG#URR8PPP
up vote
5
down vote
favorite
I searched pretty thoroughly and I could only find posts in which people have keyboard mappings that are wrong system-wide, however I have a bizarre situation in which most applications work OK, but some are completely wrong:
I am running Ubuntu 16.04 server with xfce installed (never had Unity/GNOME).
I am running tightserver.
I remote in and everything that comes with xfce seems to work. I installed various applications.
The following do work:
- gedit
- firefox
- filezilla
- gimp
The following do not work:
- notepadqq
- qbittorrent
in notepadqq I get the following (left is keypressed, right is key displayed)
a=a
b=s
c=d
d=f
e=g
(if important I will make full list)
I feel like there most be something very specific that would cause this, that is I don't think it has anything to do with processor load/hardware glitch/power fluctuation. Why would specific applications behave this way?
x11 keyboard-layout vnc qt tightvnc
edited Feb 26 '17 at 14:39
Jeff Schaller
33.1k849111
asked Feb 19 '17 at 13:49
Jesse Adam
6817
 |Â
show 1 more comment
up vote
5
down vote
favorite
I searched pretty thoroughly and I could only find posts in which people have keyboard mappings that are wrong system-wide, however I have a bizarre situation in which most applications work OK, but some are completely wrong:
I am running Ubuntu 16.04 server with xfce installed (never had Unity/GNOME).
I am running tightserver.
I remote in and everything that comes with xfce seems to work. I installed various applications.
The following do work:
- gedit
- firefox
- filezilla
- gimp
The following do not work:
- notepadqq
- qbittorrent
in notepadqq I get the following (left is keypressed, right is key displayed)
a=a
b=s
c=d
d=f
e=g
(if important I will make full list)
I feel like there most be something very specific that would cause this, that is I don't think it has anything to do with processor load/hardware glitch/power fluctuation. Why would specific applications behave this way?
x11 keyboard-layout vnc qt tightvnc
edited Feb 26 '17 at 14:39
Jeff Schaller
33.1k849111
asked Feb 19 '17 at 13:49
Jesse Adam
6817
Notepadqq and qbittorrent both use the Qt library, so the common factor is presumably some Qt bug or strange configuration. Can you try other Qt/KDE to check if they're also failing? What keyboard layout do you use and how is it configured? Where (what OS and client software) are you remoting from and can you reproduce the problem locally or with a different way of remoting?
– Gilles
Feb 19 '17 at 19:33
1
The following Clients all have the same problem: Windows RealVNC Windows TightVNC OSX RealVNC OSX native screenshare
– Jesse Adam
Feb 20 '17 at 21:11
@Gilles I'm having trouble getting Qt programs to install, Filezilla works (I don't know if it still uses Qt), I installed Qt configuration tool and that seems OK, is there a specific program you recommend I try?
– Jesse Adam
Feb 21 '17 at 3:17
Filezilla doesn't use Qt. The Qt configuration tool does. That's quite a mysterious bug here. Have you found a client that doesn't have this bug? Can you try remoting with something other than tightvncserver? It would help to figure out whether the problem is on the server side or on the client side.
– Gilles
Feb 21 '17 at 12:36
I know this is an old-ish thread, I've just seen this exact same problem with Virtualbox Manager on a brand new minimal Ubuntu server running XFCE over tightvncserver. All the locale was there, keyboard mapping perfect on most apps but Virtualbox character input was as described above. Took me an age to find this post; I solved my problem by using vnc4server instead of tightvncserver (no change to client) and everything now working perfectly.
– Aitch
Jun 2 '17 at 11:18
 |Â
show 1 more comment
up vote
5
down vote
favorite
up vote
5
down vote
favorite
I searched pretty thoroughly and I could only find posts in which people have keyboard mappings that are wrong system-wide, however I have a bizarre situation in which most applications work OK, but some are completely wrong:
I am running Ubuntu 16.04 server with xfce installed (never had Unity/GNOME).
I am running tightserver.
I remote in and everything that comes with xfce seems to work. I installed various applications.
The following do work:
- gedit
- firefox
- filezilla
- gimp
The following do not work:
- notepadqq
- qbittorrent
in notepadqq I get the following (left is keypressed, right is key displayed)
a=a
b=s
c=d
d=f
e=g
(if important I will make full list)
I feel like there most be something very specific that would cause this, that is I don't think it has anything to do with processor load/hardware glitch/power fluctuation. Why would specific applications behave this way?
x11 keyboard-layout vnc qt tightvnc
edited Feb 26 '17 at 14:39
Jeff Schaller
33.1k849111
asked Feb 19 '17 at 13:49
Jesse Adam
6817
I searched pretty thoroughly and I could only find posts in which people have keyboard mappings that are wrong system-wide, however I have a bizarre situation in which most applications work OK, but some are completely wrong:
I am running Ubuntu 16.04 server with xfce installed (never had Unity/GNOME).
I am running tightserver.
I remote in and everything that comes with xfce seems to work. I installed various applications.
The following do work:
- gedit
- firefox
- filezilla
- gimp
The following do not work:
- notepadqq
- qbittorrent
in notepadqq I get the following (left is keypressed, right is key displayed)
a=a
b=s
c=d
d=f
e=g
(if important I will make full list)
I feel like there most be something very specific that would cause this, that is I don't think it has anything to do with processor load/hardware glitch/power fluctuation. Why would specific applications behave this way?
x11 keyboard-layout vnc qt tightvnc
x11 keyboard-layout vnc qt tightvnc
edited Feb 26 '17 at 14:39
Jeff Schaller
33.1k849111
asked Feb 19 '17 at 13:49
Jesse Adam
6817
edited Feb 26 '17 at 14:39
Jeff Schaller
33.1k849111
asked Feb 19 '17 at 13:49
Jesse Adam
6817
edited Feb 26 '17 at 14:39
Jeff Schaller
33.1k849111
edited Feb 26 '17 at 14:39
Jeff Schaller
33.1k849111
edited Feb 26 '17 at 14:39
Jeff Schaller
33.1k849111
33.1k849111
asked Feb 19 '17 at 13:49
Jesse Adam
6817
asked Feb 19 '17 at 13:49
Jesse Adam
6817
asked Feb 19 '17 at 13:49
Jesse Adam
6817
6817
Notepadqq and qbittorrent both use the Qt library, so the common factor is presumably some Qt bug or strange configuration. Can you try other Qt/KDE to check if they're also failing? What keyboard layout do you use and how is it configured? Where (what OS and client software) are you remoting from and can you reproduce the problem locally or with a different way of remoting?
– Gilles
Feb 19 '17 at 19:33
1
The following Clients all have the same problem: Windows RealVNC Windows TightVNC OSX RealVNC OSX native screenshare
– Jesse Adam
Feb 20 '17 at 21:11
@Gilles I'm having trouble getting Qt programs to install, Filezilla works (I don't know if it still uses Qt), I installed Qt configuration tool and that seems OK, is there a specific program you recommend I try?
– Jesse Adam
Feb 21 '17 at 3:17
Filezilla doesn't use Qt. The Qt configuration tool does. That's quite a mysterious bug here. Have you found a client that doesn't have this bug? Can you try remoting with something other than tightvncserver? It would help to figure out whether the problem is on the server side or on the client side.
– Gilles
Feb 21 '17 at 12:36
I know this is an old-ish thread, I've just seen this exact same problem with Virtualbox Manager on a brand new minimal Ubuntu server running XFCE over tightvncserver. All the locale was there, keyboard mapping perfect on most apps but Virtualbox character input was as described above. Took me an age to find this post; I solved my problem by using vnc4server instead of tightvncserver (no change to client) and everything now working perfectly.
– Aitch
Jun 2 '17 at 11:18
 |Â
show 1 more comment
Notepadqq and qbittorrent both use the Qt library, so the common factor is presumably some Qt bug or strange configuration. Can you try other Qt/KDE to check if they're also failing? What keyboard layout do you use and how is it configured? Where (what OS and client software) are you remoting from and can you reproduce the problem locally or with a different way of remoting?
– Gilles
Feb 19 '17 at 19:33
1
The following Clients all have the same problem: Windows RealVNC Windows TightVNC OSX RealVNC OSX native screenshare
– Jesse Adam
Feb 20 '17 at 21:11
@Gilles I'm having trouble getting Qt programs to install, Filezilla works (I don't know if it still uses Qt), I installed Qt configuration tool and that seems OK, is there a specific program you recommend I try?
– Jesse Adam
Feb 21 '17 at 3:17
Filezilla doesn't use Qt. The Qt configuration tool does. That's quite a mysterious bug here. Have you found a client that doesn't have this bug? Can you try remoting with something other than tightvncserver? It would help to figure out whether the problem is on the server side or on the client side.
– Gilles
Feb 21 '17 at 12:36
I know this is an old-ish thread, I've just seen this exact same problem with Virtualbox Manager on a brand new minimal Ubuntu server running XFCE over tightvncserver. All the locale was there, keyboard mapping perfect on most apps but Virtualbox character input was as described above. Took me an age to find this post; I solved my problem by using vnc4server instead of tightvncserver (no change to client) and everything now working perfectly.
– Aitch
Jun 2 '17 at 11:18
Notepadqq and qbittorrent both use the Qt library, so the common factor is presumably some Qt bug or strange configuration. Can you try other Qt/KDE to check if they're also failing? What keyboard layout do you use and how is it configured? Where (what OS and client software) are you remoting from and can you reproduce the problem locally or with a different way of remoting?
– Gilles
Feb 19 '17 at 19:33
Notepadqq and qbittorrent both use the Qt library, so the common factor is presumably some Qt bug or strange configuration. Can you try other Qt/KDE to check if they're also failing? What keyboard layout do you use and how is it configured? Where (what OS and client software) are you remoting from and can you reproduce the problem locally or with a different way of remoting?
– Gilles
Feb 19 '17 at 19:33
1
1
The following Clients all have the same problem: Windows RealVNC Windows TightVNC OSX RealVNC OSX native screenshare
– Jesse Adam
Feb 20 '17 at 21:11
The following Clients all have the same problem: Windows RealVNC Windows TightVNC OSX RealVNC OSX native screenshare
– Jesse Adam
Feb 20 '17 at 21:11
@Gilles I'm having trouble getting Qt programs to install, Filezilla works (I don't know if it still uses Qt), I installed Qt configuration tool and that seems OK, is there a specific program you recommend I try?
– Jesse Adam
Feb 21 '17 at 3:17
@Gilles I'm having trouble getting Qt programs to install, Filezilla works (I don't know if it still uses Qt), I installed Qt configuration tool and that seems OK, is there a specific program you recommend I try?
– Jesse Adam
Feb 21 '17 at 3:17
Filezilla doesn't use Qt. The Qt configuration tool does. That's quite a mysterious bug here. Have you found a client that doesn't have this bug? Can you try remoting with something other than tightvncserver? It would help to figure out whether the problem is on the server side or on the client side.
– Gilles
Feb 21 '17 at 12:36
Filezilla doesn't use Qt. The Qt configuration tool does. That's quite a mysterious bug here. Have you found a client that doesn't have this bug? Can you try remoting with something other than tightvncserver? It would help to figure out whether the problem is on the server side or on the client side.
– Gilles
Feb 21 '17 at 12:36
I know this is an old-ish thread, I've just seen this exact same problem with Virtualbox Manager on a brand new minimal Ubuntu server running XFCE over tightvncserver. All the locale was there, keyboard mapping perfect on most apps but Virtualbox character input was as described above. Took me an age to find this post; I solved my problem by using vnc4server instead of tightvncserver (no change to client) and everything now working perfectly.
– Aitch
Jun 2 '17 at 11:18
I know this is an old-ish thread, I've just seen this exact same problem with Virtualbox Manager on a brand new minimal Ubuntu server running XFCE over tightvncserver. All the locale was there, keyboard mapping perfect on most apps but Virtualbox character input was as described above. Took me an age to find this post; I solved my problem by using vnc4server instead of tightvncserver (no change to client) and everything now working perfectly.
– Aitch
Jun 2 '17 at 11:18
 |Â
show 1 more comment
2 Answers
2
active
oldest
votes
up vote
4
down vote
accepted
This sounds very much like a known bug: TightVNC doesn't support XKEYBOARD, which confuses Qt5. (XKEYBOARD is one of several widely-supported extensions to the original X11 protocol.) The bug report against the Qt project has a comment that states that it is unlikely to be fixed because lack of XKEYBOARD is rare. The Debian bug report suggests using TurboVNC instead of TightVNC; it's a fork of TightVNC which implements some additional extensions including XKEYBOARD.
answered Feb 21 '17 at 18:41
Gilles
511k12010141543
This should be the accepted answer; in my case on Ubuntu Server (with minimal XFCE install) and tightvncserver, switching to vnc4server similar to suggestion above fixed the problem immediately.
– Aitch
Jun 2 '17 at 11:20
add a comment |Â
up vote
0
down vote
TigerVNC might also be an option. I find the server to be faster and the client to be simple but adequate for most requirements.
answered Apr 2 at 18:33
G. Cito
1012
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
4
down vote
accepted
This sounds very much like a known bug: TightVNC doesn't support XKEYBOARD, which confuses Qt5. (XKEYBOARD is one of several widely-supported extensions to the original X11 protocol.) The bug report against the Qt project has a comment that states that it is unlikely to be fixed because lack of XKEYBOARD is rare. The Debian bug report suggests using TurboVNC instead of TightVNC; it's a fork of TightVNC which implements some additional extensions including XKEYBOARD.
answered Feb 21 '17 at 18:41
Gilles
511k12010141543
This should be the accepted answer; in my case on Ubuntu Server (with minimal XFCE install) and tightvncserver, switching to vnc4server similar to suggestion above fixed the problem immediately.
– Aitch
Jun 2 '17 at 11:20
add a comment |Â
up vote
4
down vote
accepted
This sounds very much like a known bug: TightVNC doesn't support XKEYBOARD, which confuses Qt5. (XKEYBOARD is one of several widely-supported extensions to the original X11 protocol.) The bug report against the Qt project has a comment that states that it is unlikely to be fixed because lack of XKEYBOARD is rare. The Debian bug report suggests using TurboVNC instead of TightVNC; it's a fork of TightVNC which implements some additional extensions including XKEYBOARD.
answered Feb 21 '17 at 18:41
Gilles
511k12010141543
This should be the accepted answer; in my case on Ubuntu Server (with minimal XFCE install) and tightvncserver, switching to vnc4server similar to suggestion above fixed the problem immediately.
– Aitch
Jun 2 '17 at 11:20
add a comment |Â
up vote
4
down vote
accepted
up vote
4
down vote
accepted
This sounds very much like a known bug: TightVNC doesn't support XKEYBOARD, which confuses Qt5. (XKEYBOARD is one of several widely-supported extensions to the original X11 protocol.) The bug report against the Qt project has a comment that states that it is unlikely to be fixed because lack of XKEYBOARD is rare. The Debian bug report suggests using TurboVNC instead of TightVNC; it's a fork of TightVNC which implements some additional extensions including XKEYBOARD.
answered Feb 21 '17 at 18:41
Gilles
511k12010141543
This sounds very much like a known bug: TightVNC doesn't support XKEYBOARD, which confuses Qt5. (XKEYBOARD is one of several widely-supported extensions to the original X11 protocol.) The bug report against the Qt project has a comment that states that it is unlikely to be fixed because lack of XKEYBOARD is rare. The Debian bug report suggests using TurboVNC instead of TightVNC; it's a fork of TightVNC which implements some additional extensions including XKEYBOARD.
answered Feb 21 '17 at 18:41
Gilles
511k12010141543
answered Feb 21 '17 at 18:41
Gilles
511k12010141543
answered Feb 21 '17 at 18:41
Gilles
511k12010141543
answered Feb 21 '17 at 18:41
Gilles
511k12010141543
511k12010141543
This should be the accepted answer; in my case on Ubuntu Server (with minimal XFCE install) and tightvncserver, switching to vnc4server similar to suggestion above fixed the problem immediately.
– Aitch
Jun 2 '17 at 11:20
add a comment |Â
This should be the accepted answer; in my case on Ubuntu Server (with minimal XFCE install) and tightvncserver, switching to vnc4server similar to suggestion above fixed the problem immediately.
– Aitch
Jun 2 '17 at 11:20
This should be the accepted answer; in my case on Ubuntu Server (with minimal XFCE install) and tightvncserver, switching to vnc4server similar to suggestion above fixed the problem immediately.
– Aitch
Jun 2 '17 at 11:20
This should be the accepted answer; in my case on Ubuntu Server (with minimal XFCE install) and tightvncserver, switching to vnc4server similar to suggestion above fixed the problem immediately.
– Aitch
Jun 2 '17 at 11:20
add a comment |Â
up vote
0
down vote
TigerVNC might also be an option. I find the server to be faster and the client to be simple but adequate for most requirements.
answered Apr 2 at 18:33
G. Cito
1012
add a comment |Â
up vote
0
down vote
TigerVNC might also be an option. I find the server to be faster and the client to be simple but adequate for most requirements.
answered Apr 2 at 18:33
G. Cito
1012
add a comment |Â
up vote
0
down vote
up vote
0
down vote
TigerVNC might also be an option. I find the server to be faster and the client to be simple but adequate for most requirements.
answered Apr 2 at 18:33
G. Cito
1012
TigerVNC might also be an option. I find the server to be faster and the client to be simple but adequate for most requirements.
answered Apr 2 at 18:33
G. Cito
1012
answered Apr 2 at 18:33
G. Cito
1012
answered Apr 2 at 18:33
G. Cito
1012
answered Apr 2 at 18:33
G. Cito
1012
1012
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f346107%2fkeyboard-mapping-wrong-only-in-specific-applications-under-tightvnc%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Notepadqq and qbittorrent both use the Qt library, so the common factor is presumably some Qt bug or strange configuration. Can you try other Qt/KDE to check if they're also failing? What keyboard layout do you use and how is it configured? Where (what OS and client software) are you remoting from and can you reproduce the problem locally or with a different way of remoting?
– Gilles
Feb 19 '17 at 19:33
1
The following Clients all have the same problem: Windows RealVNC Windows TightVNC OSX RealVNC OSX native screenshare
– Jesse Adam
Feb 20 '17 at 21:11
@Gilles I'm having trouble getting Qt programs to install, Filezilla works (I don't know if it still uses Qt), I installed Qt configuration tool and that seems OK, is there a specific program you recommend I try?
– Jesse Adam
Feb 21 '17 at 3:17
Filezilla doesn't use Qt. The Qt configuration tool does. That's quite a mysterious bug here. Have you found a client that doesn't have this bug? Can you try remoting with something other than tightvncserver? It would help to figure out whether the problem is on the server side or on the client side.
– Gilles
Feb 21 '17 at 12:36
I know this is an old-ish thread, I've just seen this exact same problem with Virtualbox Manager on a brand new minimal Ubuntu server running XFCE over tightvncserver. All the locale was there, keyboard mapping perfect on most apps but Virtualbox character input was as described above. Took me an age to find this post; I solved my problem by using vnc4server instead of tightvncserver (no change to client) and everything now working perfectly.
– Aitch
Jun 2 '17 at 11:18