[Bug 68271] Re: slapd starts too late, causing X startup problems

2008-01-22 Thread Chuck Short
*** This bug is a duplicate of bug 67404 *** https://bugs.launchpad.net/bugs/67404 ** This bug has been marked a duplicate of bug 67404 bind policy in 251-5.2 breaks the whole system -- slapd starts too late, causing X startup problems https://bugs.launchpad.net/bugs/68271 You received th

[Bug 68271] Re: slapd starts too late, causing X startup problems

2007-02-23 Thread Sergey V. Udaltsov
Slapd should be start earlier than gdm - so if gdm starts at sequnce number 13, slapd should be at least 12. Also, /etc/libnss_ldap.conf should be readable by everybody (in dapper it is rw---) -- slapd starts too late, causing X startup problems https://launchpad.net/bugs/68271 -- ubuntu-b

[Bug 68271] Re: slapd starts too late, causing X startup problems

2006-10-30 Thread Alessandro Amici
I see the client machine problem as well. The problem appear to be that something in the boot process uses libnss- ldap before the network is up and the machine hangs. This can be worked-around with 'bind_policy soft' in /etc/libnss- ldap.conf, but then mounting an NFS filesistem (/home) fails.

[Bug 68271] Re: slapd starts too late, causing X startup problems

2006-10-30 Thread Alessandro Amici
This appears to be related to Bug #67404. -- slapd starts too late, causing X startup problems https://launchpad.net/bugs/68271 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs