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.

Description of problem:
After changing resolution of guest system in remote-viewer using xrandr and running xrandr command again afterwards, the resolution is reverted back to the previous one. According to xrandr output, the resolution is still the same as set previously.

Version-Release number of selected component (if applicable):
Host & client: RHEL 7 
    qemu-kvm-1.5.2-2.el7.x86_64
    spice-server-0.12.4-1.el7.x86_64
    virt-viewer-0.5.7-1.el7.x86_64)

Guest: 
Fedora 19: spice-vdagent-0.14.0-2.fc19.x86_64
RHEL 7: spice-vdagent-0.14.0-3.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. make sure spice-vdagent service is running in guest (resolution is 1024x768)
2. execute 'xrandr -s 640x480'
3. execute 'xrandr' to trigger the resolution reversion (with RHEL7 guest this step is not needed) 

Actual results:
Guest screen resolution changes back from 640x480 to 1024x768, even though xrandr output states the actual resolution is still 640x480.

Expected results:
Guest screen resolution stays the same as set.

Additional info:

Created attachment 783302 [details]
remote-viewer --spice-debug log

Created attachment 783303 [details]
spice-vdagent log

This is a problem with the new kms driver, where the agent is no longer involved in the display resizing path. I've done some testing and it seems that monitor changes don't get seen by the guest (by gnome-settings-daemon?) until xrandr is run.

IE if you fullscreen the client window then running xrandr from a terminal will actually resize the guest to the fullscreen resolution, where one would expect the resize to happen immediately upon going fullscreen (tested with a fully up2date F-19).

It seems that using kms also sometimes causes empty monitor config info to the client, ie during my F-19 tests I get various messages like these:

(remote-viewer:14603): GSpice-CRITICAL **: display_handle_monitors_config: assertion 'config->count > 0' failed

This doesn't reproduce for me with a RHEL 7 Beta 1 guest and host.

Is this still reproducible?

In RHEL7 Beta1, I couldn't reproduce. However, the warning message as reported by Hans is still being printed.

I have filed 

    https://bugzilla.redhat.com/show_bug.cgi?id=1061942

to track the warning message.

Closing this bug since it isn't reproducible any more.