Hi,

I spent time looking at this some more. It seems that X was not
configured correctly.
You can not rely on auto detection, you must add an explicit section
for the vmware mouse, which means having sections for everything else.
Below is an example minimal config.

With vmmouse loaded (although vmmouse claims it needs no option, it
does in fact need the minimal options of 'mouse', ie Option "device"
"....") then the mouse is free to leave the vmware window.

With 'mouse', which is what X would auto load, the mouse is stuck.

However once I got vmmouse running it seems I fell over another bug.
The pointer on screen and where X thinks the pointer is do not line
up. Some searching and this seems to be a problem other distributions
have seen with the current:

xserver-xorg-input-vmmouse

There is a work around mentioned here
http://communities.vmware.com/docs/DOC-7870, however it does not work
for me.

So my choice seems to be either use 'mouse' and have a trapped mouse
(very annoying), or use 'vmmouse' and only be able to click on things
in the bottom right corner of the guest desktop.

I would suggest you provide helpers for configuring X, other then that
you should probably close this bug report, or assign it to
xserver-xorg-input-vmmouse

Regards

Thorben


Section "InputDevice"
        Identifier      "Generic Keyboard"
        Driver          "kbd"
      ..........
EndSection

Section "InputDevice"
        Identifier      "VMware Mouse"
        Driver          "vmmouse"
        Option  "Device"        "/dev/input/mice"
EndSection

Section "Device"
        Identifier      "VMware Video Device"
        Driver          "vmware"
EndSection

Section "Monitor"
        Identifier      "VMware Monitor"
        VendorName      "VMware, inc"
        HorizSync       1-10000
        VertRefresh     1-10000
EndSection

Section "Screen"
        Identifier      "Default Screen"
        Device          "VMware Video Device"
        Monitor         "VMware Monitor"
        DefaultDepth    24

#Modes only needed for login screen, ie before vmware-user is running
        SubSection      "Display"
                Depth           4
                ViewPort        0 0
                Modes   "1280x800" "1024x640" "800x500"
        EndSubSection
        SubSection      "Display"
                Depth           8
                ViewPort        0 0
                Modes   "1280x800" "1024x640" "800x500"
        EndSubSection
        SubSection      "Display"
                Depth           15
                ViewPort        0 0
                Modes   "1280x800" "1024x640" "800x500"
        EndSubSection
        SubSection      "Display"
                Depth           16
                ViewPort        0 0
                Modes   "1280x800" "1024x640" "800x500"
        EndSubSection
        SubSection      "Display"
                Depth           24
                ViewPort        0 0
                Modes   "1280x800" "1024x640" "800x500"
        EndSubSection
EndSection

Section "ServerLayout"
        Identifier      "Default Layout"
        Screen          "Default Screen"
        InputDevice     "Generic Keyboard" "CoreKeyboard"
        InputDevice     "VMware Mouse" "CorePointer"
EndSection



2008/10/8 TJ <[EMAIL PROTECTED]>:
> Hi,
>
> Thank you for looking at this and replying.
>
> That maintainer looks dead (metaphorically) to me. What it take to
> have someone else make a new package, especially since the package
> diff still applies cleanly. (somethings in debian/ still need
> updating/fixing though)
>
> While the lack of liburiparser 0.7.0 explains why unity mode is
> missing, it does not explain the original mouse issue, which I know
> should work without unity mode support. It is only recently that I
> packaged and installed the new liburiparser, however before that I
> just had unity mode disabled at build time, this did not break
> vmware-user's ability to have your mouse move freely in and out of the
> vmware window/desktop.
>
> Maybe it was miss leading for me to mention unity, but I thought it
> better to try and be as complete as possible. Please don't postpone
> looking into this until after you fix unity mode. (although unity mode
> negate the need for an untrapped mouse)
>
> I will try to see if the mouse being trapped is an upstream issue if I
> have the chance. I note that X is unloading vmmouse and failing back
> to mouse at startup. I don't know if this affects vmware-user's
> ability to sync the mouse without trapping it.
>
> Regards
>
> Thorben
>
> 2008/10/8 Daniel Baumann <[EMAIL PROTECTED]>:
>> severity 501536 normal
>> thanks
>>
>> Thorben Jändling wrote:
>>> Also unity mode is not always available, and when it is, it does not 
>>> function correctly. Guest windows receive keyboard events but not any mouse 
>>> input. They can't even be dragged/moved/resized.
>>
>> blocked by #493073 and #494680.
>>
>> --
>> Address:        Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
>> Email:          [EMAIL PROTECTED]
>> Internet:       http://people.panthera-systems.net/~daniel-baumann/
>>
>

Reply via email to