open-vm-tools-devel

[open-vm-tools-devel] Mouse Capture

[Adam T. <moz...@gm...>]

I have been experimenting with VMware Workstation 6, and VMware Server 1.0.4,
and I have noticed a couple of issues with Mouse Capture.

It seems that, with IceWM, VMware's ability to "grab" and "un-grab" windows
is non-existent.

On these same virtual machines, (running openSuSE and Gentoo) both KDE and
Xfce are able to perform these functions.

I was wondering what the requirements were for a Window Manager to make use
of these functions, and why IceWM (possibly others) don't work as expected.

Thanks for your time,

Adam Tygart

Re: [open-vm-tools-devel] Mouse Capture

[Adar D. <ad...@vm...>]

> I have been experimenting with VMware Workstation 6, and=20
> VMware Server 1.0.4, and I have noticed a couple of issues=20
> with Mouse Capture.
>=20
> It seems that, with IceWM, VMware's ability to "grab" and=20
> "un-grab" windows is non-existent.=20

Just to clarify, you aren't even able to click the mouse and have the =
guest
grab the input? Or are you referring to automatic grab/ungrab, where =
moving
the mouse in and out of the guest will automatically redirect input to =
it (or
to the host)?

> On these same virtual machines, (running openSuSE and Gentoo)=20
> both KDE and Xfce are able to perform these functions.

Presumably you tested with KDE/IceWM/Xfce in the _host_, not in the =
guest,
right? That's how I interpreted your e-mail; I just want to be sure.

> I was wondering what the requirements were for a Window=20
> Manager to make use of these functions, and why IceWM=20
> (possibly others) don't work as expected.=20

I don't know the requirements myself, but I'll try and find someone who =
can
elaborate.

Re: [open-vm-tools-devel] Mouse Capture

[Adam T. <moz...@gm...>]

> Just to clarify, you aren't even able to click the mouse and have the
guest
> grab the input? Or are you referring to automatic grab/ungrab, where
moving
> the mouse in and out of the guest will automatically redirect input to it
(or
> to the host)?

I was able to click the vm and have it grab input, however I was wanting the
ability to automatically redirect the input.

> Presumably you tested with KDE/IceWM/Xfce in the _host_, not in the guest,
> right? That's how I interpreted your e-mail; I just want to be sure.

I was testing with KDE/IceWM on the host, and KDE/IceWM/Xfce on the guest.
It seems as if only the guest's Window Manager made a difference as to the
ability to redirect the input.
Now, that being said I did find that if you use the vmmouse module in
xorg.conf that it removed any/all issues that I was seeing. Now I am just
curious as to why some Window Managers need the module (IceWM) while others
do not (KDE/Xfce).

> I don't know the requirements myself, but I'll try and find someone who
can
> elaborate.

Thanks for your interest so far,

Adam Tygart

Re: [open-vm-tools-devel] Mouse Capture

[Adar D. <ad...@vm...>]

> > Just to clarify, you aren't even able to click the mouse=20
> and have the guest
> > grab the input? Or are you referring to automatic=20
> grab/ungrab, where moving
> > the mouse in and out of the guest will automatically=20
> redirect input to it (or=20
> > to the host)?
>=20
> I was able to click the vm and have it grab input, however I=20
> was wanting the ability to automatically redirect the input.
>=20
> > Presumably you tested with KDE/IceWM/Xfce in the _host_,=20
> not in the guest,=20
> > right? That's how I interpreted your e-mail; I just want to be sure.
>=20
> I was testing with KDE/IceWM on the host, and KDE/IceWM/Xfce=20
> on the guest. It seems as if only the guest's Window Manager=20
> made a difference as to the ability to redirect the input.=20
> Now, that being said I did find that if you use the vmmouse=20
> module in xorg.conf that it removed any/all issues that I was=20
> seeing. Now I am just curious as to why some Window Managers=20
> need the module (IceWM) while others do not (KDE/Xfce).=20

It sounds like you're talking about the "auto grab/ungrab" feature, but =
I'm
not entirely sure because I don't know what you mean by "automatically
redirect the input" above.

If that's what we're talking about, know that vmmouse isn't the only =
provider
of this feature; the vmware-user process is another. My guess is that =
you've
been running vmware-user in the background and that the auto grab/ungrab
provided by vmware-user on IceWM doesn't work for some reason. Can you
confirm or deny this?

Re: [open-vm-tools-devel] Mouse Capture

[Adam T. <moz...@gm...>]

That is what I am seeing. the auto grab/ungrab feature doesn't work in IceWM
without vmmouse, yet it works in KDE/Xfce without vmmouse... The
vmware-guestd process is running in both instances... and vmware-user is
running in the instance of KDE for sure, I will have to check tomorrow
morning as to whether or not it is running for the others.

On 10/25/07, Adar Dembo <ad...@vm...> wrote:
>
> > > Just to clarify, you aren't even able to click the mouse
> > and have the guest
> > > grab the input? Or are you referring to automatic
> > grab/ungrab, where moving
> > > the mouse in and out of the guest will automatically
> > redirect input to it (or
> > > to the host)?
> >
> > I was able to click the vm and have it grab input, however I
> > was wanting the ability to automatically redirect the input.
> >
> > > Presumably you tested with KDE/IceWM/Xfce in the _host_,
> > not in the guest,
> > > right? That's how I interpreted your e-mail; I just want to be sure.
> >
> > I was testing with KDE/IceWM on the host, and KDE/IceWM/Xfce
> > on the guest. It seems as if only the guest's Window Manager
> > made a difference as to the ability to redirect the input.
> > Now, that being said I did find that if you use the vmmouse
> > module in xorg.conf that it removed any/all issues that I was
> > seeing. Now I am just curious as to why some Window Managers
> > need the module (IceWM) while others do not (KDE/Xfce).
>
> It sounds like you're talking about the "auto grab/ungrab" feature, but
> I'm
> not entirely sure because I don't know what you mean by "automatically
> redirect the input" above.
>
> If that's what we're talking about, know that vmmouse isn't the only
> provider
> of this feature; the vmware-user process is another. My guess is that
> you've
> been running vmware-user in the background and that the auto grab/ungrab
> provided by vmware-user on IceWM doesn't work for some reason. Can you
> confirm or deny this?
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> open-vm-tools-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/open-vm-tools-devel
>

Re: [open-vm-tools-devel] Mouse Capture

[Adar D. <ad...@vm...>]

> That is what I am seeing. the auto grab/ungrab feature=20
> doesn't work in IceWM without vmmouse, yet it works in=20
> KDE/Xfce without vmmouse... The vmware-guestd process is=20
> running in both instances... and vmware-user is running in=20
> the instance of KDE for sure, I will have to check tomorrow=20
> morning as to whether or not it is running for the others.=20

Sorry you were left in the lurch, but a fellow engineer stumbled across =
this
exchange yesterday and mentioned that vmware-guestd isn't autostarting
vmware-user for you because it's likely that the "blessed apps" it looks =
for
(gnome-panel, ksmserver, startkde, kwrapper, panel, and xfce4-panel) =
don't
run during an IceWM session. You can manually start vmware-user within =
the
session, though vmware-guestd may stupidly kill vmware-user because it =
thinks
that the running X session was killed (again, due to the lack of =
"blessed
apps").

We should just kill that autostart code and follow the xdg autostart =
spec,
but no one has gotten around to it yet. Plus retaining some sort of =
autostart
behavior on older versions of Xorg/XFree86 may be tricky.

Re: [open-vm-tools-devel] Mouse Capture

[Adam T. <moz...@gm...>]

Don't worry about just leaving off like that, I ended up using the vmmouse
driver, and that seems to have solved my issue (well, it was at least a
workaround).

On Jan 8, 2008 8:22 PM, Adar Dembo <ad...@vm...> wrote:

> > That is what I am seeing. the auto grab/ungrab feature
> > doesn't work in IceWM without vmmouse, yet it works in
> > KDE/Xfce without vmmouse... The vmware-guestd process is
> > running in both instances... and vmware-user is running in
> > the instance of KDE for sure, I will have to check tomorrow
> > morning as to whether or not it is running for the others.
>
> Sorry you were left in the lurch, but a fellow engineer stumbled across
> this
> exchange yesterday and mentioned that vmware-guestd isn't autostarting
> vmware-user for you because it's likely that the "blessed apps" it looks
> for
> (gnome-panel, ksmserver, startkde, kwrapper, panel, and xfce4-panel) don't
> run during an IceWM session. You can manually start vmware-user within the
> session, though vmware-guestd may stupidly kill vmware-user because it
> thinks
> that the running X session was killed (again, due to the lack of "blessed
> apps").
>
> We should just kill that autostart code and follow the xdg autostart spec,
> but no one has gotten around to it yet. Plus retaining some sort of
> autostart
> behavior on older versions of Xorg/XFree86 may be tricky.
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
>
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> open-vm-tools-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/open-vm-tools-devel
>

Re: [open-vm-tools-devel] Mouse Capture

[Adar D. <ad...@vm...>]

Yeah, I think vmmouse is probably the preferred method of getting
auto-grab/ungrab.

But, without vmware-user, you won't be able to use drag n' drop or file
copy/paste. Nor will you be able to resize the VM's window and have the
guest's resolution automatically change to fit the new window size. Not =
sure
how important those features are to you.

In the near term, perhaps there's a blessed app for IceWM that we ought =
to be
tracking as part of xautostart.conf?

> Don't worry about just leaving off like that, I ended up=20
> using the vmmouse driver, and that seems to have solved my=20
> issue (well, it was at least a workaround).
>=20
>=20
> On Jan 8, 2008 8:22 PM, Adar Dembo < ad...@vm...> wrote:
>=20
>=20
> 	> That is what I am seeing. the auto grab/ungrab feature=20
> 	> doesn't work in IceWM without vmmouse, yet it works in
> 	> KDE/Xfce without vmmouse... The vmware-guestd process is
> 	> running in both instances... and vmware-user is running in
> 	> the instance of KDE for sure, I will have to check tomorrow=20
> 	> morning as to whether or not it is running for the others.
> =09
> =09
> 	Sorry you were left in the lurch, but a fellow engineer=20
> stumbled across this
> 	exchange yesterday and mentioned that vmware-guestd=20
> isn't autostarting=20
> 	vmware-user for you because it's likely that the=20
> "blessed apps" it looks for
> 	(gnome-panel, ksmserver, startkde, kwrapper, panel, and=20
> xfce4-panel) don't
> 	run during an IceWM session. You can manually start=20
> vmware-user within the=20
> 	session, though vmware-guestd may stupidly kill=20
> vmware-user because it thinks
> 	that the running X session was killed (again, due to=20
> the lack of "blessed
> 	apps").
> =09
> 	We should just kill that autostart code and follow the=20
> xdg autostart spec,=20
> 	but no one has gotten around to it yet. Plus retaining=20
> some sort of autostart
> 	behavior on older versions of Xorg/XFree86 may be tricky.
> =09
> =09
> --------------------------------------------------------------
> -----------=20
> 	Check out the new SourceForge.net Marketplace.
> 	It's the best place to buy or sell services for
> 	just about anything Open Source.
> =09
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.n
> et/marketplace=20
> <http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.
> net/marketplace>=20
> =09
> 	_______________________________________________
> 	open-vm-tools-devel mailing list
> 	ope...@li...=20
> <mailto:ope...@li...>=20
> 	https://lists.sourceforge.net/lists/listinfo/open-vm-tools-devel
> =09
>=20
>=20
>=20

Re: [open-vm-tools-devel] Mouse Capture

[Adam T. <moz...@gm...>]

I am not sure, unfortunately, that box has been out of my care for almost a
month and a half. My boss currently uses it as his primary workstation.

On Jan 8, 2008 8:51 PM, Adar Dembo <ad...@vm...> wrote:

> Yeah, I think vmmouse is probably the preferred method of getting
> auto-grab/ungrab.
>
> But, without vmware-user, you won't be able to use drag n' drop or file
> copy/paste. Nor will you be able to resize the VM's window and have the
> guest's resolution automatically change to fit the new window size. Not
> sure
> how important those features are to you.
>
> In the near term, perhaps there's a blessed app for IceWM that we ought to
> be
> tracking as part of xautostart.conf?
>
> > Don't worry about just leaving off like that, I ended up
> > using the vmmouse driver, and that seems to have solved my
> > issue (well, it was at least a workaround).
> >
> >
> > On Jan 8, 2008 8:22 PM, Adar Dembo < ad...@vm...> wrote:
> >
> >
> >       > That is what I am seeing. the auto grab/ungrab feature
> >       > doesn't work in IceWM without vmmouse, yet it works in
> >       > KDE/Xfce without vmmouse... The vmware-guestd process is
> >       > running in both instances... and vmware-user is running in
> >       > the instance of KDE for sure, I will have to check tomorrow
> >       > morning as to whether or not it is running for the others.
> >
> >
> >       Sorry you were left in the lurch, but a fellow engineer
> > stumbled across this
> >       exchange yesterday and mentioned that vmware-guestd
> > isn't autostarting
> >       vmware-user for you because it's likely that the
> > "blessed apps" it looks for
> >       (gnome-panel, ksmserver, startkde, kwrapper, panel, and
> > xfce4-panel) don't
> >       run during an IceWM session. You can manually start
> > vmware-user within the
> >       session, though vmware-guestd may stupidly kill
> > vmware-user because it thinks
> >       that the running X session was killed (again, due to
> > the lack of "blessed
> >       apps").
> >
> >       We should just kill that autostart code and follow the
> > xdg autostart spec,
> >       but no one has gotten around to it yet. Plus retaining
> > some sort of autostart
> >       behavior on older versions of Xorg/XFree86 may be tricky.
> >
> >
> > --------------------------------------------------------------
> > -----------
> >       Check out the new SourceForge.net Marketplace.
> >       It's the best place to buy or sell services for
> >       just about anything Open Source.
> >
> > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.n
> > et/marketplace
> > <http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.
> > net/marketplace>
> >
> >       _______________________________________________
> >       open-vm-tools-devel mailing list
> >       ope...@li...
> > <mailto:ope...@li...>
> >       https://lists.sourceforge.net/lists/listinfo/open-vm-tools-devel
> >
> >
> >
> >
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
>
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> open-vm-tools-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/open-vm-tools-devel
>