Bug 2357952

Summary:	Cannot connect to server 1.15.0 started from xinetd
Product:	[Fedora] Fedora	Reporter:	Patrick Monnerat <patrick>
Component:	tigervnc	Assignee:	Jan Grulich <jgrulich>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	41	CC:	jgrulich
Target Milestone:	---	Keywords:	Regression
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	tigervnc-1.15.0-5.fc43 tigervnc-1.15.0-5.fc42 tigervnc-1.15.0-5.fc41	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-04-08 13:27:59 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Patrick Monnerat 2025-04-07 15:01:57 UTC

When using (home-compiled) xinetd on the server, there is no way to start a dynamic vnc session

This is an upstream bug: https://github.com/TigerVNC/tigervnc/issues/1937

Used to work with tigervnc-server-1.14

Reproducible: Always

Steps to Reproduce:
1. On the server, prepare xinetd and a service scheduling Xvnc -inetd ...
2. Try to connect to service with vncviewer
Actual Results:  
Connection error

Expected Results:  
A dynamic vnc session

A dirty patch for it is listed in the upstream bug.

Comment 1 Fedora Update System 2025-04-08 13:24:56 UTC

FEDORA-2025-e75cc7e7f7 (tigervnc-1.15.0-5.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-e75cc7e7f7

Comment 2 Fedora Update System 2025-04-08 13:27:59 UTC

FEDORA-2025-e75cc7e7f7 (tigervnc-1.15.0-5.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 3 Fedora Update System 2025-04-08 13:29:30 UTC

FEDORA-2025-4e979b9d95 (tigervnc-1.15.0-5.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-4e979b9d95

Comment 4 Fedora Update System 2025-04-08 13:30:03 UTC

FEDORA-2025-e722a4e0e8 (tigervnc-1.15.0-5.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-e722a4e0e8

Comment 5 Fedora Update System 2025-04-09 01:25:23 UTC

FEDORA-2025-e722a4e0e8 has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-e722a4e0e8`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-e722a4e0e8

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2025-04-09 02:38:35 UTC

FEDORA-2025-4e979b9d95 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-4e979b9d95`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-4e979b9d95

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2025-04-17 19:00:06 UTC

FEDORA-2025-4e979b9d95 (tigervnc-1.15.0-5.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2025-04-24 17:33:01 UTC

FEDORA-2025-e722a4e0e8 (tigervnc-1.15.0-5.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.