Ubuntu
apport package

package apport-gtk 1.20.1-0ubuntu3 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato

Bug #767650 reported by Luke12 on 2011-04-20

This bug report is a duplicate of: Bug #767498: package apport 1.20.1-0ubuntu3 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
	apport (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: apport

Updating as of today 20 April, 22:23 Greenwhich+1

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: apport-gtk 1.20.1-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: fglrx wl
Architecture: amd64
Date: Wed Apr 20 22:21:57 2011
ErrorMessage: problemi con le dipendenze - lasciato non configurato
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
PackageArchitecture: all
SourcePackage: apport
Title: package apport-gtk 1.20.1-0ubuntu3 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato
UpgradeStatus: Upgraded to natty on 2011-03-23 (28 days ago)

Tags:

Revision history for this message

Luke12 (luca-venturini) wrote on 2011-04-20:

ApportLog.txt Edit (1.8 KiB, text/plain; charset="utf-8")
AptOrdering.txt Edit (2.1 KiB, text/plain; charset="utf-8")
CrashReports.txt Edit (1.8 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (4.6 KiB, text/plain; charset="utf-8")
Df.txt Edit (448 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (251.7 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (12.6 KiB, text/plain; charset="utf-8")

Revision history for this message

Joshua Lückers (joshualuckers) wrote on 2011-04-20:

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 #767498, 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.