Description of problem:
There seems to be some kind of erratic and invisible mouse activity under VMware
with Fedora 8. If I have two or more windows open, and I'm using
focus-follows-mouse, I can sit back and not touch the mouse or keyboard and
watch the focus jump between windows every 10-15 seconds. This happens under
both KDE and Gnome.
Also, tool-tips occasionally appear on random windows/buttons/etc. Again, I did
not move the mouse and it's not hovering over these windows/buttons/etc.
The cursor itself does not move (if it does, it's faster than my eyes can see).
I'm using VMware Fusion on a Mac with OS X 10.5.0. This happens with both
VMware Fusion 1.0 and 1.1RC1. vmware-tools is installed and configured.
Fedora 7 focus-follows-mouse works just fine under VMware Fusion (both 1.0 and
Immediately upon logging in, the focus might be fine. After I start working for
a few minutes and opening & closing windows, something triggers this weird behavior.
Workaround is to move back to click-to-focus. :(
Version-Release number of selected component (if applicable):
Fedora 8 (broken)
Fedora 7 (works)
Steps to Reproduce:
1. Install Fedora 8 i386 under VMware Fusion (1.0 or 1.1RC1) and install VMware
Tools and configure them.
2. Login to KDE or Gnome and configure it for focus-follows-mouse
3. Open up two or more windows
4. Place mouse over a window
5. Remove hands from keyboard & mouse
6. Watch as focus jumps to another window
Focus jumps to random windows, cursor remains stationary
Tool-tips may appear over random windows or buttons occasionally
Focus stays with cursor
This may happen under other VMware products, too, e.g., VMware Workstation on
Windows, but I don't have access to other products to test this.
Fedora 7 works fine.
I just discovered another neat trick
1. open a window with a vertical scroll bar, e.g., a browser viewing this BZ
2. left-click and hold the scroll bar, but do not move the mouse
3. keep holding for 10-15 seconds and eventually it will jump to the very
bottom of the page all on its own!
I think I found the solution to this. Actually, the Ubuntu community found the
Basically, the new X server reports its version as 1.3.0 instead of 7.3.0
(why?), and vmware-config-tools.pl gets really confused by this. Editing the
script to accept the new version number fixes the problem.