[Bug 985919] Re: ubi-partman crash when network is disable

[Stéphane Graber]

Can you easily reproduce this issue?

I had a quick try with a similar setup using an Ubuntu build and can't
seem to reproduce the crash.

Looking at the traceback, I don't see how it could be related to network
state. But it may be some kind of race condition in ubiquity or a
translation-related issue.

Anyway, marking Incomplete for now, if you can reliably reproduce this
issue, I'll give it another try on Lubuntu with the exact same choices
tomorrow to try and find what's broken.

** Changed in: ubiquity (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/985919

Title:
  ubi-partman crash when network is disable

Status in “ubiquity” package in Ubuntu:
  Incomplete

Bug description:
  Using Lubuntu ISO amd64 (20120419), on virtualbox.

  When there is no network available (no network card or disable by
  network-manager applet), ubiquity crashed with an error on ubi-
  partman. I attached /var/log/syslog, as requested by the error
  message.

  Error message : ubi-partman failed with exit code 141. Further
  information may be found in /var/log/syslog.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: ubiquity 2.10.15
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: amd64
  CasperVersion: 1.315
  Date: Thu Apr 19 21:38:07 2012
  InstallCmdLine: file=/cdrom/preseed/lubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=fr keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss
  LiveMediaBuild: Lubuntu 12.04 "Precise Pangolin" - Beta amd64 (20120419)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/985919/+subscriptions