Bug 450478
Summary: | GDM & VNC & FC9 | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jonathan Loh <kj6loh> | ||||
Component: | vnc | Assignee: | Adam Tkac <atkac> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | low | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 9 | CC: | i.mortimer, ovasik | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i586 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2008-06-26 18:19:02 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: | |||||||
Attachments: |
|
Description
Jonathan Loh
2008-06-09 00:04:24 UTC
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 *** |