Ubuntu
debconf package

Can't launch ubiquity on 20070117 feisty-desktop-i386.iso

Bug #80253 reported by Patrice Vetsel
46
Affects Status Importance Assigned to Milestone
debconf (Ubuntu)
Fix Released
Undecided
Colin Watson

Bug Description

Binary package hint: ubiquity

ubiquity 1.3.12 don't launch.
Messages in terminal :
...
File "/usr/lib/ubiquity/ubiquity/debconfcommunicator.py", line 22, in <module>
  import debconf
ImportError: No module named debconf

Revision history for this message
Colin Watson (cjwatson) wrote :

debconf needs a python2.5 module.

Changed in ubiquity:
status: Unconfirmed → Confirmed
Revision history for this message
Colin Watson (cjwatson) wrote :

It's a shame to have to branch debconf again just as we'd got it into sync with Debian at last, but this should only be temporary.

debconf (1.5.11ubuntu1) feisty; urgency=low

  * Install Python confmodule for python2.5 as well (LP: #80253).

 -- Colin Watson <email address hidden> Wed, 17 Jan 2007 14:32:59 +0000

Changed in debconf:
assignee: nobody → kamion
status: Confirmed → Fix Released
Revision history for this message
Peter Whittaker (pwwnow) wrote :

Confirming that 20070118 daily live installs without error.

Only remaining problems appear to be the garbled screen after step 4 (bug 74875# ), the fact that it is dog slow (took 15+ minutes to walk through the installer, Herd1 was much faster - no bug report, hard to quantify), and the presence of crash report on th CD (bug #80589)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.