OK. Now back to where I was pre 16.04.1 installs. For my Firewall/caching server, replaced a failing HDD and installed 16.04.1. All OK.
For my File server, that was an interesting exercise. Finally found the problem: there is a little parameter ( vt-handoff=7 ) on the grub file. Removing this during a boot, meant that boot went through to completion. At the moment the semi-permanent solution is to delete quiet splash from grub in order to stop the presence of vt-handoff. Will look at changing 10_linux script so that I can return to suppression of boot verbiage, without having the boot halting before boot completion. *Note:* most of the Internet hits about this problem where related to a desktop install and the need to do something with the nVidia drivers. Now I was able to check my File server backup files to see if it was me or Squid naming everything with "Squid3". I have the original Squid install conf file (pre 16.04.1); its definitely been Squid that named the various files with "Squid3" and not just "Squid" Ideally, Squid should have started with "Squid" as its file naming convention and then there would have been no problem. Since it didn't, I would have thought that the onus was on the install procedures to take into account, a change in the file naming convention. On 30 September 2016 at 20:42, ChristianEhrhardt <1625...@bugs.launchpad.net > wrote: > "I'm currently running in it in recovery mode" > > => Uh, good luck recovering! > > According to your former response I'll set the bug to incomplete for now. > If my suggestions won't help to fix the issue for you after recovering > please reopen and share a bit more about the config/setup that you use to > cause the issue. > > Given what you said (no "very" custom conf for squid used) I'd consider > purging the old package, removing all traces/dirs that you might have > made and install a fresh one. That works for me giving me a working > squid and I hope it does so for you as well. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1625569 > > Title: > package squid 3.5.12-1ubuntu7.2 failed to install%Fupgrade: subprocess > installed post-installation script returned error exit status 1 > > Status in squid3 package in Ubuntu: > Incomplete > > Bug description: > First-time user of this facility. I'm just following the instructions > generated by the do-release-upgrade process. > > ProblemType: Package > DistroRelease: Ubuntu 16.04 > Package: squid 3.5.12-1ubuntu7.2 > ProcVersionSignature: Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39 > Uname: Linux 3.13.0-95-generic i686 > ApportVersion: 2.14.1-0ubuntu3.21 > Architecture: i386 > Date: Tue Sep 20 22:25:53 2016 > DuplicateSignature: package:squid:3.5.12-1ubuntu7.2:subprocess > installed post-installation script returned error exit status 1 > ErrorMessage: subprocess installed post-installation script returned > error exit status 1 > InstallationDate: Installed on 2014-11-24 (666 days ago) > InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release > i386 (20140722.3) > RelatedPackageVersions: > dpkg 1.18.4ubuntu1.1 > apt 1.2.12~ubuntu16.04.1 > SourcePackage: squid3 > Title: package squid 3.5.12-1ubuntu7.2 failed to install/upgrade: > subprocess installed post-installation script returned error exit status 1 > UpgradeStatus: Upgraded to xenial on 2016-09-20 (0 days ago) > mtime.conffile..etc.squid.squid.conf: 2014-12-13T17:14:53.262193 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/ > 1625569/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625569 Title: package squid 3.5.12-1ubuntu7.2 failed to install%Fupgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1625569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
