Bug 718001

Summary:	spicec --help needs explanation of how to use "--fullscreen=[auto-conf]" option
Product:	Red Hat Enterprise Linux 6	Reporter:	Swapna Krishnan <skrishna>
Component:	spice-gtk	Assignee:	Christophe Fergeau <cfergeau>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.2	CC:	acathrow, cfergeau, dblechte, dyasny, mkenneth, mkrcmari
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Probably no doc needed, this only adds a bit more documentation to remote-viewer --help output	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-21 08:47:01 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Swapna Krishnan 2011-06-30 15:58:55 UTC

Description of problem:

While -f|--full-screen is explained in spicec/spicec.exe --help, there is not explanation of how to use the guest resolution change feature where on fullscreen, you can have the guest's resolution match the client's resolution. 

Add something like (uri's suggestion)

"  [ and change guest resolution to fit client (requires spice agent running on guest) "


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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 3 David Blechter 2012-04-18 14:21:28 UTC

moving to 6.4. Unfortunately, it is too late.

Comment 5 Marian Krcmarik 2012-08-01 13:42:28 UTC

Moving to spice-gtk since spice-client is being dropped and This can be reproducible with virt-viewer as well.

Comment 6 Christophe Fergeau 2012-09-07 13:44:18 UTC

Fixed upstream in http://git.fedorahosted.org/cgit/virt-viewer.git/commit/?id=c5d4570c11bc185d23575f39945e15f047250b37

Comment 10 errata-xmlrpc 2013-02-21 08:47:01 UTC

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.

http://rhn.redhat.com/errata/RHBA-2013-0343.html