Bug 380051 - br-abnt2 keymap unassigned
br-abnt2 keymap unassigned
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: virt-manager (Show other bugs)
8
All Linux
low Severity high
: ---
: ---
Assigned To: Daniel Berrange
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-11-13 09:04 EST by Davidson Paulo
Modified: 2008-03-14 23:47 EDT (History)
1 user (show)

See Also:
Fixed In Version: 0.5.3
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-03-14 23:47:24 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Davidson Paulo 2007-11-13 09:04:31 EST
Description of problem:

br-abnt2 keymap is not assigned to any vnc keymap, so when creating a virtual
machine there is no way to use a br-abnt2 (Brazilian ABNT 2) keyboard.

Version-Release number of selected component (if applicable):


How reproducible:

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

To fix, just insert the following line in
/usr/share/virt-manager/virtManager/keymap.py:

"br-abnt2":"pt-br",

Recompile the file:

# python /usr/lib/python2.5/compileall.py /usr/share/virt-manager/virtManager/

Restart libvirtd:

# service libvirtd restart

Stop the virtual machine:

# virsh shutdown [Domain]

Redefine it:

# virsh define <(virsh dumpxml [Domain] |
  sed "/vnc/s/\(\/>\)/keymap='pt-br'\1/"

Start it again:

# virsh start [Domain]

To get ',' (comma) key working on guest, the 'NumLock' key need to be pressed
three times.
Comment 1 Cole Robinson 2008-03-14 23:47:24 EDT
Hi, this has been upstream for a bit actually:

http://hg.et.redhat.com/virt/applications/virt-manager--devel?fd=4983533b800c;file=src/virtManager/keytable.py

It is in virt-manager 0.5.3, which is in F7 and F8. Closing this as CURRENTRELEASE.

Note You need to log in before you can comment on or make changes to this bug.