ubuntu-gnome 14.10 rc fails to install with a user-setup postrm failure

Bug #1384654 reported by Marius Gedminas
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I dd'ed today's ubuntu-gnome desktop ISO for i386 to a USB key, booted it on an Asus EeePC 900, tried the LiveCD session, launched the installer, installed Ubuntu onto my hard disk.

The installation failed with the user-setup postrm script exitting with status 12.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: ubiquity 2.20.0
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic i686
ApportVersion: 2.14.7-0ubuntu8
Architecture: i386
CasperVersion: 1.345
Date: Thu Oct 23 12:47:39 2014
InstallCmdLine: file=/cdrom/preseed/ubuntu-gnome.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
LiveMediaBuild: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release i386 (20141022.1)
ProcEnviron:
 PATH=(custom, no user)
 LANG=lt_LT.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Marius Gedminas (mgedmin) wrote :
Revision history for this message
Marius Gedminas (mgedmin) wrote :

The relevant bits appear to be

    Oct 23 08:26:58 ubuntu-gnome ubiquity: Purging configuration files for user-setup (1.48ubuntu3) ...
    Oct 23 08:27:12 ubuntu-gnome ubiquity: open2: fork failed: Nepavyko išskirti atminties at /usr/share/perl5/Debconf/ConfModule.pm line 59.
    Oct 23 08:27:12 ubuntu-gnome ubiquity: dpkg: error processing package user-setup (--purge):
    Oct 23 08:27:12 ubuntu-gnome ubiquity: subprocess installed post-removal script returned error exit status 12

This laptop has 1 gigabyte of RAM. Ubuntu GNOME's release notes say the minimum is 1.5 GB. That might be it.

(It also has a broken 4 GB internal SSD, which explains all those /dev/sda errors. I was installing into the 16 GB /dev/sdb.)

Revision history for this message
Marius Gedminas (mgedmin) wrote :

FWIW the system doesn't boot from the hard disk. Gets stuck somewhere in boot stage, with a pretty splash screen, but never progresses: https://twitter.com/mgedmin/status/525234926749487104

The fix is to boot in rescue mode, remount / as writable, and

    mv /sbin/initctl.REAL /sbin/initctl
    mv /sbin/start-stop-daemon.REAL /sbin/start-stop-daemon
    sync

Then reboot again and run

    sudo apt-get install -f

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote : Hardware Error

Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your log files attached to this bug report it seems that there is a problem with the disk to which you are trying to install Ubuntu. I'd recommend performing a back up of your existing operating system and then investigating the situation. Measures you might take include checking cable connections for your disks and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck!

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: hardware-error
Changed in ubiquity (Ubuntu):
status: New → Invalid
Revision history for this message
Marius Gedminas (mgedmin) wrote :

Hello, bot.

The disk died a long time ago because this is a crappy cheap slow SSD with horrible write leveling that did not like the ext3 journal. That's why I reinstalled Ubuntu onto the *other* disk. (I should find a screwdriver and remove the broken SSD, but I'm lazy.)

I don't mind the bug being closed as Invalid, since 1 GB of RAM this machine had is less than the required minimum for Ubuntu GNOME.

tags: removed: hardware-error
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.