running installer twice simultaneously, 2nd copy explodes

[Ian Jackson]

Using kubuntu i386 livecd, I clicked on the Install icon twice (because of a short delay in responding the first time). I got one copy of the installer which seems to be displaying normally, and a second copy which is displaying `Step ${INDEX} of ${TOTAL}' and `textLabel2' and a stack trace window:

Traceback (most recent call last):
  File "/usr/bin/ubiquity", line 120, in ?
    install(sys.argv[1])
  File "/usr/bin/ubiquity", line 53, in install
    wizard = ui.Wizard(distro)
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 158, in __init__
    cloexec=True))
  File "/usr/lib/python2.4/site-packages/debconf.py", line 125, in __init__
    write=self.dccomm.tochild)
  File "/usr/lib/python2.4/site-packages/debconf.py", line 48, in __init__
    self.setUp(title)
  File "/usr/lib/python2.4/site-packages/debconf.py", line 51, in setUp
    self.version = self.version(2)
  File "/usr/lib/python2.4/site-packages/debconf.py", line 60, in <lambda>
    lambda *args, **kw: self.command(command, *args, **kw))
  File "/usr/lib/python2.4/site-packages/debconf.py", line 81, in command
    status = int(status)
ValueError: invalid literal for int():

[Colin Watson (cjwatson)]

There is a substantial number of other bugs that have at least been exacerbated by this, so I've put in some trivial pid file locking for my next upload. Thanks for your report; sorry I took so long to deal with it.

[Colin Watson (cjwatson)]

ubiquity (1.1.19) edgy; urgency=low

  * Reconfigure usplash (closes: Malone #59320).
  * Divert away update-initramfs while configuring hardware-specific
    packages, and run it just once at the end.
  * Display a warning if you try to mount a FAT or NTFS filesystem where
    POSIX semantics are required (closes: Malone #48410).
  * GTK frontend: Scroll the mount points table if required (closes: Malone
    #51796).
  * Ignore failures from os.utime on directories. I don't know why I get a
    disproportionate number of reports of this failing, but to be honest I
    don't care enough about directory timestamps to investigate.
  * Add trivial pid file locking, allowing ubiquity to exit gracefully if
    you try to run more than one instance of it at once; previously it blew
    up much more spectacularly upon finding that the debconf database was
    locked (closes: Malone #46569).
  * Run gnome-screensaver-command/xscreensaver-command with LC_ALL=C to
    reduce noise on stderr.
  * Automatic update of included source packages: console-setup 1.7ubuntu9,
    partman-auto 54ubuntu3, partman-basicfilesystems 47ubuntu2.

 -- Colin Watson <email address hidden> Sat, 16 Sep 2006 00:45:27 +0100