Ubuntu
tor package

package tor 0.2.2.35-1 failed to install/upgrade: underprocessen installerade post-installation-skript gav felkod 1

Bug #965538 reported by Lucas on 2012-03-26

This bug report is a duplicate of: Bug #828504: package tor 0.2.1.30-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1. Edit Remove

This bug affects 1 person

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

Bug Description

Don't know actually

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: tor 0.2.2.35-1
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.95-0ubuntu1
AptOrdering:
opera: Purge
tor: Configure
tor-geoipdb: Configure
vidalia: Configure
Architecture: amd64
Date: Mon Mar 26 19:32:07 2012
ErrorMessage: underprocessen installerade post-installation-skript gav felkod 1
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: tor
Title: package tor 0.2.2.35-1 failed to install/upgrade: underprocessen installerade post-installation-skript gav felkod 1
UpgradeStatus: Upgraded to precise on 2012-02-20 (34 days ago)

Tags:

Revision history for this message

Lucas (lucasrabnor) wrote on 2012-03-26:

Dependencies.txt Edit (717 bytes, text/plain; charset="utf-8")
Df.txt Edit (463 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (61.4 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (53.0 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (2.9 KiB, text/plain; charset="utf-8")

Revision history for this message

papukaija (papukaija) wrote on 2013-04-11:

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 828504, 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.