** Description changed: + [ Impact ] - [ Impact ] - - * The version of rtkit in Noble is 0.13-5build1. Users who have this package may not be able - to complete an upgrade from Noble to Resolute, as the new version of rtkit (0.14-1) can - fail to install. This is due to the rtkit update being attempted before a newer systemd - version is installed, which provides a newer systemd-sysusers that rtkit 0.14-1 needs. - * rtkit 0.14-1 installs a sysusers.d file using the u! modifier, which is only supported by - systemd-sysusers starting with systemd 257 (Noble ships 255). - * The fix adds a versioned dependency on systemd (>= 257~) so that the required systemd - implementation is installed before rtkit is configured. - + * The version of rtkit in Noble is 0.13-5build1. Users who have this package may not be able + to complete an upgrade from Noble to Resolute, as the new version of rtkit (0.14-1) can + fail to install. This is due to the rtkit update being attempted before a newer systemd + version is installed, which provides a newer systemd-sysusers that rtkit 0.14-1 needs. + * rtkit 0.14-1 installs a sysusers.d file using the u! modifier, which is only supported by + systemd-sysusers starting with systemd 257 (Noble ships 255). + * The fix adds a versioned dependency on systemd (>= 257~) so that the required systemd + implementation is installed before rtkit is configured. [ Test Plan ] - - * Note: while testing this bug, I was not able to reproduce the bug during a normal - "do-release-upgrade", so the steps described below involve using dpkg directly. If a package - set is found that reproduces the bug, then testing with an upgrade would be preferable. - * To reproduce, download the Resolute rtkit .deb (can be found here: - https://packages.ubuntu.com/resolute/rtkit). - Start up a Noble container or vm and copy in the Resolute .deb. For example, in lxc: - -lxc file push rtkit_0.14-1_amd64.deb <container>/root/ - Then, in the container, update the system and install rtkit (this will be the Noble version): - -apt update && apt dist-upgrade -y && apt install -y rtkit - Once this finishes, attempt to install the Resolute version of rtkit: - -dpkg --force-depends -i rtkit_0.14-1_amd64.deb - This should fail with the same postint error that was seen in the original bug: - -/usr/lib/sysusers.d/rtkit.conf:1: Unknown modifier 'u!'. - -dpkg: error processing package rtkit (--install): - - installed rtkit package post-installation script subprocess returned error exit status 1 - * To verify the fix, first download the updated .deb (should be version 0.14-1ubuntu0.1). - Copy the new .deb into the container, as before: - -lxc file push rtkit_0.14-1ubuntu0.1_amd64.deb <container>/root/ - Next, attempt to install this version: - -dpkg -i rtkit_0.14-1ubuntu0.1_amd64.deb - This should fail when attempting to unpack, before making it to setup: - -dpkg: dependency problems prevent configuration of rtkit: - - rtkit depends on systemd-sysusers (>= 257~); however: - - Package systemd-sysusers is not installed. - - Version of systemd-sysusers on system, provided by systemd:amd64, is 255.4-1ubuntu8.17 - With the fix applied, rtkit requires that systemd be updated before it will attempt to install. - During an upgrade, this would ensure that the "u!" modifier would be accepted as valid syntax, - preventing the update failure. - - + + * Note: while testing this bug, I was not able to reproduce the bug during a normal + "do-release-upgrade", so the steps described below involve using dpkg directly. If a package + set is found that reproduces the bug, then testing with an upgrade would be preferable. + * To reproduce, download the Resolute rtkit .deb (can be found here: + https://packages.ubuntu.com/resolute/rtkit). + Start up a Noble container or vm and copy in the Resolute .deb. For example, in lxc: + -lxc file push rtkit_0.14-1_amd64.deb <container>/root/ + Then, in the container, update the system and install rtkit (this will be the Noble version): + -apt update && apt dist-upgrade -y && apt install -y rtkit + Once this finishes, attempt to install the Resolute version of rtkit: + -dpkg --force-depends -i rtkit_0.14-1_amd64.deb + This should fail with the same postint error that was seen in the original bug: + -/usr/lib/sysusers.d/rtkit.conf:1: Unknown modifier 'u!'. + -dpkg: error processing package rtkit (--install): + - installed rtkit package post-installation script subprocess returned error exit status 1 + * To verify the fix, first download the updated .deb (should be version 0.14-1ubuntu0.1). + Copy the new .deb into the container, as before: + -lxc file push rtkit_0.14-1ubuntu0.1_amd64.deb <container>/root/ + Next, attempt to install this version: + -dpkg -i rtkit_0.14-1ubuntu0.1_amd64.deb + This should fail when attempting to unpack, before making it to setup: + -dpkg: dependency problems prevent configuration of rtkit: + - rtkit depends on systemd-sysusers (>= 257~); however: + - Package systemd-sysusers is not installed. + - Version of systemd-sysusers on system, provided by systemd:amd64, is 255.4-1ubuntu8.17 + With the fix applied, rtkit requires that systemd be updated before it will attempt to install. + During an upgrade, this would ensure that the "u!" modifier would be accepted as valid syntax, + preventing the update failure. + + * In addition to these tests, it is useful to verify that the release upgrade does not regress with the fix. This can be done by launching a fresh Noble container or VM, as done previously. Then, update the system and install the fixed version of the package. From here, run: + -do-release-upgrade -d + and follow the prompts to perform the upgrade. The fixed package should not allow the original bug's failure state to occur. + [ Where problems could occur ] - - * The change only adds a versioned dependency to ensure that rtkit is configured with a sufficiently - new systemd. - * The main potential regression is that the dependency could cause systemd to be upgraded earlier in - an installation or upgrade transaction, which may affect the installation behavior of other packages - that interact with or depend on systemd. - - + + * The change only adds a versioned dependency to ensure that rtkit is configured with a sufficiently + new systemd. + * The main potential regression is that the dependency could cause systemd to be upgraded earlier in + an installation or upgrade transaction, which may affect the installation behavior of other packages + that interact with or depend on systemd. + [ Other Info ] - - * This is a relatively low-risk change, as no rtkit daemon functionality is changed by the update. - The issue being addressed only becomes apparent during a release upgrade, meaning it doesn't affect - the package otherwise, and the proposed fix should not either. + * No rtkit daemon functionality is changed by the update. + The issue being addressed only becomes apparent during a release upgrade, meaning it doesn't affect + the package otherwise, and the proposed fix should not either. However, this + is not a low-risk change, because it can affect ordering in a large transaction, + such as a release update. [Original Description] Ubuntu did not upgrade completely from 24.04 to 26.04. However, due to this bug and another one with tcpdump, Software Update does not work any longer: the upgrade cannot be completed. ProblemType: Package DistroRelease: Ubuntu 26.04 Package: rtkit 0.14-1 ProcVersionSignature: Ubuntu 6.8.0-134.134-generic 6.8.12 Uname: Linux 6.8.0-134-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Jul 5 17:50:52 2026 ErrorMessage: old rtkit package postinst maintainer script subprocess failed with exit status 1 InstallationDate: Installed on 2020-10-02 (2103 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2.1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.23.7ubuntu1 apt 2.8.3 SourcePackage: rtkit Title: package rtkit 0.14-1 failed to install/upgrade: old rtkit package postinst maintainer script subprocess failed with exit status 1 UpgradeStatus: No upgrade log present (probably fresh install)
** Description changed: [ Impact ] * The version of rtkit in Noble is 0.13-5build1. Users who have this package may not be able to complete an upgrade from Noble to Resolute, as the new version of rtkit (0.14-1) can fail to install. This is due to the rtkit update being attempted before a newer systemd version is installed, which provides a newer systemd-sysusers that rtkit 0.14-1 needs. * rtkit 0.14-1 installs a sysusers.d file using the u! modifier, which is only supported by systemd-sysusers starting with systemd 257 (Noble ships 255). * The fix adds a versioned dependency on systemd (>= 257~) so that the required systemd implementation is installed before rtkit is configured. [ Test Plan ] * Note: while testing this bug, I was not able to reproduce the bug during a normal "do-release-upgrade", so the steps described below involve using dpkg directly. If a package set is found that reproduces the bug, then testing with an upgrade would be preferable. * To reproduce, download the Resolute rtkit .deb (can be found here: https://packages.ubuntu.com/resolute/rtkit). Start up a Noble container or vm and copy in the Resolute .deb. For example, in lxc: -lxc file push rtkit_0.14-1_amd64.deb <container>/root/ Then, in the container, update the system and install rtkit (this will be the Noble version): -apt update && apt dist-upgrade -y && apt install -y rtkit Once this finishes, attempt to install the Resolute version of rtkit: -dpkg --force-depends -i rtkit_0.14-1_amd64.deb This should fail with the same postint error that was seen in the original bug: -/usr/lib/sysusers.d/rtkit.conf:1: Unknown modifier 'u!'. -dpkg: error processing package rtkit (--install): - installed rtkit package post-installation script subprocess returned error exit status 1 * To verify the fix, first download the updated .deb (should be version 0.14-1ubuntu0.1). Copy the new .deb into the container, as before: -lxc file push rtkit_0.14-1ubuntu0.1_amd64.deb <container>/root/ Next, attempt to install this version: -dpkg -i rtkit_0.14-1ubuntu0.1_amd64.deb This should fail when attempting to unpack, before making it to setup: -dpkg: dependency problems prevent configuration of rtkit: - rtkit depends on systemd-sysusers (>= 257~); however: - Package systemd-sysusers is not installed. - Version of systemd-sysusers on system, provided by systemd:amd64, is 255.4-1ubuntu8.17 With the fix applied, rtkit requires that systemd be updated before it will attempt to install. During an upgrade, this would ensure that the "u!" modifier would be accepted as valid syntax, preventing the update failure. - - * In addition to these tests, it is useful to verify that the release upgrade does not regress with the fix. This can be done by launching a fresh Noble container or VM, as done previously. Then, update the system and install the fixed version of the package. From here, run: - -do-release-upgrade -d - and follow the prompts to perform the upgrade. The fixed package should not allow the original bug's failure state to occur. + * In addition to these tests, it is useful to verify that the release upgrade does not regress with the fix. + This can be done by launching a fresh Noble container or VM, as done previously. Then, update the system + and install the fixed version of the package. From here, run: + -do-release-upgrade -d + and follow the prompts to perform the upgrade. The fixed package should not allow the original bug's + failure state to occur. [ Where problems could occur ] * The change only adds a versioned dependency to ensure that rtkit is configured with a sufficiently new systemd. * The main potential regression is that the dependency could cause systemd to be upgraded earlier in an installation or upgrade transaction, which may affect the installation behavior of other packages that interact with or depend on systemd. [ Other Info ] * No rtkit daemon functionality is changed by the update. The issue being addressed only becomes apparent during a release upgrade, meaning it doesn't affect - the package otherwise, and the proposed fix should not either. However, this - is not a low-risk change, because it can affect ordering in a large transaction, - such as a release update. + the package otherwise, and the proposed fix should not either. However, this is not a low-risk + change, because it can affect ordering in a large transaction, such as a release update. [Original Description] Ubuntu did not upgrade completely from 24.04 to 26.04. However, due to this bug and another one with tcpdump, Software Update does not work any longer: the upgrade cannot be completed. ProblemType: Package DistroRelease: Ubuntu 26.04 Package: rtkit 0.14-1 ProcVersionSignature: Ubuntu 6.8.0-134.134-generic 6.8.12 Uname: Linux 6.8.0-134-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Jul 5 17:50:52 2026 ErrorMessage: old rtkit package postinst maintainer script subprocess failed with exit status 1 InstallationDate: Installed on 2020-10-02 (2103 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2.1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.23.7ubuntu1 apt 2.8.3 SourcePackage: rtkit Title: package rtkit 0.14-1 failed to install/upgrade: old rtkit package postinst maintainer script subprocess failed with exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2159792 Title: SRU: package rtkit 0.14-1 failed to install/upgrade: old rtkit package postinst maintainer script subprocess failed with exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/2159792/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
