Bug 1235603 - xinetd-triggered Xvnc quits immediately
Summary: xinetd-triggered Xvnc quits immediately
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: tigervnc
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-25 10:02 UTC by Patrick Monnerat
Modified: 2015-07-03 18:40 UTC (History)
2 users (show)

Fixed In Version: tigervnc-1.4.3-8.fc22
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-07-03 18:40:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
xinetd configuration file for vnc service (302 bytes, text/plain)
2015-06-25 10:02 UTC, Patrick Monnerat
no flags Details

Description Patrick Monnerat 2015-06-25 10:02:06 UTC
Created attachment 1043032 [details]
xinetd configuration file for vnc service

Description of problem:
When triggered by xinetd, Xvnc closes the connection quickly after start.

Version-Release number of selected component (if applicable):
tigervnc-server-1.4.3-7.fc22

How reproducible:
Always.

Steps to Reproduce:
1. Add the line "vnc-1152x864x24         5929/tcp" to /etc/services.
2. Install xinetd. Create file /etc/xinetd.d/vnc-1152x864x24 with the attachment. Enable xinetd autostart.
3. Enable XDMCP in your display manager configuration.
4. Reboot.
5. Try a vnc connection on port 5929.

Actual results:
Connects, then immediately disconnects.

Expected results:
A usable remote graphical session.

Additional info:
This is the infamous "%*.*s" format bug in xorg. The problem has been fixed in xorg-x11-server-source-1.17.2-1.fc22 that has been produced just one day AFTER you compiled tigervnc-1.4.3-7 :-(
A simple rebuild of the tigervnc package with up to date dependencies resolves the problem.

Comment 1 Tim Waugh 2015-06-25 14:23:04 UTC
Thanks for the report. I've rebuilt it and will push an update to testing.

Comment 2 Fedora Update System 2015-06-25 14:39:12 UTC
tigervnc-1.4.3-8.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/tigervnc-1.4.3-8.fc22

Comment 3 Fedora Update System 2015-06-26 06:42:07 UTC
Package tigervnc-1.4.3-8.fc22:
* should fix your issue,
* was pushed to the Fedora 22 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing tigervnc-1.4.3-8.fc22'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-10772/tigervnc-1.4.3-8.fc22
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2015-07-03 18:40:05 UTC
tigervnc-1.4.3-8.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.


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