Bug 428431

Summary: strange behavior with dogtail.rawinput.pressKey()
Product: Red Hat Enterprise Linux 5 Reporter: James Laska <jlaska>
Component: at-spiAssignee: Matthias Clasen <mclasen>
Status: CLOSED ERRATA QA Contact: desktop-bugs <desktop-bugs>
Severity: high Docs Contact:
Priority: low    
Version: 5.1CC: atkac, atodorov, hbrock, jlaska, jturner, mbabej
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHBA-2008-0469 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-05-21 15:38:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description James Laska 2008-01-11 14:04:46 UTC
+++ This bug was initially created as a clone of Bug #410291 +++

Description of problem:
Originaly filed as:
http://bugzilla.gnome.org/show_bug.cgi?id=501286
The VNC viewer used to show a xen guest's console doesn't handle AT-SPI events
correctly.

Version-Release number of selected component (if applicable):
virt-viewer-0.0.2-2.fc8

How reproducible:
Always

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 ';'
  
Actual results:
VNC widget shows a semi-colon instead of colon

Expected results:
VNC widget shows the exact same characters as dogtail.rawinput instructs it to show.

Additional info:
Same behavior occurs with Fedora8/virt-viewer(GTK VNC widget) and
RHEL5/vncviewer(vnc package).

-- Additional comment from atodorov@redhat.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 mbabej@redhat.com on 2007-12-17 07:52 EST --
Xorg + vnc extension works for me. So i think this is vnc related issue.

-- Additional comment from berrange@redhat.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 atodorov@redhat.com 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?

Additional info:
I've tried both when running GNOME and when running Xvnc without anything else
started. Hit the bug both times. 


-- Additional comment from mbabej@redhat.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
at-spi-1.18.1/registryd/deviceeventcontroller.c 
contains this piece of code:


static gboolean
dec_lock_modifiers (SpiDEController *controller, unsigned modifiers)
{
        return XkbLockModifiers (spi_get_display (), XkbUseCoreKbd, 
                          modifiers, modifiers);
}


So locking any modifier keys doesn't work through VNC.

-- Additional comment from mbabej@redhat.com on 2008-01-10 10:10 EST --
provided a patch in the upstream bug, needs review though.

-- Additional comment from atodorov@redhat.com on 2008-01-10 11:05 EST --
Michal provided custom build rpms for RHEL 5.1 and I verified that his patches work.

Comment 2 RHEL Product and Program Management 2008-01-11 14:15:44 UTC
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 "?".

Comment 3 Matthias Clasen 2008-01-11 14:21:44 UTC
Michal, I don't see a patch in the upstream bug. 

Can you attach it there ? Or here. Or in both places...

Comment 5 RHEL Product and Program Management 2008-01-14 16:25:43 UTC
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 "?".

Comment 6 Alexander Todorov 2008-01-15 13:06:32 UTC
(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:
http://bugzilla.gnome.org/show_bug.cgi?id=508147

Michal filed another BZ at GNOME's website.

Comment 7 Alexander Todorov 2008-01-15 13:13:28 UTC
Tested and verified with provided at-spi package from Michal.
Other packages were standard RHEL5.1

Comment 9 Matthias Clasen 2008-01-17 03:18:24 UTC
Built at-spi-1.7.11-3.el5 with the patch

Comment 11 Alexander Todorov 2008-04-02 09:49:59 UTC
Fails QA with:
at-spi-1.7.11-3.el5
dogtail-0.6.1-2.el5
virt-viewer-0.0.2-1.el5


Comment 13 Matthias Clasen 2008-04-02 15:26:38 UTC
Alex, can you provide more specifics than just "Fails QA" ?

Comment 18 errata-xmlrpc 2008-05-21 15:38:34 UTC
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.

http://rhn.redhat.com/errata/RHBA-2008-0469.html