`debsums -c` returns the error of /sbin/start-stop-daemon

Bug #1978931 reported by Shih-Yuan Lee
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OEM Priority Project
Fix Committed
Critical
Shih-Yuan Lee
ubiquity (Ubuntu)
Fix Released
Undecided
Unassigned
Focal
New
Undecided
Unassigned
Jammy
Fix Released
Undecided
Steve Langasek

Bug Description

[Impact]

 * Affects Canonical OEM images for Dell on focal and jammy

[Test Plan]

 * Built Canonical OEM images for Dell on focal or jammy that includes the latest Ubiquity packages from *-proposed or *-updates.

 * Use the customized image to install Ubuntu system

 * Install debsums after the installation to check the system.

[Where problems could occur]

 * N/A

[Other Info]

 * I have built and included the customized Ubiquity packages that included the patch for focal and jammy so there should also be no problem after we finished the SRU updates.

[Original Bug Description]

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu
Description: Ubuntu 22.04 LTS
Release: 22.04

2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center
ubiquity 22.04.16

3) What you expected to happen
`debsums -c` returns no error.

4) What happened instead
`debsums -c` returns the error of /sbin/start-stop-daemon

We made the OEM jammy base image for Dell that contains dpkg 1.21.1ubuntu2 and then use dell-recovery (Ubiquity plugin) fish mechanism to install/upgrade dpkg 1.21.1ubuntu2.1.

Because Ubiquity will rename it to /sbin/start-stop-daemon.REAL and provide a fake /sbin/start-stop-daemon during the installation.
When installing newer dpkg, /sbin/start-stop-daemon will be replaced. However Ubiquity will rename /sbin/start-stop-daemon.REAL back to /sbin/start-stop-daemon after the installation.
So /sbin/start-stop-daemon will be kept as the older one.
That is why the issue happens.

Related branches

tags: added: oem-priority
Changed in oem-priority:
status: New → In Progress
importance: Undecided → Critical
assignee: nobody → Shih-Yuan Lee (fourdollars)
tags: added: originate-from-1978843 somerville
tags: added: originate-from-1978309
description: updated
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubiquity - 22.10.4

---------------
ubiquity (22.10.4) kinetic; urgency=medium

  [ Shih-Yuan Lee (FourDollars) ]
  * Use dpkg-divert /sbin/start-stop-daemon unconditionally instead of just renaming it conditionally. (LP: #1978931)

  [ Sebastien Bacher ]
  * plugin-viewer-gtk.py: specify the gtk version to use and fix a warning
  * 22.10.3 upload included: Update the ubiquity icons for the brand
    refresh. Thanks to the Yaru team.

  [ Dimitri John Ledkov ]
  * zsys-setup: increase minimum bpool partition size to 1792

 -- Dimitri John Ledkov <email address hidden> Fri, 01 Jul 2022 11:23:36 +0100

Changed in ubiquity (Ubuntu):
status: New → Fix Released
description: updated
description: updated
Revision history for this message
Steve Langasek (vorlon) wrote :

There will be no more point releases of focal, which means that this change is very low-risk with respect to focal. But in that case, is it necessary for this change to go in the archive, as opposed to in a Dell-specific archive, since there will also be no other ubiquity SRU changes in focal to worry about merging?

Steve Langasek (vorlon)
Changed in ubiquity (Ubuntu Jammy):
status: New → In Progress
assignee: nobody → Steve Langasek (vorlon)
Revision history for this message
Shih-Yuan Lee (fourdollars) wrote :

Could we still merge the change into focal and release it into Ubuntu archives? Although there is no point release for focal, will we stop the daily build for focal?

Revision history for this message
Steve Langasek (vorlon) wrote :

Yes, we have stopped daily builds for focal.

Revision history for this message
Shih-Yuan Lee (fourdollars) wrote :

There are some OEM images on focal for few platforms that we are still working on.
It is nice to have ubiquity updates on focal.

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

There is a ubiquity package in focal-proposed, version 20.04.15.20[1]:

ubiquity (20.04.15.20) focal; urgency=medium

  * Automatic update of included source packages: shim-signed 1.40.9.

 -- Graham Inggs <email address hidden> Tue, 14 Mar 2023 11:56:03 +0000

This change is not in the upstream focal branch for this project[2], where the latest version is:

ubiquity (20.04.15.19) focal; urgency=medium

  * Backport the ability to unhide passwords that are being typed-in during
    various stages of the installation (LP: #1960306).
  * Automatic update of included source packages: partman-auto
    134ubuntu13.1 (LP: #1959971).

 -- Łukasz 'sil2100' Zemczak <email address hidden> Tue, 08 Feb 2022 11:51:13 +0100

I'd rather not merge https://code.launchpad.net/~fourdollars/ubiquity/+git/ubiquity/+merge/426347 until that is sorted.

1. https://launchpad.net/ubuntu/+source/ubiquity/20.04.15.20
2. https://git.launchpad.net/ubiquity/tree/debian/changelog?h=focal

Revision history for this message
Robie Basak (racb) wrote : Please test proposed package

Hello Shih-Yuan, or anyone else affected,

Accepted ubiquity into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubiquity/22.04.20 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in ubiquity (Ubuntu Jammy):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-jammy
Revision history for this message
Julian Andres Klode (juliank) wrote :

I don't see anything to do here for sponsors, so I am unsubscribing sponsors. An upload has been uploaded for jammy and there's outstanding questions for focal that have not been addressed in this bug.

Changed in oem-priority:
status: In Progress → Fix Committed
Revision history for this message
Kai-Chuan Hsieh (kchsieh) wrote :

Install Dell oem image on Latitude 7330 Rugged Extreme with ubiquity 22.04.20.

After installation:
1. $ sudo apt update
2. $ sudo apt install debsums
3. $ sudo debsums -c

No `debsums -c` returns the error of /sbin/start-stop-daemon popped.

tags: added: verification-done verification-done-jammy
removed: verification-needed verification-needed-jammy
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubiquity - 22.04.20

---------------
ubiquity (22.04.20) jammy; urgency=medium

  [ Steve Langasek ]
  * Whenever removing packages, use apt-get autoremove --purge instead of
    apt-get purge so that no-longer-used dependencies are removed together
    with the package in question, and we do not leave behind any packages
    that will be reported as autoremovable later. LP: #1925265.
  * bin/oem-config-remove-gtk uses aptdaemon to remove packages, not
    apt-get. Set the flag to autoremove dependencies here as well.

  [ Nick Rosbrook ]
  * tests: modify test_city_entry to adapt to tzdata update (LP: #2022965)

  [ Shih-Yuan Lee (FourDollars) ]
  * Use dpkg-divert /sbin/start-stop-daemon unconditionally instead of just
    renaming it conditionally. (LP: #1978931)

 -- Steve Langasek <email address hidden> Mon, 05 Jun 2023 14:36:01 -0700

Changed in ubiquity (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Andreas Hasenack (ahasenack) wrote : Update Released

The verification of the Stable Release Update for ubiquity has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

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.