Your message dated Fri, 29 May 2009 15:12:37 +0200
with message-id <[email protected]>
and subject line Re: Bug#528742: any comments?
has caused the Debian Bug report #528742,
regarding Add FDI rule for QEMU USB tablet
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
528742: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528742
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: hal
Version: 0.5.12~git20090406.46dc48-2
Severity: wishlist
Hi,
the default mouse for KVM/QEMU guests is a PS/2 mouse however the
usbtablet is much nicer, working in absolute coordinate mode without the
need to grab the mouse [1].
However X11 autoconfiguration of the tablet doesn't work since the FDI
policy doesn't look for it. Attached file dumped into
/usr/share/hal/fdi/policy/10osvendor/10-x11-input.fdi fixes this.
Can this be applied? Once this is done I'll enable the usb tablet per
default for Squeeze KVM/QEMU guests in virtinst which should make using
KVM/QEMU guests with virt-manager much nicer.
Cheers,
-- Guido
https://bugzilla.redhat.com/show_bug.cgi?id=487025
<?xml version="1.0" encoding="UTF-8"?>
<deviceinfo version="0.2">
<device>
<match key="input.product" contains="QEMU USB Tablet">
<merge key="input.x11_driver" type="string">evdev</merge>
</match>
</device>
</deviceinfo>
--- End Message ---
--- Begin Message ---
reassign 528742 xserver-xorg-input-evdev
thanks
On Wed, May 27, 2009 at 06:49:40PM +0200, Julien Cristau wrote:
> On Wed, May 27, 2009 at 18:37:55 +0200, Guido Günther wrote:
[..snip..]
> > > Why does this device need to be handled specially, instead of falling
> > > under the generic info.capabilities test?
> > You mean the general check provided with the evdev package? It's an
> > emulated USB tablet so I'm not sure it's supposed to set input.keys. Is
> > it?
>
> Yes, I mean the general check provided with the evdev package (or a
> check for input.tablet if that's more appropriate). I don't think
> there's a point in adding specific rules for particular device names
> here.
It turns out that it *has* input.mouse in it's capabilities already so
everything is already working as expected (input.x11_driver is set to
mouse). Not sure why this failed when I tested it earlier, closing the
report.
-- Guido
--- End Message ---
