vncviewer and broken mouse behaviour - is there a fix?
Currently, using mouse with vncviewer is a bit broken: "VNC mouse pointer" moves much faster than the real mouse pointer.
As a result, it's not always easy to point&click in the right area.
Is there a workaround for that?
Signature · 2 lines
Tomasz Chmielewski http://wpkg.org
Quoted 6 lines · Tomasz Chmielewski
Currently, using mouse with vncviewer is a bit broken: "VNC mouse pointer" moves much faster than the real mouse pointer.
As a result, it's not always easy to point&click in the right area.
Is there a workaround for that?
-usbdevice tablet
Signature · 1 line
error compiling committee.c: too many arguments to function
Quoted 9 lines · Avi Kivity
Quoted 6 lines · Tomasz Chmielewski
Currently, using mouse with vncviewer is a bit broken: "VNC mouse pointer" moves much faster than the real mouse pointer.
As a result, it's not always easy to point&click in the right area.
Is there a workaround for that?
-usbdevice tablet
I already use it:
qm> info usb
Device 0.0, Speed 12 Mb/s, Product QEMU USB Tablet
I wonder why it doesn't work for me (with kvm-83)?
Do I have to configure something special on the quest?
On my guests, "vnc mouse pointer" moves much faster than the real one - both when X is started, but also in console, with gpm started.
Signature · 2 lines
Tomasz Chmielewski http://wpkg.org
use the vmmouse driver (instead of mouse) for X
Quoted 3 lines
Do I have to configure something special on the quest?
On my guests, "vnc mouse pointer" moves much faster than the real one - both when X is started, but also in console, with gpm started.
Quoted 1 line · Dietmar Maurer
use the vmmouse driver (instead of mouse) for X
Assuming it'll work, what about console? Well, I guess I could live with it.
But what about Windows guests? I've heard unconfirmed rumours that Windows doesn't run X (and have no console mode, either).
Quoted 3 lines
Quoted 3 lines
Do I have to configure something special on the quest?
On my guests, "vnc mouse pointer" moves much faster than the real one - both when X is started, but also in console, with gpm started.
Signature · 2 lines
Tomasz Chmielewski http://wpkg.org
Quoted 9 lines
Quoted 1 line · Dietmar Maurer
use the vmmouse driver (instead of mouse) for X
Assuming it'll work, what about console? Well, I guess I could live with it.
But what about Windows guests? I've heard unconfirmed rumours that Windows doesn't run X (and have no console mode, either).
Windows guests use the usb tablet driver.
- Dietmar
Quoted 12 lines · Tomasz Chmielewski
Quoted 10 lines · Avi Kivity
Quoted 7 lines · Tomasz Chmielewski
Currently, using mouse with vncviewer is a bit broken: "VNC mouse pointer" moves much faster than the real mouse pointer.
As a result, it's not always easy to point&click in the right area.
Is there a workaround for that?
-usbdevice tablet
Quoted 8 lines
I already use it:
qm> info usb
Device 0.0, Speed 12 Mb/s, Product QEMU USB TabletI wonder why it doesn't work for me (with kvm-83)?
Do I have to configure something special on the quest?
Yes, you need to make sure Xorg has activated the USB tablet, and is using it in absolute coordinate mode. If Xorg is using the shared stream /dev/input/mice, or not configured absolute mode, then the mouse pointer will still not track 1-for-1.
In current state of the art Xorg, this should all happen automatically if hal has labelled the USB tablet with 'input.x11_driver = evdev'. The FDI rules for HAL are only just added though, so your distro is probably missing them. See this bug for example of FDI rule you need to make Xorg auto-configure correctly
https://bugzilla.redhat.com/show_bug.cgi?id=487025
Regards,
Daniel
Signature · 4 lines
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
Quoted 6 lines · Tomasz Chmielewski
Currently, using mouse with vncviewer is a bit broken: "VNC mouse pointer" moves much faster than the real mouse pointer.
As a result, it's not always easy to point&click in the right area.
Is there a workaround for that?
I'm not sure if this is the bug you're referring to or not, but this might have just been fixed in gtk-vnc.
http://mail.gnome.org/archives/gtk-vnc-list/2009-February/msg00003.html