RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 841262 - RHEL 7 spice-vdagent does not enter full-screen with monitor resolution
Summary: RHEL 7 spice-vdagent does not enter full-screen with monitor resolution
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: spice-vdagent
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Default Assignee for SPICE Bugs
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-18 14:10 UTC by Bill Sanford
Modified: 2014-02-24 00:46 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-24 00:46:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Bill Sanford 2012-07-18 14:10:41 UTC
Description of problem:
When trying to have a remote-viewer go to full-screen, RHEL 7 spice-vdagent does not enter full-screen with monitor resolution, but maximizes the current resolution that is configured.

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

How reproducible:
100%

Steps to Reproduce:
1. Run remote-viewer and enter full-screen.
2.
3.
  
Actual results:
The remote-viewer only maximizes the "Full-screen" to the monitor's currently configured resolution.

Expected results:
The remote-viewer should maximize the "Full-screen" to the monitor's maximum resolution.

Additional info:

Both vdagents are running on the guest and host.

service spice-vdagentd status
spice-vdagentd.service - LSB: Agent daemon for Spice guests
	  Loaded: loaded (/etc/rc.d/init.d/spice-vdagentd)
	  Active: active (exited) since Tue, 17 Jul 2012 08:52:12 -0400; 1 day and 1h ago
	 Process: 950 ExecStart=/etc/rc.d/init.d/spice-vdagentd start (code=exited, status=0/SUCCESS)
	  CGroup: name=systemd:/system/spice-vdagentd.service

Comment 2 Hans de Goede 2013-08-08 09:36:42 UTC
Bill, just to make sure I understand this correctly. The issue is that you've a monitor on the client side running at say 1600x900, but it is capable of doing 1920x1080, and you expect remote-viewer to change the client monitor resolution to 1920x1080 when going fullscreen ?

Comment 3 Bill Sanford 2013-11-19 15:33:19 UTC
Yes Hans.

Comment 5 Marc-Andre Lureau 2014-02-24 00:46:11 UTC
Changing the client resolution is wrong in many ways (unsafe, deletes user preference/configuration, breaks desktop layout window/icons, no safety/restore mechanism).

spicec used to do that, spicy used to have experimental code to do that, but virt-viewer will not. If you want higher resolutions, you need to configure your client monitor first.


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