> Does this mean there will be no fix? I and others did NOT change our configuration. It's that this new update is failing.
It seems more likely to me that some subset of users had some kind of local configuration problem that would have failed on _any_ update of openssh (ie. any run of the postinst maintainer script). If there really was a regression caused by the update, given the number of users of the ssh service out there I would expect to see a massive flood of regression reports, rather than just five, even though it has been weeks after the update came out. So, on balance, I still think these are local configuration problems - possibly different for each reporting user - and not a regression in the openssh package caused by the update. Or it could be a bug or number of bugs that only manifest in obscure situations. To make any progress with "fixing" this, developers need to see steps to reproduce. Otherwise there is no action that can be taken on this bug since there is not enough information here for developers to go on. If you don't understand why I'm saying this, it might be helpful for you to read "How to report bugs effectively" (http://www.chiark.greenend.org.uk/~sgtatham/bugs.html) which explains this situation well. I'm marking this bug back as Incomplete to make sure that users don't get the mistaken impression that developers could be working on this bug when they cannot. ** Changed in: openssh (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1486107 Title: package openssh-server 1:6.6p1-2ubuntu2.3 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/openssh/+bug/1486107/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
