# proposed patch worked for the submitter
tags 308825 + patch
# upstream has closed the bug with 2.14 series
tags 308825 + moreinfo
stop

On Thu, Mar 16, 2006, Daniel Kahn Gillmor wrote:
> i've run into this problem (or something very similar) with the
> version of gdm in ubuntu 5.10 (gdm 2.8.0.5-0ubuntu1).  my
> /etc/nsswitch.conf uses "ldap compat", and i've removed nscd entirely.
> i'm not using LDAP for PAM at all (preferring krb5 authentication).
> 
> Thanks to the suggestions by Rob Caelers in this bug, i looked into
> problems with gdm_close_all_descriptors(), and reported my findings
> upstream to what looks like the relevant gdm GNOME bug [0].  With
> Brian Cameron's help, i found and removed a single offending call to
> gdm_close_all_descriptors() in daemon/display.c, and now gdm
> successfully works for logging in.
> 
> the patch i used against the ubuntu version was this:
> 
> diff -Nur gdm-2.8.0.5/daemon/display.c gdm-2.8.0.5.new/daemon/display.c
> - --- gdm-2.8.0.5/daemon/display.c    2005-07-19 03:53:42.000000000 -0400
> +++ gdm-2.8.0.5.new/daemon/display.c  2006-03-16 13:53:58.000000000 -0500
> @@ -307,7 +307,7 @@
>       closelog ();
>  
>       /* Close everything */
> - -   gdm_close_all_descriptors (0 /* from */, fds[0] /* except */, 
> slave_fifo_pipe_fd /* except2 */);
> +     if (0) gdm_close_all_descriptors (0 /* from */, fds[0] /* except */, 
> slave_fifo_pipe_fd /* except2 */);
>  
>       /* No error checking here - if it's messed the best response
>           * is to ignore & try to continue */
> 
> 
> i hope this helps other people to resolve this bug.  let me know if i
> can be of further assistance with it.
> 
>       --dkg
> 
> [0] http://bugzilla.gnome.org/show_bug.cgi?id=315846
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2.2 (GNU/Linux)
> Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>
> 
> iD8DBQFEGc4iiXTlFKVLY2URAgUjAJ4iOxQY7C7WUroPvPd8y6DHj2jWZwCePNIV
> 0H+ufwLiRMX50cK3Q3524XM=
> =ptz6
> -----END PGP SIGNATURE-----
> 
> 

-- 
Loïc Minier <[EMAIL PROTECTED]>

Reply via email to