viewing release notes pops up firefox warning

Bug #422254 reported by David Tombs
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: ubiquity

When installing Ubuntu 9.04 directly from the CD, and not from a live session (i.e., "Install Ubuntu"), I encounter a warning message when viewing release notes.

Clicking "Release Notes" in the setup wizard successfully launches firefox with the release notes page, but a warning dialog pops up with the following text:

"An error occurred while lading or saving configuration information for firefox. Some of your configuration settings may not work properly."

Clicking "Details" says "Failed to contact configuration server, some possible causes..." (I didn't write down the rest of the text, but can re-run installer if necessary.)

The problem is reproducible, so let me know if I can provide any more information. The syslog from the install is attached.

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
MediaBuild: Ubuntu 9.04 "Jaunty Jackalope" - Release amd64 (20090420.1)
Package: ubiquity 1.12.12
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
Uname: Linux 2.6.28-11-generic x86_64

Revision history for this message
David Tombs (dgtombs) wrote :
Revision history for this message
David Tombs (dgtombs) wrote :

The automatically-uploaded UbiquitySyslog.gz should be ignored; it's from a session in which I did not reproduce the bug.

Revision history for this message
MarcRandolph (mrand) wrote :

Howdy, and thank you for helping to improve Ubuntu by filing this report. I'm marking it confirmed since it appears to contain the necessary information for maintainers to get started on it. I am also marking it Low importance since, while annoying, it does not appear to cause any problems other than a tiny amount of confusion.

Note that I reconfirmed this still exists on the 15-Oct-2009 daily .iso build which contains ubiquity 2.0.

Changed in ubiquity (Ubuntu):
importance: Undecided → Low
status: New → Confirmed
Evan (ev)
Changed in ubiquity (Ubuntu):
importance: Low → Medium
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubiquity - 2.1.0

---------------
ubiquity (2.1.0) lucid; urgency=low

  [ Evan Dandrea ]
  * Run X with -nolisten tcp (LP: #462394).
  * Make sure we never try to install onto the live filesystem.
  * Only print the filenames being blacklisted if in debug mode.
  * Provide human readable sizes in the partitions-too-small warning
    (LP: #298974).
  * Mark the "Installation Complete" window as always on top
    (LP: #462178).
  * Fixes from Pychecker for the KDE frontend (kde_ui):
    - Don't import datetime or math. The timezone code is in a separate
      module now.
    - Remove some unused variables.
    - Don't assign to a variable that's going to be immediately discarded.
  * Signal to GTK+ when using a right-to-left language, so that it
    composes the interface from right to left (LP: #222845).
  * Signal to the slideshow when the installer is using a right-to-left
    language (LP: #446989).
  * Set SUDO_UID and SUDO_GID in ubiquity-dm so ubiquity knows what user
    to drop privileges to (LP: #422254).
  * Do not try to configure networking in oem-config (LP: #471498).
  * Make migration-assistant import failures non-fatal to the overall
    install.
  * pkgsel now provides a debconf question to avoid warning the end user
    when the language packs could not be installed (LP: #471553).
  * Make sure a device exists as part of the grub target device
    validation.
  * Allow the user to retry grub installation with a different device on
    failure.
  * Automatic update of included source packages: apt-setup
    1:0.42ubuntu1, choose-mirror 2.29ubuntu2, clock-setup 0.100ubuntu1,
    debian-installer-utils 1.71ubuntu1, grub-installer 1.47ubuntu1, hw-
    detect 1.73ubuntu1, netcfg 1.51ubuntu1, partman-base 135ubuntu1,
    tzsetup 1:0.26ubuntu1, user-setup 1.28ubuntu1.

  [ Colin Watson ]
  * Add a debian/rules target to run pychecker. I've fixed several warnings,
    but there are still several left so this is not yet enabled by default.
  * Fix debconf frontend:
    - Start oem-config on stopping rc, as well as when starting display
      managers.
    - Add some missing imports (ubiquity.frontend.base.Controller,
      ubiquity.plugin.Plugin, ubiquity.i18n, signal,
      ubiquity.components.install).
    - If there's a containing debconf frontend, talk to it rather than using
      debconf-communicator.
    - Set a controller in the language plugin.
    - Use spaces rather than ${!TAB} in localechooser when using the debconf
      frontend, since debconf doesn't support the latter yet.
    - Don't handle user-setup preseeding for the debconf frontend.
    - Remove unused progress_position handling.
    - Fix exception names in ubi-network and ubi-tasks.
  * Require Python 2.5, so we can now use hashlib rather than md5 and avoid
    a slew of warnings.
  * Add an intro message noting that we're alpha again.
 -- Evan Dandrea <email address hidden> Fri, 13 Nov 2009 10:41:42 +0000

Changed in ubiquity (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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