Bug 1113454

Summary: virt-viewer stops accepting input after copy-paste accident in virtual machine
Product: [Fedora] Fedora Reporter: David Tonhofer <bughunt>
Component: virt-viewerAssignee: Daniel Berrangé <berrange>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: berrange, cfergeau, crobinso, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-05-31 18:32:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description David Tonhofer 2014-06-26 08:31:55 UTC
Description of problem:
-----------------------

Windows 7 runs as KVM virtual machine, with a virt-viewer session open.

The spice-vdagentd is running and the spice client tools have been installed on the Windos 7 system.

It often happens that I do "complex" copy pastes, e.g. from Microsoft Outlook into Confluence Wiki open in a Firefox (all in the VM).

Sometimes the Confluence Javascript cannot properly handle the incoming data and may take a long time to work or it gets confused.

It regularly happens that at that point the virt-viewer session decides to no longer pump input to the VM: keyboard and mouse do nothing anymore.

This is solved by closing the virt-viewer and reopening a new one, at which point work with Windows can resume (i.e. the VM was happily working all the time).

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

virt-viewer-0.6.0-1.fc20.x86_64

How reproducible:
-----------------

Very reproducible but difficult to find a way to do it.

Comment 1 Christophe Fergeau 2014-06-26 08:43:44 UTC
Is this reproducible with this scratch build ? 
http://koji.fedoraproject.org/koji/taskinfo?taskID=6923408

Comment 2 David Tonhofer 2014-06-26 17:05:00 UTC
Hi Christophe,

Probably not, because I don't have that in the first place:

$ rpm --query spice-gtk
package spice-gtk is not installed

Comment 3 Christophe Fergeau 2014-06-27 06:47:42 UTC
you must have 'spice-gtk3' installed as this is a dependency of virt-viewer:
$ rpm -q --requires virt-viewer |grep spice
libspice-client-gtk-3.0.so.4()(64bit)
libspice-client-gtk-3.0.so.4(SPICEGTK_1)(64bit)
[...]


$ rpm -q --provides spice-gtk3
spice-gtk3 = 0.23-2.fc20
spice-gtk3(x86-64) = 0.23-2.fc20
libspice-client-gtk-3.0.so.4()(64bit)
libspice-client-gtk-3.0.so.4(SPICEGTK_1)(64bit)

Comment 4 David Tonhofer 2014-06-27 08:33:29 UTC
Ah, sorry. Yes, indeed:

# rpm --query spice-gtk3

spice-gtk3-0.23-2.fc20.x86_64

....But the build is for "spice-gtk", which is not the same as "spice-gtk3"?

Comment 5 Christophe Fergeau 2014-06-27 08:43:11 UTC
spice-gtk is the name of the source package, spice-gtk3 is a subpackage built out of this source package, see http://koji.fedoraproject.org/koji/taskinfo?taskID=6923410 for the x86_64 build

Comment 6 David Tonhofer 2014-06-27 09:06:41 UTC
Ok, thanks. I will try this.

Comment 7 David Tonhofer 2014-06-30 07:53:08 UTC
Hi Christophe,

I wanted to download the built RPMs but tt seems the RPMs are not accessible?

"You don't have permission to access /work/tasks/3410/6923410/spice-gtk3-devel-0.25-1.fc20.1.x86_64.rpm on this server."

Comment 8 Christophe Fergeau 2014-08-06 09:36:05 UTC
The builds seem to be gone now, try http://koji.fedoraproject.org/koji/taskinfo?taskID=7247122

Comment 9 Christophe Fergeau 2014-08-06 10:05:22 UTC
Successful build is actually http://koji.fedoraproject.org/koji/taskinfo?taskID=7247180

Comment 10 Fedora End Of Life 2015-05-29 12:13:39 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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.