The lock file did exist. I ran cp /etc/gshadow ~/ rm /etc/gshadow* apt-get install -f
This fixed the problem Thanks for responding so quickly On Wed, May 25, 2011 at 7:38 PM, Adam Gandelman <788...@bugs.launchpad.net>wrote: > Hi Mike-- > > Thanks for taking the time to report this bug. Does /etc/gshadow.lock > exist? If so, does renaming/removing the *.lock file resolve the issue? > This is probably similar to bug #432964. Its possible another process > that created the lock aborted abnormally before cleaning up after > itself. > > -- > You received this bug notification because you are a direct subscriber > of the bug. > https://bugs.launchpad.net/bugs/788419 > > Title: > package openssh-server 1:5.8p1-1ubuntu3 failed to install/upgrade: > subprocess installed post-installation script returned error exit > status 1 useradd: cannot lock /etc/gshadow; try again later > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/788419/+subscribe > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/788419 Title: package openssh-server 1:5.8p1-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 useradd: cannot lock /etc/gshadow; try again later -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
