Bug 478791

Summary:	blank vnc window
Product:	[Fedora] Fedora	Reporter:	Ian Mortimer <i.mortimer>
Component:	vnc-ltsp-config	Assignee:	Rex Dieter <rdieter>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	low
Version:	10	CC:	rdieter
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-01-13 01:26:40 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 Ian Mortimer 2009-01-05 02:21:55 UTC

Description of problem:
With vnc-ltsp-config installed and configured according to the instructions, vnc connection to the terminal server gets a blank window for any of the configured ports (5900 - 5905)


Version-Release number of selected component (if applicable):
vnc-ltsp-config-4.0-5.fc10

How reproducible:
Always

Steps to Reproduce:
1. install vnc-ltsp-config
2. chkconfig vncts on
3. configure /etc/gdm/custom.conf /etc/X11/xdm/Xaccess
4. restart gdm
5. start remote vnc connection to one of the configured ports
  
Actual results:
vncviewer shows a blank window.  Logs show Xvnc started by xinted but ps shows no additional gdm processes being started.

Expected results:
a gdm login screen should display in the vncviewer window


Additional info:
A configuration like this worked up to Fedora 8 but I haven't been able to get it working with Fedora 9 or 10.  I tried with xorg-x11-xfs installed and xfs running which was needed with Fedora 7 or 8.  I also tried with xfs turned off.

I have this in /etc/gdm/custom.conf:

[xdmcp]
Enable=true

I tried with localhost in /etc/X11/xdm/Xaccess and also with * (any host can connect) but no luck with either.

Since Fedora 8 is now EOL, I need to upgrade our vnc terminal servers to 9 or 10 as soon as possible.


Thanks
--
Ian

Comment 1 Rex Dieter 2009-01-05 02:47:48 UTC

Your symptom usually means xdmcp isn't working.

I'm unfamiliar with gdm (kde/kdm user myself), but I can vouche that it works with kdm.

Comment 2 Ian Mortimer 2009-01-05 03:22:46 UTC

(In reply to comment #1)

> Your symptom usually means xdmcp isn't working.

That's true.  netstat -l confirms nothing listening on the xdmcp port (177).

> I'm unfamiliar with gdm (kde/kdm user myself), but I can vouche that it works
> with kdm.

Ok.  I'll try with kdm.  Since gdm is the default display manager, it should work so I'll post a bug against gdm also.

Thanks for the quick reply.

Comment 3 Ian Mortimer 2009-01-13 01:26:40 UTC

Fixed in gdm-2.24.1-4.fc10 from updates-testing.