** Attachment added: "ldap.conf"
   http://librarian.launchpad.net/4685613/ldap.conf

** Description changed:

  I'm running beta Edgy. I had a working ldap server on localhost (serving
  also another PC in the house running Dapper). I did a dist-upgrade last
  night. There were 98 new packages, among them a new version of udev
- (ubuntu17). On restart, the system took more than 20 minutes to boot and
- displayed lots of messages about being unable to connect to the ldap
- server. Unfortunately, I'm about to leave on a trip to the u.s. until
- next tuesday, so I'm going to attach a bunch of files in the hope that
- one of them will be able to help you narrow the problem down.
+ (ubuntu17) and hal.
+ 
+ On restart, the system took more than 20 minutes to boot and displayed
+ lots of messages about being unable to connect to the ldap server.
+ 
+ udevd [2128]: nss_ldap: could not connect to any LDAP server.
+ 
+ 
+ Unfortunately, I'm about to leave on a trip to the u.s. until next tuesday, 
so I'm going to attach a bunch of files in the hope that one of them will be 
able to help you narrow the problem down.

** Description changed:

  I'm running beta Edgy. I had a working ldap server on localhost (serving
  also another PC in the house running Dapper). I did a dist-upgrade last
  night. There were 98 new packages, among them a new version of udev
  (ubuntu17) and hal.
  
  On restart, the system took more than 20 minutes to boot and displayed
  lots of messages about being unable to connect to the ldap server.
  
  udevd [2128]: nss_ldap: could not connect to any LDAP server.
  
  
- Unfortunately, I'm about to leave on a trip to the u.s. until next tuesday, 
so I'm going to attach a bunch of files in the hope that one of them will be 
able to help you narrow the problem down.
+ Unfortunately, I'm about to leave on a trip to the u.s. until next tuesday, 
so I'm going to attach a bunch of files in the hope that one of them will be 
able to help you narrow the problem down. 
+ 
+ The only work around I found was to revert the ldap changes and use
+ files/compat instead. The system works fine without ldap.

-- 
[Edgy] Problems with latest upgrades and ldap
https://launchpad.net/bugs/64307

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to