Bug 689562

Summary:	Copy-paste large text area from a client to a guest
Product:	Red Hat Enterprise Linux 6	Reporter:	Marian Krcmarik <mkrcmari>
Component:	spice-vdagent	Assignee:	Hans de Goede <hdegoede>
Status:	CLOSED DUPLICATE	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.1	CC:	dblechte
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-03-22 17:25:40 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Marian Krcmarik 2011-03-21 19:18:34 UTC

Description of problem:
Copying large text area (cca 200KB of plain text) through clipboard from Client to Guest doesn't work. Copying of the same amount of data from Guest to Client works fine. It's sometimes not able to display context menu after trying to paste the text to Guest application and sometimes even agents gets stuck (service running but agent doesn't work (losing mouse cursor for example).

Version-Release number of selected component (if applicable):
spice-server-0.7.3-2.el6.x86_64
spice-client-0.8.0-2.el6.x86_64
spice-vdagent-0.6.3-6.el6.x86_64


How reproducible:
Always (when using large enough text area).

Steps to Reproduce:
1. Open gedit in guest and client machine
2. Make large amount of text (200KB of plain text should be enough) in client gedit
3. Copy the text into clipboard in client
4. Paste the text into gedit in Guest
  
Actual results:
Nothing is copied and sometimes context menu cant be displayed or agent got stuck.

Expected results:
Text should be copied into gedit.

Additional info:.

Comment 2 Hans de Goede 2011-03-22 17:25:40 UTC

This is very likely caused by the lack of proper flow control on the agent channel in the client to guest direction, which is bug 672191, marking this one as a duplicate.

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