Bug 1560726 - VM unresponsive after host return from blank screen
Summary: VM unresponsive after host return from blank screen
Keywords:
Status: CLOSED DUPLICATE of bug 1485968
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: 27
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-26 20:44 UTC by Alessio
Modified: 2018-03-27 18:52 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-03-27 18:52:59 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Alessio 2018-03-26 20:44:37 UTC
virt-manager-1.4.3-2.fc27
Gnome Wayland session

A running VM is working.
The host system after the configured time "goes to blank screen".
Returning to activity the mouse and the keyboard works well, but the VM seems unresponsive, no mouse or keyboard action seems to have effects.

To solve the issue, I have to close the virt-manager, start it again, open the running VM and all back to works.

Comment 1 Cole Robinson 2018-03-26 21:45:03 UTC
Thanks for the report. It might be this: https://bugzilla.redhat.com/show_bug.cgi?id=1485968

Can you run virt-manager --debug from a terminal, and when you reproduce, see if the 'keyboard grab failed' message is in the terminal?

Comment 2 Alessio 2018-03-27 18:47:31 UTC
(In reply to Cole Robinson from comment #1)
> Thanks for the report. It might be this:
> https://bugzilla.redhat.com/show_bug.cgi?id=1485968
> 
> Can you run virt-manager --debug from a terminal, and when you reproduce,
> see if the 'keyboard grab failed' message is in the terminal?

Yeah. These are the lines appearing in the terminal

(virt-manager:3063): GSpice-CRITICAL **: cursor_handle_set: assertion 'c->init_done == TRUE' failed

(virt-manager:3063): GSpice-WARNING **: keyboard grab failed 1

Comment 3 Cole Robinson 2018-03-27 18:52:59 UTC
Thanks, duping to that bug

*** This bug has been marked as a duplicate of bug 1485968 ***


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