Hm, I see. Yeah, the package priority has no effect about its runtime behavior or anything like that, so this is not related to the issue you're having.
I would suggest seeking help on a support forum: https://discourse.ubuntu.com/t/community-support/709. That may help you find the issue, or gather enough information to create a bug report against the correct package with relevant logs etc. ** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2098710 Title: The systemd-cryptsetup package priority should be important, as per LP: #2084251 Status in systemd package in Ubuntu: Invalid Bug description: ### **Summary** The package priority should be **important**, as per LP: #2084251 (https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2084251). --- ### **Bug Description** #### **System Information** ```bash $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 24.10 Release: 24.10 Codename: oracular ``` #### **Package Information** ```bash $ apt-cache policy systemd-cryptsetup systemd-cryptsetup: Installed: 256.5-2ubuntu3.1 Candidate: 256.5-2ubuntu3.1 Version table: *** 256.5-2ubuntu3.1 500 500 http://ca.archive.ubuntu.com/ubuntu oracular-updates/main amd64 Packages 100 /var/lib/dpkg/status 256.5-2ubuntu3 500 500 http://ca.archive.ubuntu.com/ubuntu oracular/main amd64 Packages ``` ```bash $ apt-cache show systemd-cryptsetup | grep -i priority Priority: optional Priority: optional ``` --- ### **Expected Behavior** The priority of `systemd-cryptsetup` should be **important**, as per the fix mentioned in **LP: #2084251**. According to the fix: - `systemd-cryptsetup` should have **Priority: important** in the package metadata. --- ### **Actual Behavior** Despite installing **systemd-cryptsetup 256.5-2ubuntu3.1**, the package priority remains **optional**, instead of **important**. This means the intended fix was **not fully applied** in the Ubuntu package repository. --- ### **Steps to Reproduce** 1. Run `apt-cache policy systemd-cryptsetup` to verify the installed version. 2. Run `apt-cache show systemd-cryptsetup | grep -i priority` to check the package priority. 3. Notice that the priority is still **optional** instead of **important**. --- ### **Additional Notes** - The fix for **LP: #2084251** states that `systemd-cryptsetup` should be **important**, but the repository metadata has not been updated accordingly. - The package is installed and correctly recommended by `systemd`, but the incorrect priority setting may lead to **unexpected removals** in some cases. - The priority should be updated in the repository metadata to match the intended fix. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: systemd-cryptsetup 256.5-2ubuntu3.1 ProcVersionSignature: Ubuntu 6.11.0-14.15-generic 6.11.0 Uname: Linux 6.11.0-14-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 17 11:48:35 2025 InstallationDate: Installed on 2024-08-15 (187 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> SourcePackage: systemd UpgradeStatus: Upgraded to oracular on 2024-10-26 (115 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2098710/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
