Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#12405 - No seamless mode in VMPlayer anymore
Attached to Project:
Community Packages
Opened by Filipp Andjelo (scorp) - Wednesday, 10 December 2008, 17:11 GMT
Last edited by Roman Kyrylych (Romashka) - Sunday, 11 January 2009, 09:46 GMT
Opened by Filipp Andjelo (scorp) - Wednesday, 10 December 2008, 17:11 GMT
Last edited by Roman Kyrylych (Romashka) - Sunday, 11 January 2009, 09:46 GMT
|
DetailsDescription:
After last updating of X.Org to version 1.5.3-3 and xf86-input-vmmouse to version 12.6.2-1, seamless mode doesn't work anymore. The mousecursor is captured by the VMPlayer and can be released only by CTRL + ALT. It's pretty annoying on working with two monitors with host system on the one and client on the other. From time to time Host system captures the mouse by itself => frustraiting moments, if you are writing something. Previous versions were fine. Additional info: * package version(s) - xf86-input-vmmouse 12.6.2-1 - xorg-server 1.5.3-3 Steps to reproduce: 1) Install ArchLinux in VMPlayer 2) Update packets to the versions above 3) Install open-vm-tools 4) Start X 5) run vmware-user in background 6) try to move the mouse between host an client systems |
This task depends upon
Closed by Roman Kyrylych (Romashka)
Sunday, 11 January 2009, 09:46 GMT
Reason for closing: Not a bug
Additional comments about closing: not a bug anymore
Sunday, 11 January 2009, 09:46 GMT
Reason for closing: Not a bug
Additional comments about closing: not a bug anymore
Comment by Glenn Matthys (RedShift) -
Sunday, 28 December 2008, 07:26 GMT
- Field changed: Severity (Critical → Medium)
Unless you are losing data or you have an unusable system, this bug is not critical.