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.
Bug 1674311 - [wayland] Mouse pointer visibly leaves spice-gtk widget in relative mouse mode
Summary: [wayland] Mouse pointer visibly leaves spice-gtk widget in relative mouse mode
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: spice-gtk
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.1
Assignee: Francesco Giudici
QA Contact: SPICE QE bug list
URL:
Whiteboard:
Depends On: 1682775
Blocks: 1806601
TreeView+ depends on / blocked
 
Reported: 2019-02-10 23:15 UTC by David Jaša
Modified: 2020-11-04 04:07 UTC (History)
7 users (show)

Fixed In Version: spice-gtk-0.38-2.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-04 04:07:05 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description David Jaša 2019-02-10 23:15:32 UTC
Description of problem:
Mouse pointer visibly leaves spice-gtk widget in relative mouse mode

Version-Release number of selected component (if applicable):
spice-gtk3-0.35-7.el8.x86_64

How reproducible:
always

Steps to Reproduce:
1. in a VM with disabled vmport (<features><vmport state='off'/>) or USB tablet and vdagent not active, move mouse pointer consistently in one direction
2.
3.

Actual results:
mouse pointer leaves the widget

Expected results:
mouse pointer, wherever it is, should never apparently leave spice-gtk widget

Additional info:
This is old bug dating to earliest versions of spice-gtk, but the oldie spicec never suffered from it

Comment 1 Victor Toso 2019-02-12 09:52:09 UTC
Does not happen when running with x11 backend, that is, GDK_BACKEND=x11 remote-viewer ..
We will address wayland backend issues upstream and target is 8.1

Comment 2 David Blechter 2019-08-16 14:26:39 UTC
Wayland related issues where not addressed yet, moving to the backlog

Comment 3 Francesco Giudici 2020-05-11 09:44:33 UTC
Issue is due to lack of official, stable support in Wayland for pointer locking in the widget.
Wayland-protocols come to the rescue.. patch merged upstream:
https://gitlab.freedesktop.org/spice/spice-gtk/-/commit/dd7015d57c

Comment 4 Victor Toso 2020-05-20 10:24:56 UTC
Ongoing build, I'm setting ITR to 8.3.0 to get the release+

Comment 14 errata-xmlrpc 2020-11-04 04:07:05 UTC
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 (spice-gtk bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:4817


Note You need to log in before you can comment on or make changes to this bug.