Bug 1586141 - Can't see mouse in windows guest's console after releasing mouse from guest by shift+F12
Summary: Can't see mouse in windows guest's console after releasing mouse from guest b...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-viewer
Version: 28
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Daniel Berrangé
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-05 15:09 UTC by mxie@redhat.com
Modified: 2019-05-28 20:30 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-28 20:30:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screenshot (496.32 KB, image/png)
2018-06-05 15:09 UTC, mxie@redhat.com
no flags Details
remote-viewer-fedora28.log (384.14 KB, text/plain)
2018-06-05 15:10 UTC, mxie@redhat.com
no flags Details

Description mxie@redhat.com 2018-06-05 15:09:25 UTC
Created attachment 1447887 [details]
screenshot

Description of problem:
Can't see mouse in windows guest's console after releasing mouse from guest by remote viewer

Version-Release number of selected component (if applicable):
virt-viewer-6.0-3.fc28.x86_64
spice-gtk3-0.34-4.fc28.x86_64
rhv4.2.4-0.1.el7

How reproducible:
100%

Steps to Reproduce:
1.Log into rhv4.2 with admin account
2.Power on a windows guest and open its console using remote-viewer, or save console.vv to local and use remote-viewer to open
3.Mouse could be seen in guest, but mouse will be disappeared in console if release mouse from guest by inputting "shift+F12", so it is hard to close guest console by mouse, pls refer to screenshot (try to use mouse to click the X button,although the button is selected, the mouse can be seen)


Actual results:
As above description

Expected results:
Can see mouse in windows guest's console after releasing mouse from guest by remote viewer on fedora28


Additional info:
1.Can see mouse in linux guest's console no matter whether release mouse from guest by remote viewer on fedora28
2.Can see mouse in windows guest's console after releasing mouse from guest by remote viewer on both rhel6 and rhel7

Comment 1 mxie@redhat.com 2018-06-05 15:10:41 UTC
Created attachment 1447888 [details]
remote-viewer-fedora28.log

Comment 2 Ben Cotton 2019-05-02 21:39:12 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Ben Cotton 2019-05-28 20:30:10 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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