package sun-java6-jre (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

Bug #463413 reported by Jeff Kelley
58
This bug affects 13 people
Affects Status Importance Assigned to Milestone
sun-java6 (Ubuntu)
New
Undecided
Unassigned

Bug Description

This is on the 64-bit version of Ubuntu 9.10 final running in a VirtualBox VM. The host is a Mac Pro running Mac OS X 10.6.1.

I attempted to install the "Ubuntu restricted extras" package and got this error.

ProblemType: Package
Architecture: amd64
Date: Thu Oct 29 11:51:51 2009
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess new pre-installation script returned error exit status 128
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Package: sun-java6-jre (not installed)
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: sun-java6
Title: package sun-java6-jre (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
Uname: Linux 2.6.31-14-generic x86_64

Revision history for this message
Jeff Kelley (slaunchaman) wrote :
Revision history for this message
David Finch (ubuntu-mytsoftware) wrote :

This seems like the same problem I had. I was installing "Ubuntu restricted extras" through "Ubuntu Software Center", and the installer stopped progressing at 54%, with zero indication as to what was going on. I ran "ps -A" and noticed there was a "preinst" process holding up the install. I was pretty sure it was waiting for user feedback, as a number of packages do ask for input, and the software center keeps it all hidden from you. I had no way to see it or respond.

It wasn't until much later, when I decided to restart the system, that I saw it flash another desktop I hadn't seen as it shut down, with a frameless window asking me to accept the Java EULA. It was too late then. It's like it created a new x11 desktop in the background under the root user and presented the EULA on that desktop, halting the installation.

On the next boot it reported the same error as is in the title, which eventually led me here, the closest of the similar bug reports.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.