From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Description of problem:
This is a weird one.
Since installing vmware..
my mouse has not acted properly when first logging in to X.
When I click on icons and windows, I either get no response, or the
click is made somewhere else. For example, I right-click on the
desktop in the center, the menu appears to the side.
Ctrl+Alt+F1, Ctrl+Alt+F7 seems to help, as does right,left-clicking on
parts of the screen, as if I'm teaching the mouse where it is.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
I can reproduce this on two machines.
If evolution is added as a startup app, using gnome's "sessions", the
mouse does not work at all properly when I log in to X.
This sounds like evolution is grabbing the mouse, and not letting
go of it. I don't know if that's the case or not, but I can't think
of any other logical explanation for why the above symptoms would
Oddly, nobody else has reported this problem as far as I can see
Reassigning to evolution component.
I recommend getting an strace and ltrace of evolution running
when this problem occurs, and perhaps running it in a gdb session
to debug the issue.
"Since installing vmware.."
I missed that in the original comment. If this only happens
when using VMware (which is unsupported), you might also want
to report this to VMware Inc. and to X.Org bugzilla located
at http://bugs.freedesktop.org in the "xorg" component, in case
there is a problem with vmware's driver.
What state is Evolution in when it starts up? Does the main window
appear? Any other dialogs? Which component appears? The mail
component or another?
Is this when running on a simulated computer inside VMware, or running
as the real computer?
The host machine is Linux, at the point that I get the problem, I am
not running any virtual machines - but the vmware service has started
X starts as usual - evolution is set to start with X.
evolution starts as usual.
The problem is that the mouse requires a lot of work to get it to
Ok, to clarify, you are booting Linux outside of VMware, and running
evolution also outside of vmware, only the vmware system service
(and thus also the vmware unsupported kernel modules) are running.
If you disable the vmware service at boot, and ensure the vmware
kernel modules never load at all, does the problem go away?
I will try to test this tomorrow, but iirc it is only a problem when
evolution is started automatically from Sessions.
I can no longer reproduce this. Will reopen if it happens again.