© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
One update: The problem can also be reproduced with Xubuntu 8.04 instead of Windows XP.
Emilio wrote:
> both with the client that works and the one that doesn't.
Hmm, when you say client do you refer to the vnc client (vinagre) on my machine 1 or the X clients on my machine 2?
There are too many clients here and maybe my configuration can be understood the easiest way be looking at the attached diagram.
I have the old vnc client (well actually it's the old library libgtk-vnc-1.0-0 version 0.3.7-0ubuntu2) and it does not work with any X client. (That's what this bug is all about.) It does not produce any debugging information about keycodes when starting it using the command vinagre --gtk-vnc-debug. (maybe the library needs to be built with an certain flag turned on???)
Next I have the new vnc client (well actually it's the new library libgtk-vnc-1.0-0 version 0.3.7-0ubuntu2.1) and it works with most X clients on the remote machine, but not with all. However, the debugging info from vinagre --gtk-vnc-debug, is always the same, regardless which X client on the remote machine has focus.
debugging info looks like this:
press keycode: 108 state: 0 group 0, keyval: 65027
press keycode: 20 state: 128 group 0, keyval: 92
release keycode: 20 state: 128 group 0, keyval: 92
release keycode: 108 state: 128 group 0, keyval: 65027
(Pressing AltGr, pressing the plus sign, which has the backslash in the AltGr position and releasing them in the opposite order)
I guess the vnc client side there is no knowledge about who has focus on the vnc server side. Key presses are just blindly transmitted from the vnc client to the vnc server.
But coming back to your question:
> Try investigating the output for vinagre --gtk-vnc-debug both with the client
> that works and the one that doesn't.
I could not do this, because
- only the new vnc client produced debugging output and
- the debugging output is the same for both X clients where AltGr works and X clients where AltGr doesn't work.
So I'm actually inclined to believe that your fix is valid for the vnc client side problem. (But there must be another bug somewhere in vino, the X server, or vmware running on my machine 2.)
Just to exclude any doubts: As mentioned erlier AltGr *does* work correctly for all clients on machine 2 when typing on the physical keyboard of machine 2.