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.
Bug 1826726 - TigerVNC exits at startup
Summary: TigerVNC exits at startup
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: tigervnc
Version: 8.1
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: 8.0
Assignee: Jan Grulich
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1826822 1826839 1826841
TreeView+ depends on / blocked
 
Reported: 2020-04-22 12:32 UTC by Andrew Haley
Modified: 2020-05-11 12:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1826822 1826839 1826841 (view as bug list)
Environment:
Last Closed: 2020-05-11 12:40:41 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Andrew Haley 2020-04-22 12:32:12 UTC
Description of problem:

Tigervnc exits at startup

Version-Release number of selected component (if applicable):

tigervnc-1.9.0-14.el8_1.src.rpm

How reproducible:

Every time

Steps to Reproduce:
1. vncserver :1
2. vncviewer :1

Actual results:
 $ vncserver :1

New 'zarquon.pink:1 (aph)' desktop is zarquon.pink:1

Starting applications specified in /home/aph/.vnc/xstartup
Log file is /home/aph/.vnc/zarquon.pink:1.log
 $ vncviewer :1

TigerVNC Viewer 64-bit v1.9.0
Built on: 2020-04-09 13:36
Copyright (C) 1999-2018 TigerVNC Team and many others (see README.rst)
See http://www.tigervnc.org for information on TigerVNC.

Wed Apr 22 13:15:49 2020
 DecodeManager: Detected 32 CPU core(s)
 DecodeManager: Creating 4 decoder thread(s)
 CConn:       connected to host localhost port 5901
 CConnection: Server supports RFB protocol version 3.8
 CConnection: Using RFB protocol version 3.8
 CConnection: Choosing security type VeNCrypt(19)
 CVeNCrypt:   Choosing security type TLSVnc (258)

Wed Apr 22 13:15:53 2020
 CConn:       Invalid display size
 $

Comment 3 George 2020-04-24 13:17:42 UTC
+1
Had to downgrade to 1.9.0-10, to get my remote desktop back.
Inconvenient when working from home.
Is there a workaround for v1.9.0-14?

Comment 4 Jan Grulich 2020-04-24 14:24:22 UTC
There is 1.9.0-15 on the way. Until then you can just use the older version. I'm sorry for all the troubles.


Note You need to log in before you can comment on or make changes to this bug.