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:
A crash occurs when connecting to a spice guest by ssh from fedora24 to rhel7
Version-Release number of selected component (if applicable):
spice-gtk-0.31-4.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Prepare a spice guest running on rhel7 host.
2. Prepare a fedora24 host.
3. SSH to rhel7 host from fedora24.
4. Launch virt-viewer/remote-viewer to connect to a spice guest.
Actual results:
# remote-viewer spice://127.0.0.1:5900
** (remote-viewer:10597): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-7jLRj4kWh2: Connection refused
(remote-viewer:10597): GSpice-WARNING **: PulseAudio context failed Connection refused
(remote-viewer:10597): GSpice-WARNING **: pa_context_connect() failed: Connection refused
(remote-viewer:10597): GSpice-WARNING **: PulseAudio context failed Connection refused
(remote-viewer:10597): GSpice-WARNING **: pa_context_connect() failed: Connection refused
(remote-viewer:10597): GSpice-WARNING **: PulseAudio context failed Connection refused
(remote-viewer:10597): GSpice-WARNING **: pa_context_connect() failed: Connection refused
libEGL warning: DRI3: failed to query the version
libEGL warning: DRI2: failed to authenticate
(remote-viewer:10597): GSpice-CRITICAL **: egl init failed: cannot create EGL context
(remote-viewer:10597): Gdk-ERROR **: The program 'remote-viewer' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
(Details: serial 325 error_code 1 request_code 153 (unknown) minor_code 1)
(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.)
Trace/breakpoint trap (core dumped)
Expected results:
No crash should occur and connect to spice guest successfully.
Additional info:
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://rhn.redhat.com/errata/RHBA-2016-2229.html