One possible solution is to split the fwupd package along it's possible plugins
into multiple packages.
However I tend to agree that it has no use in a cloud or container seed.
I also agree libmm-glib0 shouldn't recommend modem manager.
** Changed in: fwupd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
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 modemmanager package in Ubuntu:
New
Status in ubuntu-meta package in Ubuntu:
New
Bug 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
