Red Hat Bugzilla – Bug 428431
strange behavior with dogtail.rawinput.pressKey()
Last modified: 2013-09-02 02:23:09 EDT
+++ This bug was initially created as a clone of Bug #410291 +++
Description of problem:
Originaly filed as:
The VNC viewer used to show a xen guest's console doesn't handle AT-SPI events
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Use virt-install to start a Xen HVM (para virt should do as well) installation
2. Wait for the VNC console to appear
3. start python
3. use dogtail.rawinput.pressKey(':') which sould generate a key press event at
the VNC console
4. instead of colon ':' there appears a semi-colon ';'
VNC widget shows a semi-colon instead of colon
VNC widget shows the exact same characters as dogtail.rawinput instructs it to show.
Same behavior occurs with Fedora8/virt-viewer(GTK VNC widget) and
-- Additional comment from email@example.com on 2007-12-04 08:06 EST --
I am still not sure if the bug is in the viewer or the underlying GTK/VNC widget.
-- Additional comment from firstname.lastname@example.org on 2007-12-17 07:52 EST --
Xorg + vnc extension works for me. So i think this is vnc related issue.
-- Additional comment from email@example.com on 2007-12-17 09:05 EST --
Can you tell me what keymap you have configured on your local X desktop, what
keymap is configured inside the guest OS, and include the output of 'virsh
dumpxml [name of guest]' for the guest that you are trying to view.
-- Additional comment from firstname.lastname@example.org on 2007-12-18 04:23 EST --
Created an attachment (id=289867)
virsh dumpxml output
> keymap configured inside the guest OS
I'm not sure how do I tell. I hit the bug when booting the installation media.
> keymap configured on your local X desktop
Same here. I don't remember doing some speciffic settings in my GNOME session.
Which file should I look for that?
I've tried both when running GNOME and when running Xvnc without anything else
started. Hit the bug both times.
-- Additional comment from email@example.com on 2008-01-08 08:12 EST --
moving to at-spi component, since i'm pretty sure it's a bug in at-spi-registryd.
VNC server doesn't support XKB extension, and
contains this piece of code:
dec_lock_modifiers (SpiDEController *controller, unsigned modifiers)
return XkbLockModifiers (spi_get_display (), XkbUseCoreKbd,
So locking any modifier keys doesn't work through VNC.
-- Additional comment from firstname.lastname@example.org on 2008-01-10 10:10 EST --
provided a patch in the upstream bug, needs review though.
-- Additional comment from email@example.com on 2008-01-10 11:05 EST --
Michal provided custom build rpms for RHEL 5.1 and I verified that his patches work.
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".
Michal, I don't see a patch in the upstream bug.
Can you attach it there ? Or here. Or in both places...
(In reply to comment #3)
> Michal, I don't see a patch in the upstream bug.
> Can you attach it there ? Or here. Or in both places...
Patch is attached here:
Michal filed another BZ at GNOME's website.
Tested and verified with provided at-spi package from Michal.
Other packages were standard RHEL5.1
Built at-spi-1.7.11-3.el5 with the patch
Fails QA with:
Alex, can you provide more specifics than just "Fails QA" ?
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.