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.
Description of problem:
cannot display graphical console after upgrading spice-gtk to 0.33-1
Version-Release number of selected component (if applicable):
virt-install-1.4.1-1.el7.noarch
spice-glib-0.33-1.el7.x86_64
spice-gtk3-0.33-1.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Upgrade spice-gtk3 and spice-glib to latest 0.33-1.el7
2. Reopen virt-manager and start up a spice guest.
3. Double click the guest to open the graphical console.
Actual results:
Black screen displays and only can see mouse cursor on desktop.
Expected results:
virt-manager should display graphic console correctly.
Additional info:
For issues like this, please also check if virt-viewer reproduces the issue. If so, it's likely a spice issue. If virt-viewer works and virt-manager fails, probably virt-manager specific.
(In reply to Cole Robinson from comment #5)
> For issues like this, please also check if virt-viewer reproduces the issue.
> If so, it's likely a spice issue. If virt-viewer works and virt-manager
> fails, probably virt-manager specific.
yes, only virt-manager fails. i didn't describe it clearly.
This is most likely spice-gtk issue even though virt-viewer is not affected by the updated.
If you run virt-manager --debug you can see that there is a spice warning:
(virt-manager:29969): Spice-WARNING **: channel-display-gst.c:303:create_pipeline: GStreamer error: no element "avdec_h264"
and the same warning is printed if you run virt-viewer:
(virt-viewer:30071): Spice-WARNING **: channel-display-gst.c:303:create_pipeline: GStreamer error: no element "avdec_h264"
The rebase to 0.33 version add a new build requirements for gstreamer1 however there is no gstreamer1-libav on RHEL and it probably breaks virt-manager because if I compile spice-gtk witout gstreamer virt-manager works correctly.
Even RPM compilation prints a warning about it:
configure: WARNING: The avdec_h264 GStreamer element(s) are missing. You should be able to find them in the gstreamer-libav 1.0 package.
configure: WARNING: The GStreamer video decoder can be built but may not work.
interesting, I don't see how gstreamer can affect it. I can do a scratchbuild
(it is just an optional runtime stuff for video streaming decompression and these warnings should rather be debugs )
It is related to the gtk version used during the build.
The working build mentioned in the comment 7 uses gtk 3.22 while the original build uses gtk 3.14
gstreamer addition is unrelated to the issue
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.
https://access.redhat.com/errata/RHBA-2017:1849