Comment 3 for bug 43774

The proper solution (which I described in the original report, and you described right back at me) requires much more invasive changes to update-manager. I'm actually interested in working on this, but now I'm merely hoping to see less troubles like "I clicked the icon, but it said it's already running" in time for dapper, which is fast approaching.

I apologize if I did not make it clear that this was intended as a small and easily-tested workaround until update-notifier and update-manager become properly integrated, presumably sometime between dapper and edgy. Perhaps this report should've been categorized in launchpad more appropriately as release-specific.