Bug 450421

Summary: gdm logins for YP users fail, xorg gets SIGTERM
Product: [Fedora] Fedora Reporter: Brian Cain <brian.cain>
Component: gdmAssignee: jmccann
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 9CC: cschalle, 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: 2008-06-29 02:03:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Brian Cain 2008-06-08 03:22:02 UTC
Description of problem:

When attempting a graphical login of a YP user (whose home directory is
automounted via NFS), the X server appears to crash (strace indicates that it
receives SIGTERM and the screen rapidly changes modes and returns to gdm's
greeter w/o any indication of an error).

A text-mode login of YP users (locally using a different VT or remotely via ssh)
succeeds without error.  After a successful local console login, executing
'startx' brings up a GNOME desktop without error.

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

How reproducible:

Out of ten trials (across multiple hardware platforms, one was the HP xw9400
workstation), all ten failed.

Steps to Reproduce:
1.configure YP, autofs (edit yp.conf, auto.master) to match network settings
2.start ypbind
3.start autofs
4.attempt graphical login at GDM greeter

Actual results:

Login attempt fails without explicit error indication.  syslog includes
complaints about inability to set some read-only screensaver...power_management
value from gconfd.  Nothing I have done has been able to address that issue, but
I'm not so sure that it's a part of the login problem.

Expected results:

Login succeeds without error.  User is presented with GNOME desktop.

Additional info:

I've tried removing .gconf*, .gnome*, from the user's home directory, none of
which appears to resolve this problem.  Complicating things is the fact that
ypbind does not typically get started by NetworkManager (though chkconfig
indicates that ypbind is 'on' for runlevels 3,4,5).  Or perhaps NetworkManager
invokes/contacts ypbind before the interface is ready for traffic?  Hopefully
there's already a bug on that issue.

The ypbind daemon was running during all of the trials described above.

Comment 1 Ray Strode [halfline] 2008-06-08 04:56:02 UTC
what version of gdm?

Comment 2 Brian Cain 2008-06-08 14:17:55 UTC
$ rpm -qa | grep gdm

$ cat /etc/redhat-release
Fedora release 9 (Sulphur)

$ cat /etc/gdm/custom.conf
# GDM configuration storage




Comment 3 Ray Strode [halfline] 2008-06-09 15:43:18 UTC
Ah, can you try upgrading to 2.22.0-5 ?  I think it should address this issue.

Comment 4 Brian Cain 2008-06-09 18:22:16 UTC
2.22.0-5 did not address the problem.

$ rpm -qa | grep gdm


$ cat /etc/gdm/custom.conf
# GDM configuration storage




Comment 5 Brian Cain 2008-06-29 02:05:10 UTC
Apologies.  This behavior looks like it was caused by an `exec bash` in my NIS
account's .bashrc.