Comment 15 for bug 549217

I recognize it is difficult to confirm bugs relating to update checking, because (1) they're dependent on updates from a repository you don't control, (2) the steps often involve waiting for days, and (3) we've never had a specification for exactly how they should behave. It would be super-awesome if someone could write a test harness to solve #1 and #2, with a dummy updates repository that you can configure to advertise a particular kind of update at a particular time, combined with temporarily setting your computer's clock forward to test whatever the next step is. Meanwhile, solving #3 is my responsibility, and I've started writing a specification <https://wiki.ubuntu.com/SoftwareUpdateHandling>, but it needs a lot of detail yet.

Paddy, thanks for clarifying your problem. Do you know for sure that security updates are being auto-installed on your computer? If they are, then the bugs ceg and Konstantin are seeing are both different from yours and should be reported separately.

Here's a test case to start off with:
------------
1. Install Ubuntu 10.04.
2. Log in to the new Ubuntu installation for the first time.
3. In "Software Sources" > "Updates", choose "Check for updates: Daily" and "Install security updates without confirmation".
4. Set the system clock forward one day.
5. Wait for ten minutes.

What should happen: Update Manager opens, displaying only non-security updates.
------------
If that's not what actually happens, please replace the current description with this, plus a line for what actually happens. Then this report will be ready for an engineer.