Installer crash when moving to partitioning

Bug #79080 reported by cstrippie
2
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: ubiquity

Installer had just finished language selection, etc. I had empty space ready and was going to manually partition, but the installer hung for a very long time and then came back with a crash report. At no time did the normal autopart/manual part menu come up.

System is a Dell 1705 laptop (Core 2 Duo) and was booted to Feisty Herd 2 live CD at the time. No other applications running.

Report:

Traceback (most recent call last):
  File "/usr/lib/ubiquity/bin/ubiquity", line 185, in ?
    main()
  File "/usr/lib/ubiquity/bin/ubiquity", line 180, in main
    install(args[0])
  File "/usr/lib/ubiquity/bin/ubiquity", line 56, in install
    ret = wizard.run()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtkui.py", line 310, in run
    self.process_step()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtkui.py", line 867, in process_step
    self.process_autopartitioning()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtkui.py", line 922, in process_autopartitioning
    choice = self.get_autopartition_choice()[0]
  File "/usr/lib/ubiquity/ubiquity/frontend/gtkui.py", line 1620, in get_autopartition_choice
    raise AssertionError, "no active autopartitioning choice"
AssertionError: no active autopartitioning choice

*NOTE*

The bug report asks that I attach syslog & partman, but I see no way to do so.

Revision history for this message
cstrippie (ctfreedom) wrote :

Ok, now I see how to attach.

Revision history for this message
cstrippie (ctfreedom) wrote :

Attaching log from partman

Revision history for this message
Dennis Polling (dpolling) wrote :

I have the exact same problem on my Dell Inspiron 8600 (Pentium M). This is on a dual-boot Windows XP (NTFS) / Dapper (EXT3) system.

Changed in ubiquity:
status: Unconfirmed → Confirmed
Revision history for this message
Luka Renko (lure) wrote :

Thanks for report. This bug was reported by multiple users, therefore closing is as duplicate.

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.