Bug 487560 - Broken handling of relative mouse grab mode
Broken handling of relative mouse grab mode
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: gtk-vnc (Show other bugs)
All Linux
high Severity high
: rc
: ---
Assigned To: Daniel Berrange
Martin Jenner
: 432232 (view as bug list)
Depends On:
Blocks: 223805
  Show dependency treegraph
Reported: 2009-02-26 13:11 EST by Daniel Berrange
Modified: 2009-09-02 05:48 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-09-02 05:48:41 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2009:1301 normal SHIPPED_LIVE gtk-vnc bug fix update 2009-09-01 06:05:55 EDT

  None (edit)
Description Daniel Berrange 2009-02-26 13:11:34 EST
Description of problem:
The current GTK-VNC code has a couple of problems with the way it handles relative mouse mode in VNC described here


These cause an 'invisible wall' problem as per bug 223805

This is fixed upstream here:


Version-Release number of selected component (if applicable):

How reproducible:
Difficult, but common

Steps to Reproduce:
1. Use a guest virtual machine for a while
Actual results:
At some point the mouse cursor will hit an invisible wall, preventing movement over some part of the guest console desktop

Expected results:

Additional info:
Comment 1 Daniel Berrange 2009-04-01 11:06:43 EDT
Fix built into gtk-vnc-0.3.8-1.el5
Comment 2 Daniel Berrange 2009-04-01 11:10:14 EDT
*** Bug 432232 has been marked as a duplicate of this bug. ***
Comment 7 errata-xmlrpc 2009-09-02 05:48:41 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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