Bug 718001 - spicec --help needs explanation of how to use "--fullscreen=[auto-conf]" option
Summary: spicec --help needs explanation of how to use "--fullscreen=[auto-conf]" option
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: spice-gtk
Version: 6.2
Hardware: Unspecified
OS: All
unspecified
low
Target Milestone: rc
: ---
Assignee: Christophe Fergeau
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-30 15:58 UTC by Swapna Krishnan
Modified: 2013-02-21 08:47 UTC (History)
6 users (show)

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
Clone Of:
Environment:
Last Closed: 2013-02-21 08:47:01 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0343 0 normal SHIPPED_LIVE spice-gtk bug fix and enhancement update 2013-02-20 20:53:54 UTC

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


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