[Bug 208657] Re: package samba-common 3.0.28a-1ubuntu2 failed to install/upgrade: subprocess post-installation script returned error exit status 1
As per original post, after the failed merge, I let the install overwrite then manually merged my changes. (Actually, now I can't remember in which direction I did the merge.) -- package samba-common 3.0.28a-1ubuntu2 failed to install/upgrade: subprocess post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/208657 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 208657] Re: package samba-common 3.0.28a-1ubuntu2 failed to install/upgrade: subprocess post-installation script returned error exit status 1
Ok, sorry for overlooking that in your original report. In that case, I'm afraid we probably can't resolve this bug because the information needed in order to reproduce the failure has been lost. ** Changed in: samba (Ubuntu) Status: New = Incomplete -- package samba-common 3.0.28a-1ubuntu2 failed to install/upgrade: subprocess post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/208657 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 155947] Re: ldap config causes Ubuntu to hang at a reboot
On Tue, 2008-04-08 at 12:07 +, Kevin Slater wrote: I had the problem in two different desktop machines running Fiesty, with LDAP client authentication working, when I upgraded them to Gutsy. @Kevin, Thanks for confirming our suspicions, that this problem arises in systems upgraded from an original Feisty installation. The fix was to change bind policy to soft and to manually configure the proper files using various sources on the web as a guide. Interesting, okay. So perhaps the 'fix' to this bug is to ensure that the upgrade process injects this 'soft bind' policy into the configuration files. Let me thinking abou that. The machines would hang to the point that they were only accessible by starting with a recovery kernel config. Please clarify... Would you be prompted with a login? Were you able to enter a username? And what about a password? Is that, then, the point at which your system 'hung'? If so, I am able to reproduce this behavior. But I'd call that a 'hang on login', which is different than a 'hang on boot'. :-Dustin ** Attachment added: unnamed http://launchpadlibrarian.net/13259217/unnamed -- ldap config causes Ubuntu to hang at a reboot https://bugs.launchpad.net/bugs/155947 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
