There were indeed some flashplugin updates that I applied in the last days, but notethat the first two emails are for the *same* version. My laptop was probably in sleep over one night which might explain the day of silence.
/usr/share/package-data-downloads/flashplugin-installer dates of the 18th of April around midnight and /var/lib/update-notifier/package-data-downloads/flashplugin-installer of the 20th of April.
So I don't see why this should have run on the 20th.
But while checking the code, I believe I've actually found a bug in the handling of failed updates:
def hook_aged_out(hook_name):
"""Check if this hook has been failing consistently for >= 3 days"""
Hi,
After some recent updates in precise, I've started receiving cron emails such as:
Date: Tue, 17 Apr 2012 11:49:02 +0200 (CEST)
Subject: Anacron job 'cron.daily' on bee
/etc/cron. daily/update- notifier- common: installer: downloading archive. canonical. com/pool/ partner/ a/adobe- flashplugin/ adobe-flashplug in_ 228.orig. tar.gz
flashplugin-
http://
11.2.202.
Installing from local file /tmp/tmppRl5Rq.gz
Flash Plugin installed.
Then the next day:
Date: Wed, 18 Apr 2012 11:25:36 +0200 (CEST)
Subject: Anacron job 'cron.daily' on bee
/etc/cron. daily/update- notifier- common: installer: downloading archive. canonical. com/pool/ partner/ a/adobe- flashplugin/ adobe-flashplug in_ 228.orig. tar.gz
flashplugin-
http://
11.2.202.
Installing from local file /tmp/tmpTeTtwA.gz
Flash Plugin installed.
Then after a day of silence:
Date: Fri, 20 Apr 2012 07:38:09 +0200 (CEST)
Subject: Anacron job 'cron.daily' on bee
/etc/cron. daily/update- notifier- common: installer: downloading archive. canonical. com/pool/ partner/ a/adobe- flashplugin/ adobe-flashplug in_ 233.orig. tar.gz
flashplugin-
http://
11.2.202.
Installing from local file /tmp/tmpZsCTV4.gz
Flash Plugin installed.
There were indeed some flashplugin updates that I applied in the last days, but notethat the first two emails are for the *same* version. My laptop was probably in sleep over one night which might explain the day of silence.
/usr/share/ package- data-downloads/ flashplugin- installer dates of the 18th of April around midnight and /var/lib/ update- notifier/ package- data-downloads/ flashplugin- installer of the 20th of April.
So I don't see why this should have run on the 20th.
But while checking the code, I believe I've actually found a bug in the handling of failed updates: out(hook_ name):
def hook_aged_
"""Check if this hook has been failing consistently for >= 3 days"""
try:
d = timedelta(
if d.days >= 3:
except OSError:
except Exception:
return False
os.times()[4] seems a completely bogus value for checking age: "/var/lib/ update- notifier/ package- data-downloads/ flashplugin- installer" ).st_ctime; cur_time = os.times()[4]; microseconds = cur_time - hook_date; d= timedelta( microseconds= microseconds) ; print d.days; print microseconds; print cur_time; print hook_date'
python -c 'from datetime import timedelta; import os; hook_date = os.stat(
-1
-1315376334.45
19523955.25
1334900289.7
(I used the successful stamp file rather than a failed stamp file, but it's the same problem.)
I believe you want: fromtimestamp( os.stat( "/var/lib/ update- notifier/ package- data-downloads/ flashplugin- installer" ).st_ctime) ; cur_time = datetime.now(); d=cur_time - hook_date; print d.days; print cur_time; print hook_date'
python -c 'from datetime import datetime; import os; hook_date = datetime.
Cheers,
ProblemType: Bug notifier- common 0.119ubuntu8 ature: Ubuntu 3.2.0-18.28-generic 3.2.9 ture: all fr_FR:fr: en_GB:en
DistroRelease: Ubuntu 12.04
Package: update-
ProcVersionSign
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 2.0.1-0ubuntu5
Architecture: amd64
Date: Fri Apr 20 15:02:17 2012
PackageArchitec
ProcEnviron:
LANGUAGE=
TERM=xterm
PATH=(custom, user)
LANG=fr_FR.UTF-8
SHELL=/bin/zsh
SourcePackage: update-notifier
UpgradeStatus: Upgraded to precise on 2009-12-07 (864 days ago)