Description of problem: Trying to run vnc and gdm it worked on FC6-7. But I upgraded to 9, and it does not work. I suspect it may be due to the fact that gdm was upgraded. What I mean by it does'nt work is that vnc connects and a window is brought up on the remote computer but rather than having me log in. It just gives me a blank screen. Previously, I was presented with a login screen. Version-Release number of selected component (if applicable): vnc-4.1.2-30.fc9.i386 gdm-2.22.0-5.fc9.i386 How reproducible: Just did a fresh install on another box and it doesn't work either. I'll include my pertinent config files Steps to Reproduce: 1. Need gdm, xinet, and vnc installed 2. Add the configs 3. vncviewer localhost:0 Oh and then you'll need to punch the requisite holes in your firewall. I'm not using SELinux so it isn't that. Actual results: get a grey window. Expected results: Should be prompted for a login. Additional info:
Created attachment 308664 [details] settings
I'm having the same problem with a configuration that worked with F8. When Xvnc starts from xinetd on F8 two new processes start: /usr/sbin/gdm-binary -nodaemon /usr/libexec/gdmlogin On F9, no extra gdm related processes start (hence the blank screen).
Similar result with vnc-ltsp-config.
(In reply to comment #2) > I'm having the same problem with a configuration that worked with F8. When Xvnc > starts from xinetd on F8 two new processes start: > > /usr/sbin/gdm-binary -nodaemon > /usr/libexec/gdmlogin > > On F9, no extra gdm related processes start (hence the blank screen). > It seems that you are running machine in runlevel 3. I think that in F8 you modified /etc/inittab to start gdm also in runlevel 3 (line "x:5:respawn:/etc/X11/prefdm -nodaemon" changed to "x:35:respawn:/etc/X11/prefdm -nodaemon" or something similar). Would it be possible confirm it, please? Thanks
Added ian.edu.au to CC (please see comment #4)
Next problem is in gdm because it parses custom.conf configuration file wrongly - see bug #452528
> It seems that you are running machine in runlevel 3. In this case (on F8) the (server) host is in runlevel 5: # runlevel N 5 -- Ian
(In reply to comment #7) > > It seems that you are running machine in runlevel 3. > > In this case (on F8) the (server) host is in runlevel 5: > Small misunderstood. I'm talking about that broken F9 machine. Does it also running in runlevel 5? If yes then gdm-binary should run. In other runlevels gdm doesn't run.
(In reply to comment #8) > Small misunderstood. I'm talking about that broken F9 machine. Does it also > running in runlevel 5? If yes then gdm-binary should run. In other runlevels gdm > doesn't run. Both hosts (working f8 and failing f9) are in runlevel 5 and gdm-binary is running on both. I was talking about an *additional* gdm-binary and a gdmlogin process which gets launched on f8 when you make a vnc connection. No *additional* gdm related processes get launched on f9 when you make a vnc connection. What this indicates (I think) is that it's a gdm problem rather than a xinetd or vncserver problem. -- Ian
(In reply to comment #9) > What this indicates (I think) is that it's a gdm problem rather than a xinetd or > vncserver problem. > Right you are *** This bug has been marked as a duplicate of 452528 ***