Bug#308825: ,gdm logins fail to start sessions

[Steve Langasek]

--T1STeyE7BzLxwmnN
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, May 20, 2005 at 08:42:33AM -0500, Jay Kline wrote:
> Steve Langasek wrote:
> | On Wed, May 18, 2005 at 08:31:51AM -0500, Jay Kline wrote:
> |
> |>Steve Langasek wrote:
> |>| On Wed, May 18, 2005 at 07:51:05AM -0500, Jay Kline wrote:
> |>|
> |>|>| Jay, taking care to run rm -f /usr/lib/libldap.so.2.0.15 before
> |>doing so,
> |>|>| would you mind upgrading to the libldap2 from unstable to see if it
> |>fixes
> |>|>| your problem?
> |
> |
> |>| Does this mean you only upgraded to 2.1.30-6?  You need 2.1.30-7 from
> |>| unstable to check whether it's the bug we fixed.
> |
> |
> |>Oops, my mistake.  Our local repository hasnt been updated since we
> |>started running into problems.  However, still no change with these
> |>versions:
> |
> |
> |>ldap-utils     2.1.30-3
> |>libldap-2.2-7  2.2.23-1
> |>libldap2       2.1.30-7
> |>libldap2       2.1.30-7
> |>libnss-ldap    238-1
> |>libpam-ldap    178-1
> |>gdm            2.6.0.8-1
> |
> |
> | Are you running nscd on this system?  (That package enjoys frequent
> mention
> | in the log of bug #302296.)  If so, can you please restart it and see if
> | that makes a difference?

> Heh- no, we avoid that like the plague.  Being a DoD site we rather not
> deal
> with software with a track record like that. :-) We have libnss-ldap
> going directly to the ldap server.

Ok... :)

How about restarting gdm itself?

--=20
Steve Langasek
postmodern programmer

--T1STeyE7BzLxwmnN
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCj4k5KN6ufymYLloRAl2TAJ9zDHK4i+E4liK1cS0Np9I28iO8TACcDf5s
bc32UMEA9DsPbRx6VmsmCYM=
=ps+F
-----END PGP SIGNATURE-----

--T1STeyE7BzLxwmnN--