Update-notifier-common not purged
Bug #437907 reported by
Robert Browne
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update notifier |
Confirmed
|
Undecided
|
Unassigned | ||
update-notifier (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
When update-notifier is purged, update-
Also an apt-get autoremove does not purge it.
Update-
a random wait. At least the default values should all be 0, so the script will not run.
APT::Periodic:
To post a comment you must log in.
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 motd.d/ 20-cpu- checker exited with return code 2 update- notifier/ update- motd-updates- available: not found motd.d/ 90-updates available exited with return code 2 update- notifier/ update- motd-reboot- required: not found motd.d/ 98-reboot- required exited with return code 2
run-parts: /etc/update-
exec: 3: /usr/lib/
run-parts: /etc/update-
exec: 3: /usr/lib/
run-parts: /etc/update-
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.