With a git X server from 20071127, the vmmouse module loads fine but the pointer doesn't seem to respond at all. This is with qemu's vmmouse emulation, but nothing has changed there and going back to an earlier X server (1.3) with the same qemu has things work fine.
(In reply to comment #0) > With a git X server from 20071127, the vmmouse module loads fine but the > pointer doesn't seem to respond at all. This is with qemu's vmmouse emulation, > but nothing has changed there and going back to an earlier X server (1.3) with > the same qemu has things work fine. do you have a debug server installed? I had a look at VMMouseDoPostEvent and it seems to call the API correctly. can you step through and determine whether the problem is in the driver or the server?
Aha, I see what it is. With the new xinput ABI, conversion_proc is never being called. See xserver commit 60ea7b51fe2b8a19a08b63db48504971a7a50ee6 and then there's also a thread from Debian with a hacky patch at http://groups.google.com/group/linux.debian.maint.x/browse_thread/thread/9c2ecc22fba0f03a
Until #10324 is fixed, this patch is a good solution.
Yeah, I've gone ahead and added it to the Fedora package for now, but getting the patch from 10324 or similar would definitely make things nicer (and allow for other nice things).
is this a dupe of bug 12506? https://bugs.freedesktop.org/show_bug.cgi?id=12506
Peter, see bug #10324, there's a patch now.
*** Bug 12506 has been marked as a duplicate of this bug. ***
(In reply to comment #0) > With a git X server from 20071127, the vmmouse module loads fine but the > pointer doesn't seem to respond at all. This is with qemu's vmmouse emulation, > but nothing has changed there and going back to an earlier X server (1.3) with > the same qemu has things work fine. > magnus has merged his patches into master. Could you please verify whether the problem persists?
Seems to work fine with current xserver Git in VMware Workstation.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.