KDE installer error: RuntimeError: Install failed with exit code
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
In bug 49088, Matt Blissett wrote:
I have the same, the installer crashed whilst installing the bootloader, which hasn't installed correctly. Is this because GRUB doesn't work if /boot/grub/... can't be accessed by the BIOS? I.e. my / partition is 40GB after the start of the disk (Windows got there first). I've never had GRUB working in this situation, but Lilo does (I think all of LILO fits in the MBR?)
Traceback (most recent call last):
File "/usr/bin/
install(
File "/usr/bin/
ret = wizard.run()
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
raise RuntimeError, ("Install failed with exit code %s; see "
RuntimeError: Install failed with exit code 1; see /var/log/
http://
http://
http://
Changed in ubiquity: | |
importance: | Untriaged → Medium |
status: | Unconfirmed → Confirmed |
Thanks for your report. Due to some reliability problems with GRUB and XFS, you need to use a non-XFS root filesystem or create a non-XFS /boot filesystem. The fact that the partitioner doesn't warn you about this up-front is also bug 47848, and is fixed in dapper-updates.