Ubiquity crashes with XFS and GRUB

Bug #53205 reported by abattoir
0
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
New
Undecided
Unassigned

Bug Description

Ubiquity crashes with the following Traceback:
****************************************
Traceback (most recent call last):
  File "/usr/bin/ubiquity", line 130, in ?
    install(sys.argv[1])
  File "/usr/bin/ubiquity", line 55, in install
    ret = wizard.run()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 311, in run
    self.process_step()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 734, in process_step
    self.mountpoints_to_summary()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 1047, in mountpoints_to_summary
    self.progress_loop()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 524, in progress_loop
    raise RuntimeError, ("Install failed with exit code %s; see "
RuntimeError: Install failed with exit code 1; see /var/log/installer/syslog and /var/log/syslog
********************************************
On checking /var/log/installer, i think it is grub-installer which causes it to crash. I know that the Grub and XFS combination has issues, but the 8th comment in https://launchpad.net/distros/ubuntu/+source/lilo/+bug/13851 seems to suggest that the version of grub included with dapper should not face a problem in coexisting with XFS. Also, i thought Ubiquity would in that case install LILO instead of Grub.

Revision history for this message
abattoir (abattoir) wrote :

/var/log/installer/syslog attachment.

Revision history for this message
abattoir (abattoir) wrote :

/var/log/syslog
(Launchpad doesnt seem to like multiple attachments to the same comment)

Revision history for this message
abattoir (abattoir) wrote :

/var/log/partman

Revision history for this message
abattoir (abattoir) wrote :

/var/log/partman

Revision history for this message
William Grant (wgrant) wrote :

Thanks for the bug report. This particular issue has already been reported in bug #47848.

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.