Kubuntu 6.06 Installation Crashes on AMD64

Bug #58438 reported by duckdown
4
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Quite simply, I received free Kubuntu & Ubuntu 64-bit versions for free in the mail on CD (I was thrilled), however, installation is a complete nightmare and fails early into the process once the copying of files is complete.

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

That is the output and the reason for crashing apparently

It is an AMD64 3500+ 2.2GHZ S939
Abit AN8-Ultra nForce4 Motherboard
3D Fuzion (By BFG) 7300LE PCI-Express VideoCard
512mb DDR400 Crucial RAM

Please let me know how this turns out

Revision history for this message
Vassilis Pandis (pandisv) wrote :

Could you please attach /var/log/installer/syslog, /var/log/syslog, and /var/log/partman to this bug, by commenting on the bug's web page? Thanks in advance.

Changed in ubiquity:
importance: Untriaged → Medium
status: Unconfirmed → Needs Info
Revision history for this message
duckdown (liquidhex) wrote :

Hi

So I tried to re-install again (since I shutdown after yesterdays fiasco) and it has happened again... I watched it closely this time.

It finishes copying the files, and finishes scanning the mirrors, and loading modules, it fails at the 96% "Configuring boot loader...' stage.

Once again the trace output that its asked me to report is:

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

I will attatch the files you requested, however I am only allowed to attatch one attatchment a time for some reason.

Here is /var/log/installer/syslog

Revision history for this message
duckdown (liquidhex) wrote :
Revision history for this message
duckdown (liquidhex) wrote :
Changed in ubiquity:
status: Needs Info → Confirmed
Revision history for this message
Colin Watson (cjwatson) wrote :

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.

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.