From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.7) Gecko/20050416 Fedora/1.0.3-1.3.1 Firefox/1.0.3 Description of problem: I'd been using early-login for a few days but the 4/24 or 4/25 update broke it. Everything looks like it's working normally but when you actually try to login, it complains about "Cannot start the session due to some internal error." The details are that "session_child_run: Could not exec /etc/X11/xdm/Xsession gnome-session". If I restart the system and remove early-login from the kernel cmdline, logging in works fine. Version-Release number of selected component (if applicable): gdm-2.6.0.8-7 How reproducible: Always Steps to Reproduce: 1. enable early-login 2. 3. Actual Results: login fails Expected Results: login works Additional info: I've enabled early-login based on Ray Strode's post a few weeks back. chkconfiged the three gdm related init scripts, changed xfs and syslog start numbers, etc.
I've seen this problem too. For me, it seems to be a 'mismatch' caused by early-login and init: some init scripts appear to be executing in the SELinux domain 'init_t' instead of 'initrc_t'. This appears to cause lots of access failures, I believe when it checks to see if the display manager is already running. I haven't had time yet to completely track this down. The first time this happened, I worked around it by 'CTL-ALT-F2' to a text screen, logging in as root, and doing a 'setenforce 0'. 'CTL-ALT-F7' restores the graphical stuff, and things work. You can also boot with 'early-login enforcing=0'.
Does installing firstboot change anything?. Based on https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=159140
I'm going to close this bug, since the early-login experiment is pretty much over with now.