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.
Fixed upstream in
commit 283434730d0cc3a1ee8270e137d71cebe4f0e01b
Author: Daniel P. Berrange <berrange>
Date: Tue Apr 11 11:06:28 2017 +0100
Report a proper error message if hitting connection timeout
Signed-off-by: Daniel P. Berrange <berrange>
commit a51e6a6973e9bdfcba0e52d3f9ee37686cd95db9
Author: Daniel P. Berrange <berrange>
Date: Tue Apr 11 10:47:56 2017 +0100
Fix crash when no error is set after connection failure
Signed-off-by: Daniel P. Berrange <berrange>
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/RHSA-2017:2258
Created attachment 1270707 [details] all thread backtrace Description of problem: As subject. Version-Release number of selected component (if applicable): virt-viewer-5.0-2.el7.x86_64 gtk-vnc2-0.7.0-1.el7.x86_64 How reproducible: 100% Steps to Reproduce: # remote-viewer vnc://www.baidu.com:5901 [1] 17633 segmentation fault (core dumped) remote-viewer vnc://www.baidu.com:5901 Backtrace: (gdb) bt full #0 0x00007fb5e4cf5b59 in vnc_connection_coroutine (conn=0x55afc41d8610 [VncConnection]) at vncconnection.c:5469 enumerator = 0x55afc403fd00 sock = 0x0 priv = 0x55afc41d4a70 addr = <optimized out> sockaddr = 0x0 conn_error = 0x0 conn = 0x55afc41d8610 [VncConnection] priv = <optimized out> s = {conn = 0x0, caller = 0x0, signum = 0, params = {cursor = 0x0, absPointer = 0, text = 0x0, ledstate = 0, area = {x = 0, y = 0, width = 0, height = 0}, size = {width = 0, height = 0}, pixelFormat = 0x0, authReason = 0x0, authUnsupported = 0, authCred = 0x0, authTypes = 0x0, message = 0x0}} #1 0x00007fb5e4cf5b59 in vnc_connection_coroutine (opaque=<optimized out>) at vncconnection.c:5513 conn = 0x55afc41d8610 [VncConnection] priv = <optimized out> s = {conn = 0x0, caller = 0x0, signum = 0, params = {cursor = 0x0, absPointer = 0, text = 0x0, ledstate = 0, area = {x = 0, y = 0, width = 0, height = 0}, size = {width = 0, height = 0}, pixelFormat = 0x0, authReason = 0x0, authUnsupported = 0, authCred = 0x0, authTypes = 0x0, message = 0x0}} #2 0x00007fb5e4cf94eb in coroutine_trampoline (cc=0x55afc41d4aa0) at coroutine_ucontext.c:55 co = 0x55afc41d4a70 #3 0x00007fb5e14dfd40 in __start_context () at /usr/lib64/libc-2.17.so #4 0x000055afc41d4e68 in () #5 0x0000000000000000 in () Actual results: As above Expected results: No segment fault Additional info: No reproduced on virt-viewer-2.0-12.el7.x86_64 gtk-vnc2-0.5.2-7.el7.x86_64