prompted to remove systemd-hwe-hwdb but re-installed via updates

Bug #1991139 reported by ipv
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Triaged
Low
Unassigned

Bug Description

sudo apt upgrade

gives me this :

The following package was automatically installed and is no longer required:
systemd-hwe-hwdb
Use 'sudo apt autoremove' to remove it.
The following packages have been kept back:
libnss-systemd libpam-systemd libspeechd2 libsystemd0 libudev1 python3-speechd speech-dispatcher speech-dispatcher-audio-plugins
speech-dispatcher-espeak-ng systemd systemd-oomd systemd-sysv systemd-timesyncd udev
0 upgraded, 0 newly installed, 0 to remove and 14 not upgraded.

sudo apt autoremove

removes the no longer required systemd-hwe-hwdb

but the software updater brings it back & this cycle goes on in loop.

kindly check.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu:
status: New → Confirmed
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1991139/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
ipv (ipv) wrote (last edit ):

update :

i had 14 phased updates pending & after installing them with a work around the systemd-hwe-hwdb issue no longer persists.

summary: prompted to remove systemd-hwe-hwdb but re-installed via updates
+ [SOLVED]
Revision history for this message
halogen2 (halogen2) wrote : Re: prompted to remove systemd-hwe-hwdb but re-installed via updates [SOLVED]

> am gonna mark this thread as solved.

Well, you used a workaround following https://ubuntuforums.org/showthread.php?t=2479535 but that doesn't fix the bug. So this bug report should not be marked solved yet.

I see the same behavior as reported in this bug. My post on ubuntuforums about it - https://ubuntuforums.org/showthread.php?t=2478639&p=14113797&viewfull=1#post14113797

Regarding the bot comment #2, source packages affected are probably update-manager and synaptic

tags: added: jammy
affects: ubuntu → apt (Ubuntu)
Revision history for this message
ipv (ipv) wrote :

> this bug report should not be marked solved yet.

duly noted.

have made the changes.

pardon me for the confusion.

summary: prompted to remove systemd-hwe-hwdb but re-installed via updates
- [SOLVED]
tags: added: foundations-triage-discuss
tags: removed: foundations-triage-discuss
Revision history for this message
ipv (ipv) wrote :

requesting an update on the status of this bug.

i have not encountered it after a fresh install.

can i mark it solved?

i do not wish to leave it hanging.

Revision history for this message
Julian Andres Klode (juliank) wrote :

I think it's a bug where update-manager installs those additional packages which stems from its implementation of phased updates, but it's also not a priority to work on because this only happens when an SRU introduces a new dependency which does not happen all that often.

affects: apt (Ubuntu) → update-manager (Ubuntu)
Changed in update-manager (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Julian Andres Klode (juliank) wrote :

The reason the bug does not occur anymore is because systemd finished phasing.

Revision history for this message
Lukas Märdian (slyon) wrote :

We have a workaround available (force installing phasing updates) and introduction of new dependencies in SRUs rarely happens, so I'm setting the priority to "Low".

Changed in update-manager (Ubuntu):
importance: Undecided → Low
Revision history for this message
ipv (ipv) wrote (last edit ):

cool.

no worries, no hurries, take your time.

julian & lukas thank you much for acknowledging & the prompt replies.

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.