[Bug 2090834] Re: vboxpostinstall.sh returned non-zero exit status 1.

Dan Bungert 2090834 at bugs.launchpad.net
Thu Dec 11 15:09:06 UTC 2025


** Project changed: subiquity => ubuntu

** Package changed: ubuntu => subiquity (Ubuntu)

** Changed in: subiquity (Ubuntu)
    Milestone: None => ubuntu-24.04.4

** Also affects: subiquity (Ubuntu Resolute)
   Importance: Undecided
       Status: Triaged

** Changed in: subiquity (Ubuntu Resolute)
    Milestone: ubuntu-24.04.4 => ubuntu-26.04

** Also affects: subiquity (Ubuntu Noble)
   Importance: Undecided
       Status: New

** Changed in: subiquity (Ubuntu Noble)
    Milestone: None => ubuntu-24.04.4

** Changed in: subiquity (Ubuntu Noble)
       Status: New => Triaged

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

Title:
  vboxpostinstall.sh returned non-zero exit status 1.

Status in ubuntu-desktop-provision:
  Triaged
Status in Virtualbox:
  Unknown
Status in subiquity package in Ubuntu:
  Triaged
Status in subiquity source package in Noble:
  Triaged
Status in subiquity source package in Resolute:
  Triaged

Bug description:
  We have multiple private bug reports where people try to install
  Ubuntu 24.04 using virtualbox but vboxpostinstall.sh fails.

  All these bugs have:

  * CasperMD5CheckResult: fail

  So they all ended up closed automatically. I created an exception so
  that such reports would not automatically get closed if they also
  have:

  * CasperMD5CheckMismatches: ./boot/grub/grub.cfg

  After investigating, I found out that vboxpostinstall.sh indirectly
  relies on usermod to add the `vboxuser` user to a group (vboxuser is
  the default name for VirtualBox unattended installations but can be
  changed by when creating the VM).

  We know for a fact that Subiquity-based installers do not create users
  until first boot so using usermod in a postinstall scripts doesn't
  work.

  Note that one cannot reproduce this issue with an Ubuntu Host OS at
  the moment. The virtualbox package in Ubuntu does not have the
  autoinstall support ; so when selecting unattended installation, there
  is no automation at all. Autoinstall support is new in VirtualBox 7.1.

  Workaround:
  https://bugs.launchpad.net/subiquity/+bug/2090834/comments/7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-desktop-provision/+bug/2090834/+subscriptions




More information about the foundations-bugs mailing list