In feisty on a vmware machine - when the xorg mouse driver is vmmouse - a single click is all too easily interpreted as a double click (unless the mouse button release is very slow after the press, which is unnatural).
this happens with both vmware 5.x and 6 beta, on different hosts (RHEL4 and feisty respectively).
if anyone has experienced it and can suggest workarounds I'll be happy to know.
PS - I have been using both linux and vmware for years. I have no probs with either usually!
i should add that since feisty uses XOrg 7.2 I need to manually take the drivers (for Xorg 7.x) from the vmware tools and copy over to my xorg install
I also tried using the distro's own xorg vmmouse driver (which I'd guess is aligned ith 7.2) but it makes no difference
Even more, the weird behavior is there also without vmtoos - just with the xorg stock vmware video and vmmouse input drivers
Message was edited by:
Edoardo
On my machine the problem disappeared when I followed the instructions in http://www.vmware.com/info?id=97
thanks for the info, but my host is a linux host and I can't find a config.ini
... and even through many updates, the ubuntu guest mouse is still erratic and a single click is often interpreted as a double click
Edoardo,
Did you ever find a solution to this issue? I experience the same problem...
-Josh
I also have this problem. The mouse is erratic, sometimes a single click does nothing. Disabling DHCP in Ubuntu helped with the pointer being erratic. (I don't have a DHCP server, my IPs must be static).
Sometimes I see two pointers at full screen. I do not have VMware tools installed, I am running the Feisty LiveCD in VMPlayer v2 on Windows Vista host.
just to clarify, i still have the mouse-click-sometimes-does-nothing type problem.
Message was edited by:
hithere
It is now July the 11th and this question remains unanswered. Will the VMWare staff please respond to this issue.
Thank you.
It is now July the 11th and this question remains
unanswered. Will the VMWare staff please respond to
this issue.
Thank you.
Know one is required to respond to any posting on the Community forums, this forum is staffed by volunteers and they respond in their free time.
If you need intermediate assistance with an issue, please file a service request with technical support.
Now what is your issue?
Please post complete details of your configuration
Thanks for your response.
What specific config information do you need and how Do I get it.
The host OS is Ubuntu Feisty 7.04 Running VMWare Workstation 6.00 and the guest is Feisty Server 7.04. The problem experienced is the one defined in the first post of this thread.
Post the /etc/X11/xorg.conf from your Ubuntu guest
\# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
\# This file was generated by dexconf, the Debian X Configuration tool, using
\# values from the debconf database.
#
\# Edit this file with caution, and see the xorg.conf(5) manual page.
\# (Type "man xorg.conf" at the shell prompt.)
#
\# This file is automatically updated on xserver-xorg package upgrades \*only*
\# if it has not been modified since the last upgrade of the xserver-xorg
\# package.
#
\# If you have edited this file but would like it to be automatically updated
\# again, run the following command:
\# sudo dpkg-reconfigure -phigh xserver-xorg
Section "Files"
FontPath "/usr/share/fonts/X11/misc"
FontPath "/usr/share/fonts/X11/cyrillic"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/usr/share/fonts/X11/75dpi"
path to defoma fonts
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection
Section "Module"
Load "i2c"
Load "bitmap"
Load "ddc"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "vbe"
EndSection
Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
Identifier "Configured Mouse"
Driver "vmmouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ps/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection
Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/input/wacom"
Option "Type" "stylus"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection
Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "Device" "/dev/input/wacom"
Option "Type" "eraser"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection
Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/input/wacom"
Option "Type" "cursor"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection
Section "Device"
Identifier "VMware SVGA"
Driver "vmware"
EndSection
Section "Screen"
Identifier "Default Screen"
Device "VMware SVGA"
Monitor "vmware"
Don't specify DefaultColorDepth unless you know what you're
doing. It will override the driver's preferences which can
cause the X server not to run if the host doesn't support the
depth.
Subsection "Display"
VGA mode: better left untouched
Depth 4
Modes "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 8
Modes "800x600"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 15
Modes "800x600"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "800x600"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "800x600"
ViewPort 0 0
EndSubsection
EndSection
Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
InputDevice "stylus" "SendCoreEvents"
InputDevice "cursor" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"
EndSection
Section "DRI"
Mode 0666
EndSection
Section "Monitor"
Identifier "vmware"
VendorName "VMware, Inc"
HorizSync 1-10000
VertRefresh 1-10000
EndSection
Any ideas yet?
Tried in
1) Ubuntu Gusty Guest.
2) VMWare appliance downloaded from Vmware market place (Feisty).
3) Fresh install of Feisty 7.04 Host (and guest on host)
The problem only occurs after installing the VMWare tools. With out the tools the single clicks are as they should be. But of course the mouse cannot cross the borders. And all installing vmware, the vmmouse is giving the problem.
Thanks.
Workarounds for this issue can be found in the following thread:
http://www.vmware.com/community/thread.jspa?messageID=716756