[Bug 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container
Ćukasz Zemczak
1981109 at bugs.launchpad.net
Mon Nov 21 13:03:51 UTC 2022
Updated the bug description to be SRUable.
** Description changed:
+ [Impact]
+
+ Cloud images should not have fwupd, modemmanager, and udisks2 installed
+ as those are not needed and only taking up memory.
+
+ [Test Case]
+
+ Build cloud images with livecd-rootfs and confirm that fwupd,
+ modemmanager, and udisks2 are not present and not running.
+
+ [Regression Potential]
+
+ Only thing that might happen is for any of the 3 listed packages getting
+ removed from images where they might be used. So possibly double-
+ checking if this will affect preinstalled server images and if they care
+ about this or not.
+
+ [Original Description]
+
Looking at memory utilization in a pristine Ubuntu lxd container (top -o
RES), I see that ModemManager is running, which I was surprised to see
is present at all in the stock image.
Tracking this I find that fwupd depends on libmm-glib0, which in turn
Recommends: modemmanager.
Libraries in general should not recommend daemons, so it's possible this
should be fixed by libmm-glib0 dropping this Recommends. It certainly
doesn't seem to be a deliberate decision by the Server Team to have
modemmanager installed and running by default on all systems.
** Changed in: livecd-rootfs (Ubuntu Jammy)
Status: Triaged => Fix Committed
** Tags added: verification-needed verification-needed-jammy
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1981109
Title:
server image pulls in ModemManager via fwupd, consumes 25MiB RAM in
every container
Status in fwupd package in Ubuntu:
Invalid
Status in livecd-rootfs package in Ubuntu:
Fix Released
Status in modemmanager package in Ubuntu:
Triaged
Status in ubuntu-meta package in Ubuntu:
New
Status in fwupd source package in Jammy:
Invalid
Status in livecd-rootfs source package in Jammy:
Fix Committed
Status in modemmanager source package in Jammy:
New
Status in ubuntu-meta source package in Jammy:
New
Bug description:
[Impact]
Cloud images should not have fwupd, modemmanager, and udisks2
installed as those are not needed and only taking up memory.
[Test Case]
Build cloud images with livecd-rootfs and confirm that fwupd,
modemmanager, and udisks2 are not present and not running.
[Regression Potential]
Only thing that might happen is for any of the 3 listed packages
getting removed from images where they might be used. So possibly
double-checking if this will affect preinstalled server images and if
they care about this or not.
[Original Description]
Looking at memory utilization in a pristine Ubuntu lxd container (top
-o RES), I see that ModemManager is running, which I was surprised to
see is present at all in the stock image.
Tracking this I find that fwupd depends on libmm-glib0, which in turn
Recommends: modemmanager.
Libraries in general should not recommend daemons, so it's possible
this should be fixed by libmm-glib0 dropping this Recommends. It
certainly doesn't seem to be a deliberate decision by the Server Team
to have modemmanager installed and running by default on all systems.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1981109/+subscriptions
More information about the foundations-bugs
mailing list