package libdb4.7-java-gcj 4.7.25-10ubuntu1 failed to install/upgrade: 子程序 新的 post-removal script 傳回了錯誤退出狀態 2

Bug #747493 reported by Carbo Kuo on 2011-04-01
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gcj-4.4 (Ubuntu)
Undecided
Unassigned

Bug Description

package libdb4.7-java-gcj 4.7.25-10ubuntu1 failed to install/upgrade: 的 post-removal script

i can not remove it.

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: libdb4.7-java-gcj 4.7.25-10ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Fri Apr 1 22:50:03 2011
ErrorMessage: 子程序 新的 post-removal script 傳回了錯誤退出狀態 2
InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
SourcePackage: db4.7
Title: package libdb4.7-java-gcj 4.7.25-10ubuntu1 failed to install/upgrade: 子程序 新的 post-removal script 傳回了錯誤退出狀態 2
UpgradeStatus: Upgraded to natty on 2011-04-01 (0 days ago)

Carbo Kuo (byvoid-kcp) wrote :
Thorsten Glaser (mirabilos) wrote :

gcj-dbtool-4.4 is terminated due to memory corruption (both bugs, this and LP #748903)

Thorsten Glaser (mirabilos) wrote :

I think this is somewhat related to Debian #569977 too.

Anyway, please follow the advice:

From: Clint Adams <email address hidden>

On Fri, Mar 12, 2010 at 12:02:53AM -0500, Gary Dale wrote:
> The gcj-dbtool-4.2 seems to be part of Lenny's gij-4.2 package. There is
> a similarly named package gcj-dbtool in Squeeze that is part of
> gcj-jre-headless & gcj-4.4-jre-headless. I'm guessing that somewhere in
> the updates from Lenny to Squeeze something got messed up. The question
> is, how do I fix it?

Oh, that's easy. Just rm gcj-dbtool-4.2. Alternately, if you
think it was part of the gij-4.2 package and somehow got left
behind you could install that package and remove it again.

affects: db4.7 (Ubuntu) → gcj-4.4 (Ubuntu)
Thorsten Glaser (mirabilos) wrote :

Since db just exhibits the bug by calling it, reassigning to gcj-4.4-jre-headless

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers