Bug 531195

Summary: [gdm] fails to start (probably due to update)
Product: [Fedora] Fedora Reporter: Joachim Frieben <jfrieben>
Component: gdmAssignee: jmccann
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: rawhideCC: atorkhov, awilliam, cschalle, jmccann, mattdm, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-10-29 13:29:42 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 473303    

Description Joachim Frieben 2009-10-27 04:20:33 EDT
Description of problem:
After a fresh install from the Fedora "rawhide" tree on 2009-10-25, the GDM login manager seems to work correctly. It's (probably) after updating to a later Koji version, that it does not start up anymore after rebooting the system.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install current Fedora "rawhide".
2. Update package gdm to later Koji version.
3. Restart system.
Actual results:
System starts up but X does not get started when entering runlevel 5.

Expected results:
X and GDM start up as expected.

Additional info:
A suspicious entry appears in /var/log/secure related to the update of package gdm:

  "localhost useradd[2459]: failed adding user 'gdm', data deleted"
Comment 1 Matthew Miller 2009-10-27 10:46:07 EDT
Same here. If run from the command line as root afterward, gdm just exits silently.

I have the same log entry in /var/log/secure.

The gdm user *does* exist, with what looks like the correct information (uid 42, home dir /var/lib/gdm, shell /sbin/nologin).

I don't have a koji version, though -- just what's in rawhide right now.

Comment 2 Joachim Frieben 2009-10-27 11:34:01 EDT
(In reply to comment #1)
Issue seems to have been fixed by today's "rawhide" update including a fair number of GNOME updates - can you confirm? Also gone are erratically missing sound and flickering keyboard lights apparently related to this bug.
Comment 3 Matthew Miller 2009-10-27 11:40:33 EDT
Joachim -- I see only gdm-2.28.1-5.fc12 in rawhide right now, and that's what's not working for me.
Comment 4 Ray Strode [halfline] 2009-10-27 17:22:18 EDT
perhaps a transient selinux bug?
Comment 5 Matthew Miller 2009-10-27 18:41:47 EDT
Not here -- selinux is disabled on this box after running into eighteen too many times when that *was* the case. :)
Comment 6 Ray Strode [halfline] 2009-10-27 19:20:04 EDT
It sounds like this may not be related to gdm, though.  Can you try doing a full rawhide update?

Might be gnome-settings-daemon or something else...
Comment 7 Ray Strode [halfline] 2009-10-27 19:20:41 EDT
Also, Matt, do you have nvidia hardware?
Comment 8 Matthew Miller 2009-10-27 19:58:44 EDT
ATI Radeon M76XT. This happened after yum upgrade to rawhide this morning and reboot. Oh, and installed the koji kernel to fix from bug #517625.

I'll try again tomorrow. Nothing is logged and the binary just exits. Nothing is apparently logged. I switched to kdm as a workaround, but I'm happy to try any diagnostics you want. I'm actually using xfce as the desktop once logged in.
Comment 9 Alexey Torkhov 2009-10-29 06:56:48 EDT
I'm not sure, if this is the same issue or not, but my gdm also has similar simptoms with fail to start. But it is able to start when called with "sh /usr/sbin/gdm".

Log from wrapper script if set -x added to it:

Log from sh -x gdm:

As seen, when called directly, it stops at ". /etc/profile.d/modules.sh". If called via sh, it continues though that call. Very weird.
Comment 10 Matthew Miller 2009-10-29 07:10:34 EDT
Ah -- it hadn't even occurred to me to check if the gdm binary was a script. I also have environment-modules installed. I'll poke around today and see where that gets me.
Comment 11 Adam Williamson 2009-10-29 13:07:02 EDT
I'm setting this as a blocker to be reviewed tomorrow, as it's a worrying looking bug.

Fedora Bugzappers volunteer triage team
Comment 12 Joachim Frieben 2009-10-29 13:24:25 EDT
(In reply to comment #1)
Matt, as stated in a previous comment, the issue is gone for me. I should add though that as long as GDM failed to start up as expected, I was nevertheless able to bring it up by executing 'gdm-binary' from a root shell. Have you tried that one, too? I haven't seen GDM exit silently then as you seem to observe. It is also true however, that I was unable to find any trace of the previous failed attempt in any log file.
Comment 13 Ray Strode [halfline] 2009-10-29 13:29:42 EDT
Looking at the changelog for environment-modules, this is already fixed.

*** This bug has been marked as a duplicate of bug 530770 ***
Comment 14 Adam Williamson 2009-10-29 13:39:45 EDT
whoops, I should've caught that, sorry Ray.

Matthew, can you confirm that it works if you update to environment-modules-3.2.7b-5.fc12 ?

Fedora Bugzappers volunteer triage team
Comment 15 Matthew Miller 2009-10-29 13:49:59 EDT
Yes, just got to testing this, and it does indeed work with the updated environment-modules package. Thanks guys.