I am sure I had never touched my nfs-common prior to the bug showing up. I suspect that an upgrade has introduced code that is less tolerant of syntax than before.
On 06/01/16 11:55, jmartinz wrote: > I've been having the same error. > In my case statd.log gave this message: > /proc/self/fd/9: 6: /etc/default/nfs-common: no: not found > > Checking /etc/default/nfs-common there was this line > NEED_STATD= no > instead of > NEED_STATD=no > (note the space between = an no) and it was giving me that error. > > I am not aware of having changed nfs-common file configuration... > > Anyway, this bug has helped me to solve my problem. > thanks > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1523228 Title: package nfs-common 1:1.2.8-6ubuntu1.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1523228/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
