Still the same problem with server version 21 dec 2010. Main keyboard numbers from 1 to 0 gives 12345^67890, 6 comes with ^ in front. Numpad numbers gives 1234567890, is correct. Viewer is 2.0.2
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What program using to display the characters?
You can attach zipped log files of the server and viewer towards the wrong characters (log verbosity level = 9).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I sent you a file with a session of typing 0123456789 into Start > cmdline
All applications produces the same error. Ultraviewer used with same result.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I made the new tvnserver.exe version with more detailed logs. Please repeat the test and attach the logs again. I must make sure that is the server problem because I can't reproduce it.
Another question: Do you use any key catcher or a key spier or a keyboard layout switcher or another utility that may hook your keyboard?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Updated file shows that last version gives ^6 on the numpad aswel, but only after pressing the main 6 on the keyboard first. Pressed after other keys it gives a normal 6 as response.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I work around the bug. But it seems this a Winapi bug that appears on the combination:
language - Netherland
keyboard - USA
I sent a question to the msdn forum yesterday, but still no replies.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
> If yes, are u going to publish the code with a fix soon ?
If we are able to fix the bug, the fix would be available in the next TightVNC source code release. Our code repository is not publicly available at the moment, sorry. If your company needs closer collaboration and technical support, please consider purchasing a support contract:
Normal setting Dutch language and USA (international ) keyboard.
I've tried it with language = English and keyboard = USA (normal) NO error!
And with English language and USA (international) keyboard is error!
Conclusion: If switching between USA(normal) and USA(international) keyboard layouts you can see the differences. I think it's not the language, but keyboard handeling (imo). I need USA international keyboard (mostly used in the netherlands) to use accents in combination with characters.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've made two log files with two sesions. One with us keyboard and one with us international keyboard.
In the first one is keyboard layout is 0x04090409 and in the second one the layout is 0xF0010409. Maybe this info will help?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm using server version 2.0.3 on Windows 7, which was supposed to have fixed this bug. Nonetheless, when I log in from my Android device using RealVNC's viewer, and I enter the number 6 on the soft keyboard, it produces ^6 on the server.
It's worth noting that I don't use exactly the US-International keyboard but a version I modified myself to include additional sticky keys. But the only one that seems to cause problems is the carat on the 6.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi I have the same problem using the keyboard Portuguese (Brazil) ABNT2 or ABNT; English keyboard (USA), or us united states (international). In Brazil the character keypad on the 6 is the umlaut (¨) instead of the character (^), but the situation is the same as reported in this bug. I'm using version 2.0.4 (built on 3 aug 2011 at 20:17:46) on the server with windows vista and windows vista and 7 on the client, the java version 1.6.0.31. I noticed that the problem only occurs with the use of applets, which did not happen with the client (viewer).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi. I have had this problem for years and it is still a problem when connecting to windows machines with TightVNC Server. On linux machines I tend to use x11vnc as server and this problem does not happen on those. I get an umlaut before each numer 6 pressed. I have tried updating both my client and the remote server versions and the problem persists. Any ideas? This is quite annoying and causes all sorts of problems.
Most machines I connect to use Brazilian Portuguese language with ABNT keyboar (some use "US international" keyboard and have the same problem).
Example attached.
Please test the latest version of the tvnserver.exe file:
http://www.tightvnc.com/tmp/tvnserver-101221.zip
Please let me know if the bug still happens.
Still the same problem with server version 21 dec 2010. Main keyboard numbers from 1 to 0 gives 12345^67890, 6 comes with ^ in front. Numpad numbers gives 1234567890, is correct. Viewer is 2.0.2
What program using to display the characters?
You can attach zipped log files of the server and viewer towards the wrong characters (log verbosity level = 9).
I sent you a file with a session of typing 0123456789 into Start > cmdline
All applications produces the same error. Ultraviewer used with same result.
I made the new tvnserver.exe version with more detailed logs. Please repeat the test and attach the logs again. I must make sure that is the server problem because I can't reproduce it.
Another question: Do you use any key catcher or a key spier or a keyboard layout switcher or another utility that may hook your keyboard?
Sorry, Forgot:
Link to the new version:
http://www.tightvnc.com/tmp/tvnserver-110112.zip
With version 110112 both keyboard 6's give ^6! see log files.
Oops, forget last file I sent you!!!!! Wrong one!
In the file i sent you, you'll find two sessions of enter a string 1234567890 in Start > cmdline. The last version gives ^6 on the numpad also.
Updated file shows that last version gives ^6 on the numpad aswel, but only after pressing the main 6 on the keyboard first. Pressed after other keys it gives a normal 6 as response.
Hi Syuri,
Has this bug been fixed ? If yes, are u going to publish the code with a fix soon ? We need the code for our internal use.
Thanks
Milind
I work around the bug. But it seems this a Winapi bug that appears on the combination:
language - Netherland
keyboard - USA
I sent a question to the msdn forum yesterday, but still no replies.
Thanks syuri. While debugging, I also came to this conclusion. I'm also noticing this bug on the combination you mentioned.
Any chance you will be publishing the work around ?
Sorry, I incorrectly put. I working on the bug!
Hello Milind,
> If yes, are u going to publish the code with a fix soon ?
If we are able to fix the bug, the fix would be available in the next TightVNC source code release. Our code repository is not publicly available at the moment, sorry. If your company needs closer collaboration and technical support, please consider purchasing a support contract:
http://www.tightvnc.com/support.php
If you have any questions, please contact us at the e-mail included in the page mentioned above.
> We need the code for our internal use.
Do you publish the code modifications under the GNU GPL terms?
Regards,
Constantin
Thanks for your response Constantin.
If we make the change, we will be publishing the code modification as per GNU GPL terms.
Normal setting Dutch language and USA (international ) keyboard.
I've tried it with language = English and keyboard = USA (normal) NO error!
And with English language and USA (international) keyboard is error!
Conclusion: If switching between USA(normal) and USA(international) keyboard layouts you can see the differences. I think it's not the language, but keyboard handeling (imo). I need USA international keyboard (mostly used in the netherlands) to use accents in combination with characters.
I've made two log files with two sesions. One with us keyboard and one with us international keyboard.
In the first one is keyboard layout is 0x04090409 and in the second one the layout is 0xF0010409. Maybe this info will help?
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs"
I'm using server version 2.0.3 on Windows 7, which was supposed to have fixed this bug. Nonetheless, when I log in from my Android device using RealVNC's viewer, and I enter the number 6 on the soft keyboard, it produces ^6 on the server.
It's worth noting that I don't use exactly the US-International keyboard but a version I modified myself to include additional sticky keys. But the only one that seems to cause problems is the carat on the 6.
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs"
I just wanted to add, half a year later, this bug is still ongoing. Any progress?
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs"
Hi I have the same problem using the keyboard Portuguese (Brazil) ABNT2 or ABNT; English keyboard (USA), or us united states (international). In Brazil the character keypad on the 6 is the umlaut (¨) instead of the character (^), but the situation is the same as reported in this bug. I'm using version 2.0.4 (built on 3 aug 2011 at 20:17:46) on the server with windows vista and windows vista and 7 on the client, the java version 1.6.0.31. I noticed that the problem only occurs with the use of applets, which did not happen with the client (viewer).
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs"
Bright, the latest version corrected the problems in this bug, and added new features very good. Congratulations. Consider the bug closed.
Hi. I have had this problem for years and it is still a problem when connecting to windows machines with TightVNC Server. On linux machines I tend to use x11vnc as server and this problem does not happen on those. I get an umlaut before each numer 6 pressed. I have tried updating both my client and the remote server versions and the problem persists. Any ideas? This is quite annoying and causes all sorts of problems.
Most machines I connect to use Brazilian Portuguese language with ABNT keyboar (some use "US international" keyboard and have the same problem).
Example attached.