On Wed, Aug 05, 2009 at 08:25:38PM +0200, Michael Biebl wrote: >Steve McIntyre wrote: >> >> Hmmm. What have you tried in an attempt to reproduce the bug? I can >> reproduce it at will here, and I can also see clearly related problems >> reproduced by people elsewhere: > >Could you please disable gdm for the time being, so that you can login on the >console.
OK, done. >I assume you have no network connection at this point, bug please double check. Correct, I do not have working networking at boot: no DHCP lease and no DHCP client that I can see running. >As you are using LDAP/NIS (please attach you configuration, nsswich.conf etc. >and if you use nscd/nslcd). We're using nscd. Attached tarball contains the nsswitch.conf, pam_ldap.conf and libnss_ldap.conf >Then stop the running network-manager instance and start it with >"NetworkManager --no-daemon" and attach the output. It hangs showing just one line (see typescript output). After 5 minutes I got bored and killed it. Script started on Thu 06 Aug 2009 13:49:36 BST smcintyre4:~# NetworkManager --no-daemon NetworkManager: <info> starting... Script done on Thu 06 Aug 2009 13:54:36 BST >Does NM successfully acquire an IP address via DHCP? Doesn't look like, no. >If not, what happens if you disable LDAP/NIS in your nsswitch configuration >(will probably also require a restart of dbus). If I disable LDAP in nsswitch and reboot, NetworkManager gets a lease from DHCP straight away. -- Steve McIntyre, Cambridge, UK. st...@einval.com "Because heaters aren't purple!" -- Catherine Pitt
conf.tar.gz
Description: Binary data
