Installer Crash

[Ron]

Binary package hint: ubiquity

Traceback (most recent call last):
  File "/usr/lib/ubiquity/bin/ubiquity", line 212, in <module>
    main()
  File "/usr/lib/ubiquity/bin/ubiquity", line 207, in main
    install(args[0])
  File "/usr/lib/ubiquity/bin/ubiquity", line 65, in install
    ret = wizard.run()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py", line 425, in run
    self.progress_loop()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py", line 776, in progress_loop
    (ret, realtb))
RuntimeError: Install failed with exit code 1
Traceback (most recent call last):
  File "/usr/share/ubiquity/install.py", line 1768, in <module>
    install.run()
  File "/usr/share/ubiquity/install.py", line 347, in run
    self.configure_user()
  File "/usr/share/ubiquity/install.py", line 998, in configure_user
    raise InstallStepError("UserSetupApply failed with code %d" % ret)
InstallStepError: UserSetupApply failed with code 127

[Colin Watson (cjwatson)]

Firstly, please report gOS bugs to whoever makes that, not to us. (I know they probably forgot to change the text that tells you to report installer bugs here, but I can't really help that ...)

Here's the immediate cause of this:

Sep 7 18:42:42 gOS-Live user-setup: gconftool-2: error while loading shared libraries: /usr/lib/libgobject-2.0.so.0: invalid ELF header

That file can't really be broken on the CD, otherwise the installer itself would never have managed to start up. That means it must have been broken in the process of copying it from the CD to your hard disk. (Newer versions of Ubiquity make more of an effort to detect this situation.) Further investigation reveals these log messages about your hard disk:

Sep 7 14:29:15 gOS-Live kernel: [ 58.192930] hdb:hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Sep 7 14:29:15 gOS-Live kernel: [ 58.198543] hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Sep 7 14:29:15 gOS-Live kernel: [ 58.198545] ide: failed opcode was: unknown
Sep 7 14:29:15 gOS-Live kernel: [ 58.198945] hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Sep 7 14:29:15 gOS-Live kernel: [ 58.198948] hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Sep 7 14:29:15 gOS-Live kernel: [ 58.198950] ide: failed opcode was: unknown
Sep 7 14:29:15 gOS-Live kernel: [ 58.200024] hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Sep 7 14:29:15 gOS-Live kernel: [ 58.200027] hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Sep 7 14:29:15 gOS-Live kernel: [ 58.200029] ide: failed opcode was: unknown
Sep 7 14:29:15 gOS-Live kernel: [ 58.200269] hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Sep 7 14:29:15 gOS-Live kernel: [ 58.200272] hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
Sep 7 14:29:15 gOS-Live kernel: [ 58.200274] ide: failed opcode was: unknown
Sep 7 14:29:15 gOS-Live kernel: [ 58.244919] ide0: reset: master: error (0x7f?)

So either the kernel's driver for your hard disk is broken, or your hard disk is faulty. It may help to check whether the hard disk is old and in need of replacement, or to move the system to a cooler environment.