Update-notifier-common not purged

Bug #437907 reported by Robert Browne on 2009-09-28
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
update notifier
Confirmed
Undecided
Unassigned
update-notifier (Ubuntu)
Undecided
Unassigned

Bug Description

When update-notifier is purged, update-notifier-common should be purged as well.
Also an apt-get autoremove does not purge it.

Update-notifier-common is very annoying as it runs a cron.daily script with
a random wait. At least the default values should all be 0, so the script will not run.
APT::Periodic::Update-Package-Lists "0"

Jesse Michael (jesse.michael) wrote :

I ran into this bug today upgrading a headless Lucid box to Maverick.

Every time I logged in after upgrading, I got the following lines spammed at me--

exec: 3: /usr/lib/update-notifier/update-motd-cpu-checker: not found
run-parts: /etc/update-motd.d/20-cpu-checker exited with return code 2
exec: 3: /usr/lib/update-notifier/update-motd-updates-available: not found
run-parts: /etc/update-motd.d/90-updates available exited with return code 2
exec: 3: /usr/lib/update-notifier/update-motd-reboot-required: not found
run-parts: /etc/update-motd.d/98-reboot-required exited with return code 2

The problem is that because update-notifier-common wasn't purged, the scripts in /etc/update-motd.d are not removed because they're marked as config files and pam_motd runs them at login time even though the necessary programs they attempt to execute aren't installed anymore.

Kees Cook (kees) wrote :

Additionally, since the conffiles are really scripts, they need to be able to run when the package is removed but not purged (i.e. they should check for the scripts they're trying to run). Better yet, scripts should not be conffiles.

Changed in update-notifier:
status: New → Confirmed
Changed in update-notifier (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers