The workaround is not sufficient for everyone (certainly not me), since it has to be performed for every user. On multi-user systems, this can quickly become a problem. In addition, the workaround assumes that a US keyboard layout is OK for everyone, which is not the case when different layouts are used.
I've tested tightvncserver and vnc4server, both showed the same symptoms. I also tested with a number of different clients: tightvnc on Windows, Chicken of the VNC on Mac OS, and xvnc4viewer on Gutsy. No difference. The problem only occurs when logged into Gnome: GDM and KDE work perfectly. Is there anything I can do to pinpoint the problem further, so we can locate the problem? -- vino (vnc) keyboard mapping problem https://bugs.launchpad.net/bugs/112955 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
