[Bug 843933] Re: Impossible to run ubuntu-bug when Ubiquity crashes

[Launchpad Bug Tracker]

This bug was fixed in the package ubiquity - 2.7.28

---------------
ubiquity (2.7.28) oneiric; urgency=low

  [ Stéphane Graber ]
  * Update stepUserInfo.ui to trigger info_loop() when the hostname is changed.
    (LP: #828181)

  [ Mario Limonciello ]
  * Reorder the imports in oem-config-remove-gtk to fix an import error due
    the fallbacks in aptdaemon. (LP: #837288)
  * Show the wireless page after either prepare or language to make sure
    it shows in both ubiquity and oem-config modes.
  * Call out to find_next_step even on non debconf driven pages. (LP: #843237)
  * Don't assume /target is where the new face is being put.
  * When the installer crashes, file a bug using apport-bug rather than
    directing users to a terminal window. (LP: #843933)
  * Fix the colors in the oem-config language selector. (LP: #838672)
  * Automatic update of included source packages: netcfg 1.68ubuntu2,
    user-setup 1.28ubuntu20.
 -- Mario Limonciello <Mario_Limonciello at Dell.com>   Wed, 07 Sep 2011 16:55:46 -0500

** Changed in: ubiquity (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
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/843933

Title:
  Impossible to run ubuntu-bug when Ubiquity crashes

Status in “ubiquity” package in Ubuntu:
  Fix Released

Bug description:
  When booting the system from a live CD/USB device and selecting the
  option to install Ubuntu (not to test drive before install), if
  Ubiquity crashes (like for me with bug #743359) a popup appears
  telling you to "file a new bug report using the command `ubuntu-bug
  ubiquity` in a terminal". However, it is not possible to open a
  terminal if you are directly installing, or at least I couldn't find a
  way to start a terminal. I had to restart the VM, and this time select
  the option to lauch Ubuntu to test it. From there I launched the
  install (which also failed). Then I was able to start a terminal and
  issue the command.

  Instead of telling the user to open a terminal, why not add a button
  on the error popup that would open a terminal with the needed command?
  Maybe it's even not necessary to launch a terminal, since the `ubuntu-
  bug` command opens its own popups telling the user that it's
  collecting information, etc. Not requiring the user to manually open
  the terminal would be a user-friendly improvement.

  FYI, I did try to use Ctrl Alt F2, F3, etc. to open a tty to run the
  `ubuntu-bug`command, but nothing happened. Maybe it's because it's in
  VMware? Anyway, I guess since `ubuntu-bug` then opens GTK popups, it
  would probably not work in a tty... Or maybe it would, but it's not
  really relevant to this bug report!

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