Ubuntu
squid package

package squid 2.7.STABLE7-1ubuntu12.2 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

Bug #729844 reported by François on 2011-03-05

This bug report is a duplicate of: Bug #729288: squid failed to restart after update to squid 2.7.STABLE7-1ubuntu12.2. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	squid (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: squid

this occurs during standard system update

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: squid 2.7.STABLE7-1ubuntu12.2
ProcVersionSignature: Ubuntu 2.6.32-29.58-generic 2.6.32.28+drm33.13
Uname: Linux 2.6.32-29-generic i686
NonfreeKernelModules: fglrx
Architecture: i386
Date: Sat Mar 5 19:31:24 2011
ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
SourcePackage: squid
Title: package squid 2.7.STABLE7-1ubuntu12.2 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

Tags:

Revision history for this message

François (fterrot) wrote on 2011-03-05:

AptOrdering.txt Edit (3.7 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.4 KiB, text/plain; charset="utf-8")
Df.txt Edit (853 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (43.7 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (26.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Robert Roth (evfool) wrote on 2011-03-08:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #729288, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.