Comment 7 for bug 950791

Revision history for this message
Tim Frost (timfrost) wrote :

I applied updates as detected this morning NZ time using update-manager, then refreshed the lists and applied a second set of updates. aptdaemon crashed during post-processing after instalation of the second set of updates.
 /var/cache/apt/archives has two sets of files for aptdaemon:
tim@zaphod:~$ ls -l /var/cache/apt/archives/aptdaemon*
-rw-r--r-- 1 root root 15146 Mar 9 22:03 /var/cache/apt/archives/aptdaemon_0.43+bzr778-0ubuntu1_all.deb
-rw-r--r-- 1 root root 15130 Mar 15 02:04 /var/cache/apt/archives/aptdaemon_0.43+bzr784-0ubuntu1_all.deb
-rw-r--r-- 1 root root 162996 Mar 9 22:03 /var/cache/apt/archives/aptdaemon-data_0.43+bzr778-0ubuntu1_all.deb
-rw-r--r-- 1 root root 163060 Mar 15 02:04 /var/cache/apt/archives/aptdaemon-data_0.43+bzr784-0ubuntu1_all.deb
tim@zaphod:~$
Note that timestamps are NZDT, 13 hours ahead of UTC.

After applying the second set of updates, update manager reported that a restart was required, and the restart icon has apeared in the gnome panel. aptdaemon crashed at about the time when update-manager was generating the reboot alert at the end of installation of the second set of updates, but no crash occurred when I needed to reboot last (at least 2 days ago). This suggests that the bug was introduced between bzr778 and bzr784