The kernel 4.1 update broke the mouse functionality in VMWare VMs. This was fixed upstream in x11-driver-input-vmmouse 13.1.0: http://lists.x.org/archives/xorg-announce/2015-June/002616.html Updated package uploaded for Mageia 5. Advisory: ---------------------------------------- The x11-driver-input-vmmouse package has been updated to version 13.1.0, enabling the mouse to function again in VMWare virtual machines. References: http://lists.x.org/archives/xorg-announce/2015-June/002616.html ---------------------------------------- Updated packages in core/updates_testing: ---------------------------------------- x11-driver-input-vmmouse-13.1.0-1.mga5 from x11-driver-input-vmmouse-13.1.0-1.mga5.src.rpm Reproducible: Steps to Reproduce:
I've confirmed the update fixes the issue on Mageia 5 i586.
Whiteboard: (none) => has_procedure MGA5-32-OK
Note to Thierry, if you read: http://lists.x.org/archives/xorg-announce/2015-June/002616.html It sounds like we can drop this package in Cauldron and change the installer and drakx11 to use something else (not sure what, evdev?) as the mouse driver and the kernel will handle things.
CC: (none) => thierry.vignaud
CC: (none) => davidwhodginsWhiteboard: has_procedure MGA5-32-OK => has_procedure MGA5-32-OK advisory
Confirmed that the update fixes the issue on Mageia 5 i586.
CC: (none) => ngompa13
Confirmed that the update fixes the issue on Mageia 5 x86_64.
Whiteboard: has_procedure MGA5-32-OK advisory => has_procedure MGA5-64-OK MGA5-32-OK advisory
Well done Neal. Validating. Please push to 5 updates Thanks
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
An update for this issue has been pushed to Mageia Updates repository. http://advisories.mageia.org/MGAA-2015-0154.html
Status: NEW => RESOLVEDResolution: (none) => FIXED
(In reply to David Walser from comment #2) > Note to Thierry, if you read: > http://lists.x.org/archives/xorg-announce/2015-June/002616.html > > It sounds like we can drop this package in Cauldron and change the installer > and drakx11 to use something else (not sure what, evdev?) as the mouse > driver and the kernel will handle things. Yep, I'm aware since 4.1RC[12]. I'd updated the vmware driver as soon as possible in cauldron for that. I didn't though about that when Thomas pushed 4.1 as an update though... Yes, now, I should drop the vmmouse driver from the installer.
Too bad they don't do the same for virtualbox though (less need for guest additions... at least there would be mouse integration by default). Now, vmware & libvirt are ahead of vbox for this...