Comment 23 for bug 40464

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

OK, this upload should make sure that partman exits if ubiquity crashes rather than carrying on as if nothing had happened. My apologies for any inconvenience and/or data loss caused by this bug.

Even after this bug fix, it is likely that you will still see the installer crashing in similar ways; I have not fixed all the triggers for this bug, merely (I hope) the dangerous symptoms. Please send me reports of those crashes as *new* bug reports rather than appending them to this bug; please do not reopen this bug unless you experience a crash that leaves the partitioning scripts running on a live CD with at least version 0.99.64 of ubiquity installed. Doing that will help me to keep a handle on the set of bugs I currently need to fix.

ubiquity (0.99.64) dapper; urgency=low

  * GTK frontend:
    - Use xscreensaver-command --deactivate, not --disable (closes: Malone
      #40095).
    - Hide "Set Time..." button if time-admin isn't present.
    - Recommend gnome-system-tools for time-admin.
  * KDE frontend:
    - Fix import of UbiquityUIBase (closes: Malone #40939).
  * Set the SIGPIPE handler back to the default before spawning
    debconffiltered subprocesses, so that they notice when the UI crashes
    rather than carrying merrily on and e.g. trashing the partition table
    (closes: Malone #40464). Whose bright idea was it to have Python install
    a SIGPIPE handler but then not bother to have the subprocess module
    remove it, eh?

 -- Colin Watson <email address hidden> Sun, 23 Apr 2006 19:07:52 +0100