Red Hat Bugzilla – Bug 830760
Don't grab mouse cursor on client --> server mouse mode switch
Last modified: 2013-11-21 03:24:21 EST
Description of problem:
Don't grab mouse cursor on client --> server mouse mode switch. This is a minor annoyance but spice-client doesn't suffer with it.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. connect to linux guest
2. have the keyboard focus in the client
3. switch to the console (using ctrl-alt-Fx from Send Key menu)
mouse pointer gets grabbed
mouse pointer remains intact
this could go to ZStream (proposed) to avoid unnecessary "feel" changes in spicec -> remote-viewer transition.
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
That will have the side effect that any crash/stop of the vdagent will result in mouse being "released", even if the user is doing mouse grabbing. Not only grabbing, but mouse move as well.
I believe it's more important to keep the mouse continuously working even if vdagent is stopped or crash.
If the mouse is already in the context of the client, why shouldn't it be till there, even if switching to console? However, if the mouse is not over the display, I think it would make sense to not take the grab.
Agree with the above?
(this "minor annoyance" should not occur if the guest is configured with usb tablet)
*** Bug 920822 has been marked as a duplicate of this bug. ***
(In reply to comment #3)
> That will have the side effect that any crash/stop of the vdagent will
> result in mouse being "released", even if the user is doing mouse grabbing.
> Not only grabbing, but mouse move as well.
> I believe it's more important to keep the mouse continuously working even if
> vdagent is stopped or crash.
> If the mouse is already in the context of the client, why shouldn't it be
> till there, even if switching to console? However, if the mouse is not over
> the display, I think it would make sense to not take the grab.
> Agree with the above?
I think that the line should be drawn a bit further: the cursor should be kept inside only if some button is pressed, iow if user is performing drag'n'drop - but if that would be hard, then I'm in favor of releasing the mouse always.
The reasoning is:
1) the odds of agent crashing while user performs dnd - the only possibly destructive scenario - is quite low
2) when agent crashes while user works with mouse and the mouse is released, it's matter of one click on button that user already holds == almost non-event
3) the odds of user having mouse pointer on top of client while something ordinary happens that would grab the cursor are pretty high compared to 1) - just logout can o it (on linux and iirc on XP VMs)
4) the action to release the cursor suddently is quite annoying - having to interrupt what you are currently doing, take you hand off the mouse, press the key combo (RHEV's shift-f12 isn't exactly left-hand-friendly key combo), return the hand back to mouse, resume the action you did want to actually do
sent proposed patch to ML:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.