Package: vino Version: 2.28.2-2+squeeze1 Hello,
I don't think this is a new bug, so I sent it to both bug reports I could see which seem to be related with this problem. #407805 reports a change on 2007-09-01 in vino with regards to using XKB that should solve a keyboard problem, but #444220 appeared on 2007-09-26, a few weeks after this change, and is about an accent (so keyboard) problem, and is still open. My problem seems to be #444220. If you think I should open a separate bug, please tell me.
I have a French azerty keyboard: when my X session has been freshly started, using a remote VNC client (with also an azerty keyboard) to my session gives a qwerty keyboard instead (so different layout and no accent).
It took me time to find why it almost never worked correctly. sometimes it started working mysteriously but didn't survive a restart of my X session: in very few occasions I was using setxkbmap to map the "compose" key to type some foreign characters, and that's when it was working, but because I wasn't using VNC at this time, I couldn't discover the cause, and was finding VNC working, often only days after. I think some users are still bitten by this problem.
As soon as I'm using the command setxkbmap for any purpose (even just plain "setxkbmap"), immediately, even in the current vnc session, the keyboard mapping is fully corrected. I get azerty and all French accents, including AltGr or dead keys.
I can reproduce this problem by restarting my X session, and then work around it again by running once again setxkbmap.
What should be done about this? Check what's not working in vino? Have the vino package install a setxkbmap command to be run at the beginning of the X session? Document the issue in a README file?
regards, Adel BELHOUANE. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
