Bug 441655 - Can't find a way to setup VNC login through xinetd
Can't find a way to setup VNC login through xinetd
Product: Fedora
Classification: Fedora
Component: gdm (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: jmccann
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-04-09 07:25 EDT by Frank Arnold
Modified: 2015-01-14 18:20 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-07-14 11:30:44 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Frank Arnold 2008-04-09 07:25:51 EDT
Description of problem:
That's not really a bug but degraded functionality, or at least missing
documentation. For some test boxes I usually set up a remote login like this:

Install xinetd and vncserver
chkconfig --del vncserver

Edit /etc/gdm/custom.conf

Add to /etc/services
  vnclogin1 5901/tcp

Create /etc/xinetd.d/vnclogin1 with following content
  service vnclogin1
  disable	=	no
  socket_type	=	stream
  protocol	=	tcp
  group		=       tty
  wait		=	no
  user		=	nobody
  server	=	/usr/bin/Xvnc
  server_args	=	-inetd -query localhost -geometry 800x600 -depth 16 -once
-securitytypes=none -desktop Domain-0

Finally, restart GDM, start xinetd, and probably poke a hole into the firewall.

This used to work with older Fedora releases and RHEL. Now that the GDM settings
are supposed to be managed through GConf, and gdmsetup is gone without
replacement I'm unable to find the right keys setup GDM accordingly.
Comment 1 Rex Dieter 2008-04-11 10:47:57 EDT
Fwiw, what you describe is essentially what vnc-ltsp-config does, but that 
doesn't address how each individual desktop/login manager handles enabling 

Comment 2 Bug Zapper 2008-05-14 05:11:13 EDT
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
Comment 3 Jonathan Underwood 2008-06-23 16:57:06 EDT
Isn't this a dupe of #446224 in essence - i.e. simply XDMCP in GDM being broken?
Comment 4 Bug Zapper 2009-06-09 20:05:26 EDT
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 5 Bug Zapper 2009-07-14 11:30:44 EDT
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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