Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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:
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.