[Bug 322830] Re: remove /var/lib/dbus/machine-id from installed image

Colin Watson cjwatson at canonical.com
Thu Oct 13 08:22:29 UTC 2011


We decided not to make casper generate machine-id after all, because
nothing in casper should be relying on dbus being running.  Instead,
these fixes dealt with the fallout:

casper (1.287) oneiric; urgency=low

  * Remove typo from 26disable_user_menu that led the script to
    believe that indicator-session was never actually installed.

 -- Adam Conrad <adconrad at ubuntu.com>  Wed, 12 Oct 2011 14:00:48 +0100

casper (1.286) oneiric; urgency=low

  * Convert the gsettings calls to using the gsettings override files
    because we don't have DBUS in casper.

 -- Stéphane Graber <stgraber at ubuntu.com>  Wed, 12 Oct 2011 13:38:53
+0100

** Changed in: casper (Ubuntu)
       Status: In Progress => Fix Released

** Changed in: casper (Ubuntu)
     Assignee: Colin Watson (cjwatson) => (unassigned)

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

Title:
  remove /var/lib/dbus/machine-id from installed image

Status in Automated testing of Ubuntu ISO images:
  Fix Committed
Status in “casper” package in Ubuntu:
  Fix Released
Status in “dbus” package in Ubuntu:
  Incomplete
Status in “live-build” package in Ubuntu:
  Fix Released
Status in “livecd-rootfs” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: livecd-rootfs

  Havoc Pennington reported that /var/lib/dbus/machine-id needs to be
  unique across instances of the running live CD, and between installed
  systems. The simplest way to ensure this is to remove it from the live
  filesystem.

  We do have an upgrade problem, though; a number of people will have
  installed from previous versions of the live CD and will have
  duplicated machine-ids, although we can't feasibly identify the list
  of machine-ids involved (and it would be huge). I'm opening a task on
  dbus as well to figure out how to do something about it on upgrade.
  Maybe the answer is that everyone should have their machine-id
  forcibly regenerated on the first boot after upgrading to some
  nominated version of dbus?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-server-iso-testing/+bug/322830/+subscriptions




More information about the foundations-bugs mailing list