[Karmic 9.10] no updates with hibernation mode?

[Sam_]

Binary package hint: update-manager

#1
Not sure if I assigned to the right package.

#2
Uptime with hibernation mode 14d 22h
No changes of default settings made (settings are fine with me).
http://www.ubuntu.com/getubuntu/releasenotes/910#Change%20in%20notifications%20of%20available%20updates

Issue:
So far no updates were offered while I'm hibernating.
e.g. there is a new kernel image available
http://packages.ubuntu.com/karmic-updates/linux-image-generic
Not arrived yet:
dpkg -l linux-image* | grep ii
ii linux-image-2.6.31-14-generic 2.6.31-14.48 Linux kernel image for version 2.6.31 on x86
ii linux-image-2.6.31-15-generic 2.6.31-15.50 Linux kernel image for version 2.6.31 on x86
ii linux-image-2.6.31-16-generic 2.6.31-16.53 Linux kernel image for version 2.6.31 on x86
ii linux-image-generic 2.6.31.16.29 Generic Linux kernel image

Question: Is it a bug or a feature? Is it due to update-manager or hibernate?

#3
Updates which are manually started proceed fine.
Run Synaptic, reload packages list, updates offered, mark updates, apply, done.
Although I've made configuration in Synaptic to load package list automatically, if outdated, but it doesn't seem to take effect.

ProblemType: Bug
Architecture: amd64
CheckboxSubmission: 70e14b5afb9614c469fa67a7fca95226
CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b
Date: Thu Jan 7 17:39:28 2010
DistroRelease: Ubuntu 9.10
Package: update-manager 1:0.126.9
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=C
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
SourcePackage: update-manager
Uname: Linux 2.6.31-16-generic x86_64

[Sam_ (and-sam)]

Uptime now 17d 19h.
No update-manager poped up yet, even we've got sec updates, such as USN-880-1 and USN-878-1.
http://www.ubuntu.com/usn
Hence, one could say it affects security, when release note is true.
Quote:
>Users are notified of security updates on a daily basis<
Unless, it confines to cold boot or reboot.

[Sam_ (and-sam)]

Made a
sudo updatedb
because my
/var/lib/mlocate/mlocate.db
was from 23rd of Dec, in case that'ts related; but still no reaction from update-manager.

[Jean-Baptiste Lallement (jibel)]

Thanks for your report:
What is the output of:
$ ls -l /var/lib/apt/periodic
?

[Sam_ (and-sam)]

Since I saw security updates available (on website)
I've updated manually via Synaptic, then restart was requested afterwards.
Hibernation mode, uptime now 1d 21h.

ls -l /var/lib/apt/periodic
insgesamt 0
-rw-r--r-- 1 root root 0 2010-01-16 19:22 update-stamp
-rw-r--r-- 1 root root 0 2010-01-16 20:33 update-success-stamp

[Sam_ (and-sam)]

There is a: USN-887-1: LibThai vulnerability
Output of
$ls -l /var/lib/apt/periodic
didn't change.
No activity from update-manager.
Hibernation mode, uptime 4d 1h.

$dpkg -l libthai0
ii libthai0 0.1.12-1

[Sam_ (and-sam)]

Ok, since there are lots of USNs now and it affects security , I'll update manually again via Synaptic.
Hibernation mode, uptime 4d 22h, no activity from update-manager.
No change in /var/lib/apt/periodic.

[Sam_ (and-sam)]

After updating:
$ls -l /var/lib/apt/periodic
insgesamt 0
-rw-r--r-- 1 root root 0 2010-01-16 19:22 update-stamp
-rw-r--r-- 1 root root 0 2010-01-21 18:20 update-success-stamp

[Sam_ (and-sam)]

For the record:
Hibernation mode uptime was 19d 22h, nothing, nada, zero activity from update-manager.
Hence, because of USN, upgraded to 2.6.31-19 manually via Synaptic and had to reboot of course.

[Sam_ (and-sam)]

Update:
We've had a nice trace concerning cron.
$ps -ef | grep cron
root 1074 1 0 Feb05 ? 00:00:00 cron
1000 13514 1771 0 21:11 pts/0 00:00:00 grep --color=auto cron

$grep cron /var/log/syslog
Feb 5 17:39:37 host anacron[1394]: Job `cron.daily' terminated (mailing output)
Feb 5 17:39:37 host anacron[1394]: Can't find sendmail at /usr/sbin/sendmail, not mailing output
Feb 5 17:39:37 host anacron[1394]: Job `cron.weekly' started
Feb 5 17:39:38 host anacron[2241]: Updated timestamp for job `cron.weekly' to 2010-02-05
Feb 5 17:40:26 host anacron[1394]: Job `cron.weekly' terminated
Feb 5 17:44:29 host anacron[1394]: Job `cron.monthly' started
Feb 5 17:44:30 host anacron[2389]: Updated timestamp for job `cron.monthly' to 2010-02-05
Feb 5 17:44:30 host anacron[1394]: Job `cron.monthly' terminated
Feb 5 17:44:30 host anacron[1394]: Normal exit (3 jobs run)
Feb 5 18:17:01 host CRON[3309]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Feb 5 19:17:01 host CRON[4875]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Feb 5 20:17:01 host CRON[6380]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Feb 5 21:17:01 host CRON[7900]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Feb 5 22:17:01 host CRON[9414]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Feb 5 23:17:01 host CRON[10959]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Feb 5 23:39:18 host anacron[11670]: Anacron 2.3 started on 2010-02-05
Feb 5 23:39:18 host anacron[11670]: Normal exit (0 jobs run)
Feb 6 16:02:29 host anacron[11758]: Anacron 2.3 started on 2010-02-06
Feb 6 16:02:29 host anacron[11758]: Will run job `cron.daily' in 5 min.
Feb 6 16:02:29 host anacron[11758]: Jobs will be executed sequentially
Feb 6 16:02:44 host init: anacron main process (11758) killed by TERM signal
Feb 6 16:17:02 host CRON[12308]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Feb 6 17:17:01 host CRON[13878]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Feb 6 18:17:01 host CRON[15401]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Feb 6 19:17:01 host CRON[16908]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Feb 6 20:17:01 host CRON[18454]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Feb 6 21:17:01 host CRON[20076]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Feb 6 22:17:01 host CRON[21566]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Feb 6 23:17:01 host CRON[23080]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Feb 7 00:17:01 host CRON[24615]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Feb 7 01:17:01 host CRON[26199]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Feb 7 02:04:18 host anacron[27499]: Anacron 2.3 started on 2010-02-07
Feb 7 02:04:18 host anacron[27499]: Will run job `cron.daily' in 5 min.
Feb 7 02:04:18 host anacron[27499]: Jobs will be executed sequentially
Feb 7 02:04:19 host init: anacron main process (27499) killed by TERM signal
Feb 7 09:40:09 host anacron[27587]: Anacron 2.3 started on 2010-02-07
Feb 7 09:4...

[Sam_ (and-sam)]

About forty minutes after resume today:
$ps -ef | grep -E 'cron|parts|sleep|apt'
root 1074 1 0 Feb05 ? 00:00:00 cron
1000 20861 18887 0 17:09 pts/1 00:00:00 grep --color=auto -E cron|parts|sleep|apt

My question is still, why update manager is nonactive after wakeup from hibernation and active after normal boots.
My expectation would be, the behaviour of anacron is the same in either one or the other state.
Attached syslog from last three days.

[Sam_ (and-sam)]

Have tried to add affects cron, result couldn't find cron.
Tried anacron, but isn't specified.

[Sam_ (and-sam)]

Affects update-notifier.
#
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/356152
#
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/506135
#
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/487403
#
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/484893
#
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/472518
#
http://osdir.com/ml/ubuntu-users/2010-01/msg01530.html

[Sam_ (and-sam)]

$ ps ax|grep update-notifier
 1640 ? S 0:03 update-notifier --startup-delay=60
30603 pts/1 R+ 0:00 grep --color=auto update-notifier

Current term.log is empty since 5th Feb.

[Sam_ (and-sam)]

$perl auto.pl
0 normal updates, 0 security updates available
interval_days from gconf: 0
Autolaunch disabled because interval_days 0 <= 0

Check for updates daily, notify only.

[Sam_ (and-sam)]

$gconftool --recursive-list /apps/update-notifier
 auto_launch = true
 hide_reboot_notification = false
 show_apport_crashes = true
 end_system_uids = 500
 regular_auto_launch_interval = 0

The interval (in days) when auto launching update-manager for normal updates. Please note that it will auto launch for security updates immediately. If you set it to "0" it will also launch as soon as updates become available.

$gconftool --recursive-list /apps/update-manager
 autoclose_install_window = true
 first_run = false
 show_versions = true
 remind_reload = true
 window_size = (979,855)
 show_details = true
 launch_time = 1261516722
 check_dist_upgrades = true

[Peter Ridge (pridge)]

Confirming that daily update notification doesn't trigger if the system is hibernated. I've been running Synaptic manually to check for and apply updates.

$ uptime
09:32:08 up 28 days, 49 min

$ ls -l /var/lib/apt/periodic
total 0
-rw-r--r-- 1 root root 0 2010-02-23 07:51 update-stamp
-rw-r--r-- 1 root root 0 2010-04-14 09:17 update-success-stamp

[Sam_ (and-sam)]

Update:
Upgraded to Lucid and the issue is kind of solved for me.
Update-manager GUI doesn't pop up, but it appears in 'window chooser' applet of buttom panel.
When I do a 'sudo apt-get update' it pops up.
Also I can see available updates in conky.
Fantastic, I'm happy, thanks very much for your efforts regarding Lucid.

For the record:
Resume from hibernation (2 days uptime)
$ ls -l /var/lib/apt/periodic
total 0
-rw-r--r-- 1 root root 0 2010-05-26 19:28 update-stamp
-rw-r--r-- 1 root root 0 2010-05-26 19:28 update-success-stamp

$ ps ax|grep update-notifier
 9483 ? S 0:01 update-notifier
21884 pts/0 S+ 0:00 grep --color=auto update-notifier

$ perl auto.pl
8 normal updates, 4 security updates available
interval_days from gconf: 0
Autolaunch disabled because interval_days 0 <= 0

$ gconftool --recursive-list /apps/update-notifier
 auto_launch = true
 hide_reboot_notification = false
 show_apport_crashes = true
 end_system_uids = 500
 regular_auto_launch_interval = 0

$ dpkg -l linux-image* | grep ii
ii linux-image-2.6.31-21-generic 2.6.31-21.59
ii linux-image-2.6.32-22-generic 2.6.32-22.33
ii linux-image-generic 2.6.32.22.23

$ dpkg -l update-manager
ii update-manager 1:0.134.8

$ dpkg -l update-notifier
ii update-notifier 0.99.3

[Robert Roth (evfool)]

Sam_ (and-sam): Does your last comment mean that the issue is fixed for you? IF yes, then maybe we should close this bug, as Karmic has already reached it's End Of Life, and you have reported that on Lucid you don't see the problem anymore.

[Sam_ (and-sam)]

Robert, thank you for the reminder. Agree to close this bug, apparently it was solved with Lucid.

[Robert Roth (evfool)]

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad