[Bug 2016285] Re: Redundant creation of oem user in rpi desktop images

Launchpad Bug Tracker 2016285 at bugs.launchpad.net
Fri Apr 14 16:49:16 UTC 2023


This bug was fixed in the package ubuntu-settings - 23.04.5

---------------
ubuntu-settings (23.04.5) lunar; urgency=medium

  * ubuntu-raspi-settings-desktop: Don't attempt to prepare oem-config in
    postinst; there's no guarantee oem-config is installed yet and it cannot
    be a dependency as it's uninstalled after first boot (LP: #2016285)
  * ubuntu-raspi-settings-desktop: Don't attempt to expand an already expanded
    rootfs (LP: #2016286)

 -- Dave Jones <dave.jones at canonical.com>  Fri, 14 Apr 2023 11:13:13
+0100

** Changed in: ubuntu-settings (Ubuntu)
       Status: New => Fix Released

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

Title:
  Redundant creation of oem user in rpi desktop images

Status in livecd-rootfs package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  There are two (semi-related) issues which are currently preventing the
  creation of Ubuntu desktop images for the Raspberry Pi:

  The first is that livecd-rootfs is erroneously trying to create the
  oem user (and run oem-config-prepare) twice in live-
  build/ubuntu/hooks/099-ubuntu-image-customization.chroot.

  The second is that the ubuntu-raspi-settings-desktop package is
  attempt to create the oem user and run oem-config-prepare in its
  postinst. This is the wrong place to accomplish this as there's no
  guarantee that oem-config-prepare is installed at the time that
  ubuntu-raspi-settings-desktop is installed. It cannot be a dependency
  because oem-config is uninstalled after first boot.

  It's likely that the *correct* place to do this configuration is in
  neither of these places, but in oem-config's postinst (along with some
  check that it's being installed in an image that's never been booted,
  e.g. check for the existence of some sentinel created on first boot
  ... maybe /var/log/boot.log or something). Still, that fix can wait
  until it's not release week!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2016285/+subscriptions




More information about the foundations-bugs mailing list