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.
Descriptiontest_account_123
2019-01-23 06:14:37 UTC
Created attachment 1522580[details]
vncserver log file
Description of problem:
vncserver sessions crash (seemingly) erratically
Version-Release number of selected component (if applicable):
Xvnc TigervNC 1.3.1 - built Sep 12 2016 10:00:38
How reproducible:
Crashes seem erratical, no known way to reproduce it on demand
Steps to Reproduce:
1.Launch a vnc session as normal user (e.g. vncserver :0 -verbose)
2.Connect to the remote session and do (unrelated) work. The crash always happens while using the program Virtuoso Layout Editor from Cadence Design Systems.
3.The vnc session is fully functional for periods ranging from hours to days (using the aforementioned application), but eventually it crashes.
Actual results:
Xvnc TigervNC 1.3.1 - built Sep 12 2016 10:00:38
Copyright (C) 1999-2011 TigerVNC Team and many others (see README.txt)
See http://www.tigervnc.org for information on TigerVNC.
Underlying X server release 11702000, The X.Org Foundation
Tue Aug 28 20: 50: 36 2018
vncext: VNC extension running!
vncext: Listening for VNC connections on all interface(s), port 5903
vncext: created VNC server for screen O
xrdb : "XTerm*font" on line 46 overrides entry on line 39
xrdb : "XTerm*boldFont" on line 48 overrides entry on line 40
gnome-session-is-accelerated: llvmpipe detected.
Tue Aug 28 20: 50:45 2018
Connections: accepted: 10.2.15.197::56480
SConnection: Client needs protocol version 3.8
SConnection: Client requests security type VeNcrypt(19)
Tue Aug 28 20: 50:48 2018
VNCSConnST: Server default pixel format depth 24 (32bpp) little-endian rgb888
VNCSConnST: Client pixel format depth 24 (32bpp) little- endian rgb888
(EE)
(EE) Backtrace:
(EE) 0: /bin/Xvnc (xorg_backtrace+0x55) [0x5ba9f5]
(EE) 1: /bin/Xvnc (0x400000+0x1be9d9) [0x5be9d9]
(EE) 2: /usr/lib64/libpthread.so.0 (0x7f26c3f8f000+0xf370) [0x7f26c3f9e370]
(EE) 3: /bintXvnc (FlushA1lOutput+0xc5) [0x5be2c5]
(EE) 4: /bintXvnc (WaitForSomething+0x685) [0x5b8165]
(EE) 5: /bin/Xvnc (Dispatch+0x9d) [0x5698dd]
(EE) 6: /bin/Xvnc (dix_main+0x3db) [0x56dadb]
(EE) 7: /usr/lib64/1ibc.so.6 (__libc_start_main+0xf5) [0x7f26c3091b35]
(EE) 8: /bintXvnc (0x400000+0x4adba) [0x44adba]
(EE)
(EE) Segmentation fault at address 0x18
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)
Expected results:
Additional info:
Thanks for your reply, Jan. Unfortunately it is a production server, and upgrading the OS is not a feasible.
It might be possible to upgrade tigervnc, but as this would affect many users, management is requiring an indication that this would indeed solve the problem.
This is good news! Can you please confirm if updating to the latest tigervnc (for example, from https://bintray.com/tigervnc/stable/tigervnc/1.9.0) would solve the issue?
(Also, excuse my ignorance, but after reading bug 1425614 I can't see why these are the same bug, could you please explain me so that I can talk with my management?)
They both have same or similar backtrace, I cannot say that on 100% because your backtrace is not complete. In this case it was a crash in X server so you will need both updated.
I see. Can you please explain more about the update of X server? (I currently have xorg-x11-server-Xorg-1.17.2-22.el7.x86_64)
Also, can you please tell me how to generate a complete backtrace for our crash?