Xubuntu installer

Bug #73825 reported by metaeoc
2
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

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 385, in run
    self.configure_bootloader()
  File "/usr/share/ubiquity/install.py", line 1163, in configure_bootloader
    raise InstallStepError(
InstallStepError: GrubInstaller failed with code 1

Tags: grub nospace
Revision history for this message
metaeoc (metaeoc) wrote :
Revision history for this message
metaeoc (metaeoc) wrote :
Jeff Greene (jeffgreene)
Changed in ubiquity:
status: Unconfirmed → Confirmed
Revision history for this message
Jeff Greene (jeffgreene) wrote :

I believe the cause of this error is that there was no space left on the device.

Revision history for this message
Jeff Greene (jeffgreene) wrote :

Nov 29 13:17:33 ubuntu grub-installer: info: Running chroot /target /sbin/grub-install --no-floppy "(hd0)"
Nov 29 13:17:33 ubuntu grub-installer: mkdir: cannot create directory `/boot/grub': No space left on device
Nov 29 13:17:33 ubuntu grub-installer: error: Running 'grub-install --no-floppy "(hd0)"' failed.

Revision history for this message
MillenniumBug (millenniumbug) wrote :

This bug report is several years old and concerns obsolete versions of Ubuntu. It has now been marked 'invalid'.

If the bug still appears in Ubuntu 10.10, feel free to open a new report.

Changed in ubiquity (Ubuntu):
status: Confirmed → 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.