This bug was fixed in the package livecd-rootfs - 2.765.13
---------------
livecd-rootfs (2.765.13) jammy; urgency=medium
[ Heinrich Schuchardt ]
* Backporting patches to support new RISC-V platforms (LP: #1997233)
* Add support for the LicheeRV board (SUBARCH=licheerv)
* Add support for the PolarFire Icicle Kit board (SUBARCH=icicle)
* Reduce initrd size for Nezha and LicheeRV boards
* Use efi=debug earlycon on kernel command line
livecd-rootfs (2.765.12) jammy; urgency=medium
* Remove fwupd, modemmanager, and udisks2 from the cloud images.
LP: #1981109.
-- Łukasz 'sil2100' Zemczak <lukasz.zemc...@ubuntu.com> Mon, 21 Nov
2022 11:18:14 +0100
** Changed in: livecd-rootfs (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
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 Released
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
--
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
