package squid3 3.3.8-1ubuntu6.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Scott Moore]

Bug ​#1370602 package squid3 3.3.8-1ubuntu6.1 failed to install/upgrade:..... is for version 3.3.8-1ubuntu6.1 and my version is 3.3.8-1ubuntu6.3. I'll let let triage determine if that makes this a duplicate of the aforementioned bug.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: squid3 3.3.8-1ubuntu6.3
ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.12
Architecture: amd64
Date: Thu Aug 20 18:35:59 2015
DuplicateSignature: package:squid3:3.3.8-1ubuntu6.3: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-08-10 (375 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.4
 apt 1.0.1ubuntu2.10
SourcePackage: squid3
Title: package squid3 3.3.8-1ubuntu6.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.squid3.squid.conf: 2015-05-03T00:44:54.751290

[Robie Basak (racb)]

From log:

FATAL: Bungled /etc/squid3/squid.conf line 753: acl aclname localport 3128 ... # TCP port the client connected to [fast]

[Robie Basak (racb)]

Thank you for your report.

This looks like a local configuration problem, rather than a bug in Ubuntu. Given that you modified /etc/squid3/squid.conf manually, my comments in bug 1370602 also apply to your case.

You can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Since we use this bug tracker to track bugs in Ubuntu, rather than configuration problems, I'm marking this bug as Invalid. This helps us to focus on fixing bugs in Ubuntu.

If you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.

[BCW142 (bcw142)]

I guess it depends on what you call a bug. All my Ubuntu & Lubuntu 14.04 LTS install have the error because it came from an update. I don't know what it really is, but the config makes since. The real issue is that it came in an update and I didn't write it or even install squid myself, it just showed up a few months back. Hopefully I'll fix it with the information here, I'm sure if I fix it in one system I can do so in all 6 that are doing this.

[Robie Basak (racb)]

If you can figure out how to get to this state from a fresh install, and you can do it without editing the configuration file manually, then it is probably a bug - please explain that, set the bug status back to New, and I'll take another look.