Repository navigation
Disable man-db dpkg trigger #10977
Description
Activity
Hi @lengau , we're looking into this issue , we will update on it ASAP. thank you !
Reacted by Alex Lowe and Axel Huebl- added 8 commits that reference this issue
on Nov 15, 2024 76 remaining items
- added 2 commits that reference this issue
on Oct 30, 2025 Fix is deployed. 🎉
Reacted by Connor Bär, Kelvin M. Klann, Reuben Lifshay, ThisAMJ, Storm Heg and MatthiasReacted by Alex AndersonReacted by Alexander Turenko and Oliver KästnerFunny enough, I had this line in my workflow (run on
ubuntu-latest) and it has started failing because the file no longer exists 😓- run: sudo rm /var/lib/man-db/auto-updateNeeds
-for more likely theruncan now just be removed.Reacted by Erik Bershel and R Gibim- added a commit that references this issue
on Feb 24, 2026
Description
This isn't necessarily a bug - more a performance enhancement request, but there's no category for that.
When running
apt installcommands on Ubuntu hosted runners, the runners spend about 45 seconds just processing man-db triggers:However, in very few cases are these runners ever going to actually use these man-db changes, so this is close to a minute of wasted time for each run.
Adding the following commands to the setup of each runner image would disable this trigger:
Platforms affected
Runner images affected
Image version and build link
Relevant step: https://github.com/canonical/starflow/actions/runs/11860374887/job/33055486302?pr=23#step:2:88
Is it regression?
no
Expected behavior
man-db triggers don't get run on
apt-get installActual behavior
man-db triggers do get run
Repro steps
Run the following workflow, note that it takes tends to timeout during the trigger processing.