Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionJonathon Jongsma
2014-09-17 15:26:15 UTC
Created attachment 938522[details]
screenshot of virt-viewer at the end of the "steps to reproduce"
Description of problem:
In RHEL7 (and fedora20), when you disable the first display, the guest appears to malfunction and returns a MONITORS_CONFIG message indicating that no displays are enabled. This triggers several command-line warnings and causes gnome-shell to crash. It also generally leaves the vm in an unusable state:
(virt-viewer:20309): GSpice-CRITICAL **: display_handle_monitors_config: assertion 'config->count > 0' failed
(virt-viewer:20309): GSpice-CRITICAL **: display_handle_monitors_config: assertion 'config->count > 0' failed
(virt-viewer:20309): GSpice-CRITICAL **: display_handle_monitors_config: assertion 'config->count > 0' failed
(virt-viewer:20309): GSpice-CRITICAL **: display_handle_monitors_config: assertion 'config->count > 0' failed
The problem is reproducible using a rhel6 host and a fedora20 host. It's not immediately clear to me in which component the bug exists.
Version-Release number of selected component (if applicable):
HOST:
qemu-kvm-0.12.1.2-2.439.el6.x86_64
spice-server-0.12.4-11.el6.x86_64
GUEST:
RHEL7
xorg-x11-drv-qxl-0.1.1-9.el7.x86_64
spice-vdagent-0.14.0-7.el7.x86_64
gnome-shell-3.8.4-32.el7_0.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Connect to rhel7 guest with virt-viewer
2. enable 2nd display
3. disable 1st display
Actual results:
The symptoms are not always the same. The guest generally shows the gnome-shell "oops, I crashed" screen after a short timeout, requiring the user to click 'logout'. After logging out, the desktop sometimes recovers, but often simply leaves the user with one or two black windows and no way to interact with the guest or enable / disable new displays.
Expected results:
The first display disappears and only the second display remains.
Additional info:
Fedora 20 also misbehaves in a similar way, but the symptoms are not identical.
As far as I've been able to determine, the monitor configuration information is passed on to the guest correctly, but the guest is not reconfiguring the displays correctly. Moving to gnome-shell for now, though that may not be the correct component.
This is the only error I get from gnome-shell on the commandline
Window manager warning: Log level 6: The program 'gnome-shell' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 1927 error_code 2 request_code 137 (XFIXES) minor_code 31)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
this is not reproducible any more. No gnome-shell crash.
guest - rhel7.6
gnome-shell-3.28.3-2.el7
spice-vdagent-0.14.0-16.el7
client - rhel6.10
spice-gtk-0.26-8.el6
virt-viewer-2.0.18.el6
Created attachment 938522 [details] screenshot of virt-viewer at the end of the "steps to reproduce" Description of problem: In RHEL7 (and fedora20), when you disable the first display, the guest appears to malfunction and returns a MONITORS_CONFIG message indicating that no displays are enabled. This triggers several command-line warnings and causes gnome-shell to crash. It also generally leaves the vm in an unusable state: (virt-viewer:20309): GSpice-CRITICAL **: display_handle_monitors_config: assertion 'config->count > 0' failed (virt-viewer:20309): GSpice-CRITICAL **: display_handle_monitors_config: assertion 'config->count > 0' failed (virt-viewer:20309): GSpice-CRITICAL **: display_handle_monitors_config: assertion 'config->count > 0' failed (virt-viewer:20309): GSpice-CRITICAL **: display_handle_monitors_config: assertion 'config->count > 0' failed The problem is reproducible using a rhel6 host and a fedora20 host. It's not immediately clear to me in which component the bug exists. Version-Release number of selected component (if applicable): HOST: qemu-kvm-0.12.1.2-2.439.el6.x86_64 spice-server-0.12.4-11.el6.x86_64 GUEST: RHEL7 xorg-x11-drv-qxl-0.1.1-9.el7.x86_64 spice-vdagent-0.14.0-7.el7.x86_64 gnome-shell-3.8.4-32.el7_0.x86_64 How reproducible: 100% Steps to Reproduce: 1. Connect to rhel7 guest with virt-viewer 2. enable 2nd display 3. disable 1st display Actual results: The symptoms are not always the same. The guest generally shows the gnome-shell "oops, I crashed" screen after a short timeout, requiring the user to click 'logout'. After logging out, the desktop sometimes recovers, but often simply leaves the user with one or two black windows and no way to interact with the guest or enable / disable new displays. Expected results: The first display disappears and only the second display remains. Additional info: Fedora 20 also misbehaves in a similar way, but the symptoms are not identical.