Red Hat Bugzilla – Bug 1002697
Mouse pointer appears black on PuTTY terminals opened from windows 7 guests [mingw-virt-viewer]
Last modified: 2015-09-22 09:09 EDT
*Note:* Copied from Bug 998529 and opened against the Windows version of virt-viewer, called mingw-virt-viewer.
Description of problem:
On PuTTY sessions the mouse pointer appears black when opened from a windows 7 guest connected via spice.
the issue is described more deeply here:
and arises also when connecting via rdesktop (see http://osdir.com/ml/network.rdesktop.user/2005-03/msg00012.html) but it does not arise when connecting via MSTSC or via freeRDP.
The I-beam mouse pointer that PuTTY uses is not rendered the same in rdesktop as it is in the Windows Remote Desktop client. The workaround is to change the "Text Select" pointer on the Windows machine by going to Control Panel->Mouse->Pointers. I changed it to the beam_r.cur image, which is a beefier version of the I-beam bitmap which does render nicely in rdesktop.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. open putty terminal in in Win7 guest accessed cia spice
Cursor is black
Cursor is white
(the bug is in post assuming Alon fixes work on windows too, we are missing acks to get this in the msi build)
*** Bug 1017301 has been marked as a duplicate of this bug. ***
A fix is pushed upstream -- commit 11ddba4b09bc2e3024cfd1c9f0d78948d004bb40
This bug is currently attached to errata RHEA-2013:15512. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to
minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
Thanks in advance.
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.