installer crashed

Bug #78938 reported by kilonux
This bug report is a duplicate of:  Bug #77199: installer crashed. Edit Remove
4
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: ubiquity

We're sorry; the installer crashed. Please file a new bug report at https://launchpad.net/distros/ubuntu/+source/ubiquity/+filebug (do not attach your details to any existing bug) and a developer will attend to the problem as soon as possible. To help the developers understand what went wrong, include the following detail in your bug report, and attach the files /var/log/syslog and /var/log/partman:

Traceback (most recent call last):
  File "/usr/bin/ubiquity", line 166, in ?
    main()
  File "/usr/bin/ubiquity", line 161, in main
    install(sys.argv[1])
  File "/usr/bin/ubiquity", line 57, in install
    ret = wizard.run()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtkui.py", line 305, in run
    self.process_step()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtkui.py", line 856, in process_step
    self.progress_loop()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtkui.py", line 628, in progress_loop
    raise RuntimeError, ("Install failed with exit code %s\n%s" %
RuntimeError: Install failed with exit code 1
Traceback (most recent call last):
  File "/usr/share/ubiquity/install.py", line 1404, in ?
    install.run()
  File "/usr/share/ubiquity/install.py", line 366, in run
    self.configure_timezone()
  File "/usr/share/ubiquity/install.py", line 871, in configure_timezone
    raise InstallStepError("TimezoneApply failed with code %d" % ret)
InstallStepError: TimezoneApply failed with code 1

kilonux (frode-laposte)
description: updated
Revision history for this message
kilonux (frode-laposte) wrote :

This is my second try.
First time it crashed earlier durring the install process , I lost the error report, but I'm sure it was not the same error.

This time it was almost at the end, what a pity.
I've got an asus laptop L8400 / 256 M ram.
I'm now writing to you using the xubuntu edgy eft bootable CD
I'll now try to fish up syslog and partman files, I'm new to LInux, so we'll see....

Revision history for this message
kilonux (frode-laposte) wrote :
Revision history for this message
Paul Dufresne (paulduf) wrote :

Hi, I am NOT Ubiquity developper, but reading your Syslog file I see two things worth to say.

There seems to have been a missing place on /var partition not long before the error:
ubiquity: Paramétrage de wamerican (6-2) ...
Jan 12 14:11:20 ubuntu ubiquity: debconf: DbDriver "templatedb": could not write /var/cache/debconf/templates.dat-new: Aucun espace disponible sur le périphérique
Jan 12 14:11:22 ubuntu ubiquity: dpkg : erreur de traitement de wamerican (--configure) :
Jan 12 14:11:22 ubuntu ubiquity: le sous-processus post-installation script a retourné une erreur de sortie d'état 1

I also see some error on the CDRom, before previous:
an 12 11:54:41 ubuntu kernel: [17179583.536000] hdb: media error (bad sector): status=0x51 { DriveReady SeekComplete Error }
Jan 12 11:54:41 ubuntu kernel: [17179583.536000] hdb: media error (bad sector): error=0x34 { AbortedCommand LastFailedSense=0x03 }
Jan 12 11:54:41 ubuntu kernel: [17179583.536000] ide: failed opcode was: unknown
  [repeated about 8 times on different sectors]

So two things come to my mind:
1) Test the CD (suppose to be an option for thin in the menu
when booting with the CD)
2) Mabe making sure /var partition have a bit more place?

Revision history for this message
kilonux (frode-laposte) wrote : Re:[Bug 78938] Re: installer crashed

THANKS A LOT
I'm still on the live cd
I tried twice again (before getting your mail) and I came some
further. but the install crashed loading GRUB. And worst of
all: The grub freezes (it went like this since the first
xubuntu install try). there is just this GRUB and a blinking
underline after it. escape doesn't work. There was a RedHat on
this partition before, and the old grub did very fine the dual
winXP/ redhat boot.
I don't know anything about all this, I'm very happy if you
could help.
The priority now is to make it boot on windows (sorry to say),
I've got everything there. I don't manage to get gmail working
for irc, I don't know it.

> Hi, I am NOT Ubiquity developper, but reading your Syslog
file I see two
> things worth to say.
>
> There seems to have been a missing place on /var partition
not long before the error:
> ubiquity: Paramétrage de wamerican (6-2) ...
> Jan 12 14:11:20 ubuntu ubiquity: debconf: DbDriver
"templatedb": could not write
/var/cache/debconf/templates.dat-new: Aucun espace disponible
sur le périphérique
> Jan 12 14:11:22 ubuntu ubiquity: dpkg : erreur de
traitement de wamerican (--configure)Â :
> Jan 12 14:11:22 ubuntu ubiquity: le sous-processus
post-installation script a retourné une erreur de sortie
d'état 1
>
> I also see some error on the CDRom, before previous:
> an 12 11:54:41 ubuntu kernel: [17179583.536000] hdb: media
error (bad sector): status=0x51 { DriveReady SeekComplete Error }
> Jan 12 11:54:41 ubuntu kernel: [17179583.536000] hdb: media
error (bad sector): error=0x34 { AbortedCommand
LastFailedSense=0x03 }
> Jan 12 11:54:41 ubuntu kernel: [17179583.536000] ide: failed
opcode was: unknown
> [repeated about 8 times on different sectors]
>
> So two things come to my mind:
> 1) Test the CD (suppose to be an option for thin in the menu
> when booting with the CD)
> 2) Mabe making sure /var partition have a bit more place?
>
> --
> installer crashed
> https://launchpad.net/bugs/78938
>

Envoyez vos cartes de voeux depuis www.laposte.net
Elles seront ensuite distribuées par le facteur : pratique et malin !

Revision history for this message
kilonux (frode-laposte) wrote :

back on windows after repairing the mbr

thanks for all interest
kilonux

Revision history for this message
Parthan SR (parth-technofreak) wrote :

Marking this bug as invalid as there seems to be no activity for long. Please feel free to reopen this bug if it can be reproduced for Ubuntu Hardy 8.04.

Changed in ubiquity:
status: New → Invalid
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.