Bug 1300593

Summary:	xfreerdp with --no-motion option doesn't work correctly
Product:	Red Hat Enterprise Linux 6	Reporter:	Tomas Hudziec <thudziec>
Component:	freerdp	Assignee:	Ondrej Holy <oholy>
Status:	CLOSED NOTABUG	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.7	CC:	tpelka
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-01-21 12:36:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Tomas Hudziec 2016-01-21 09:15:21 UTC

Description of problem:
after running xfreerdp with --no-motion option, xfreerdp doesn't disable all mouse events sent to remote windows window as it should

Version-Release number of selected component (if applicable):
freerdp-1.0.2-3.el6.x86_64
freerdp-libs-1.0.2-3.el6.x86_64
freerdp-plugins-1.0.2-3.el6.x86_64

How reproducible:
always

Steps to Reproduce:
Try to connect to remote windows machine via xfreerdp with --no-motion option:
$ xfreerdp --no-motion $WindowsIP

Actual results:
Mouse buttons and wheel works, only hover effect of mouse is disabled.

Expected results:
No mouse events should be populated into the windows window. You should not be able to move cursor, click mouse etc.

Additional info:

Comment 2 Ondrej Holy 2016-01-21 12:36:03 UTC

Why do you think that it should disable all mouse events? We should correct this in documentation if it is mentioned somewhere. The --no-motion means that just motion events should be disabled...

Mouse button and wheel are not motion events. Hover is not disabled, you don't see hover effect, because motion events are not transmitted and thus the guest doesn't know, that the mouse is above the element...

You can see mouse above the xfreerdp window, but this is client mouse (though it looks different) and any motion events aren't transmitted, see Bug 1071871 for more details.