Sorry, this is a production system.
I already rue the upgrade to gutsy because I experienced nasty problems with
setserial and lirc.
Using hardy is not an option.
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you are a m
Thanks Wolfgang.
With this workaround the keyboard works. I'm happy now.
BTW: I get a XKB error on Gnome startup. I think it complains about the unknown
"aa" layout.
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you are
After upgrade to Ubuntu 7.10 still suffering of this bug.
I'm tired of working with KDE...
@anonym: Would you tell me how to implement your "aa" fix?
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification because you are a member of Ubunt
> I'm one of the administrators who fell victim to this bug.
And do you know a workaround, which is not "walk around"?
To address the Ubuntu release process - I think this criterion for
"high-impact bugs" applies here: "Bugs which represent severe
regressions from the previous release of Ubuntu"
Which release of Ubuntu do you use? This bug is fixed only in unstable
7.10 and not in stable 7.04.
>From my point of view this bug has to be fixed in 7.04 too. This is a
major bug. It breaks VNC and makes Ubuntu unusable for a large group of
users, especially for admins managing lots of machines
It seems to depend on the language/keyboard setting during the Ubuntu
installation. If this is not US English, the keyboard via VNC is broken.
Please fix this bug in stable release.
--
vino (vnc) keyboard mapping problem
https://bugs.launchpad.net/bugs/112955
You received this bug notification b