update-notifier tooltip doesn't has the right number of update

[Sebastien Bacher]

update-manager display "Packages to install: 10" but update-notifier "There are
2 updates availables!"

[Michael Vogt (mvo)]

Thanks for this bugreport.
It may take up to 5 minutes for the icon to update it's status. Do you still
see this after that time? Does it not update itself?

thanks,
 Michael

[Michael Vogt (mvo)]

I uploaded a new 0.37.3 update-notifier. It detects changes from apt-get
install/remove/upgrade in max. 30sec and changes from apt-get update in max. 1min.

I would love to know if the incorrect values are gone with that changes.

thanks,
 Michael

[Sebastien Bacher (seb128)]

it was not updated for hours but my system is kind of weird, I've set hoary >
1000 in apt and I dpkg -i my package before uploading, so updates are mix of
updates and downgrades and same versions with different md5 ... I've just
installed the new version and I'll add a comment about it tomorrow

[Michael Vogt (mvo)]

(In reply to comment #3)
> it was not updated for hours but my system is kind of weird, I've set hoary >
> 1000 in apt and I dpkg -i my package before uploading, so updates are mix of
> updates and downgrades and same versions with different md5 ... I've just
> installed the new version and I'll add a comment about it tomorrow

It is not able to detect changes by dpkg directly. It will only update itself
when apt is used. I would love to hear if it still fails to update it's status
for you. I think the recent version is pretty good at keeping track (and
updating should be a matter of <1min)

thanks,
 Michael

[JonathanTurner (probata)]

(In reply to comment #1)
> Thanks for this bugreport.
> It may take up to 5 minutes for the icon to update it's status. Do you still
> see this after that time? Does it not update itself?
>
> thanks,
> Michael

I'm seeing the same thing here, I'm not sure if it's with a newer version. The
version from a few days ago disappeared after an update. Perhaps an update
should be monitored by the update-notifier so it can shut itself off if it
finished properly?

It looks like there are a few instances it should update immediately instead of
on an interval:

.) On a click, it should ask the Update Manager for the correct number of updates
.) After an update, it should check again and update the number
.) After an "update package list" <-- I believe it does this one already

I take the third one back, I just tried "update package list", and it did not
seem to update the correct number of packages until about 1.5 minutes later.
I'm not sure the user will understand the length of the delay.

[Michael Vogt (mvo)]

(In reply to comment #5)
> I'm seeing the same thing here, I'm not sure if it's with a newer version. The
> version from a few days ago disappeared after an update.

Thanks for your comment.

What does that mean exactly? Does that mean that the status was (with the
version 0.38.2 or greater):
a) not updated at all
b) updated incorrect
c) had a long intervall

> Perhaps an update
> should be monitored by the update-notifier so it can shut itself off if it
> finished properly?

That should basicly work. If a update was sucessfull and no more packages are
available the update-notifier
should go away. If not that's a bug in update-notifier.

> It looks like there are a few instances it should update immediately instead of
> on an interval:
>
> .) On a click, it should ask the Update Manager for the correct number of updates
> .) After an update, it should check again and update the number
> .) After an "update package list" <-- I believe it does this one already
>
> I take the third one back, I just tried "update package list", and it did not
> seem to update the correct number of packages until about 1.5 minutes later.
> I'm not sure the user will understand the length of the delay.

I agree that it should update itself quicker. I'll see what I can do to make it
more responsive.
I'm more worried right now about cases where it does not detect a $frontend
update/install at all :)

thanks,
 Michael

[JonathanTurner (probata)]

> What does that mean exactly? Does that mean that the status was (with the
> version 0.38.2 or greater):
> a) not updated at all
> b) updated incorrect
> c) had a long intervall

I'm not sure of the version of the one a few days ago, but after updates
yesterday(1/24/2005) I noticed it started happening. The span of time it took
to update the number of packages is over a minute.

> That should basicly work. If a update was sucessfull and no more packages are
> available the update-notifier
> should go away. If not that's a bug in update-notifier.

Okay, then it's a bug. I think it eventually goes away, but it does take a while.

> I'm more worried right now about cases where it does not detect a $frontend
> update/install at all :)

If there's anything I can do to help test, let me know.

[JonathanTurner (probata)]

>
> I'm not sure of the version of the one a few days ago, but after updates
> yesterday(1/24/2005) I noticed it started happening. The span of time it took
> to update the number of packages is over a minute.
>

After the most recent update (1/30/2005) this no longer seems to be a problem.

[JonathanTurner (probata)]

(In reply to comment #8)
> >
> > I'm not sure of the version of the one a few days ago, but after updates
> > yesterday(1/24/2005) I noticed it started happening. The span of time it took
> > to update the number of packages is over a minute.
> >
>
> After the most recent update (1/30/2005) this no longer seems to be a problem.
>

I take that back. Looks like it still happens that sometimes something doesn't
quite make it across. I updated my computer last night, and this morning
update-notifier still says the same number of updates. If I click and say "show
updates" it says the computer is up to date.

[Michael Vogt (mvo)]

I'm pretty sure that I finally found the root for this problem. It should be
fixed with the upload of update-notifier 0.38.5. If you still see problems with
a not updated update-notifier, please just reopen this bug.

thanks,
 Michael

[JonathanTurner (probata)]

(In reply to comment #10)
> I'm pretty sure that I finally found the root for this problem. It should be
> fixed with the upload of update-notifier 0.38.5. If you still see problems with
> a not updated update-notifier, please just reopen this bug.
>
> thanks,
> Michael

I'm using that version right now. 9 out of 10 times it goes away just fine.
This latest time it took about 10 mins for the update-notifer to disappear.
That doesn't sound like something easy to replicate.

[Michael Vogt (mvo)]

(In reply to comment #11)
> (In reply to comment #10)
> > I'm pretty sure that I finally found the root for this problem. It should be
> > fixed with the upload of update-notifier 0.38.5. If you still see problems with
> > a not updated update-notifier, please just reopen this bug.
>
> I'm using that version right now. 9 out of 10 times it goes away just fine.
> This latest time it took about 10 mins for the update-notifer to disappear.
> That doesn't sound like something easy to replicate.

Can you please see if the latest upload is any better? It works around a problem
in gamin that kept it from getting all the update information.

[JonathanTurner (probata)]

>
> Can you please see if the latest upload is any better? It works around a problem
> in gamin that kept it from getting all the update information.
>

Initial tests looks like this one is much better. One thing I'm a little
curious about, how often does it look for updates? I have to manually look for
package updates before it appears, unless it's set at a longer interval (> 1
day) that I'd expect.

Any thoughts there?

[JonathanTurner (probata)]

> >
> > Can you please see if the latest upload is any better? It works around a problem
> > in gamin that kept it from getting all the update information.
> >
>
> Initial tests looks like this one is much better. One thing I'm a little
> curious about, how often does it look for updates? I have to manually look for
> package updates before it appears, unless it's set at a longer interval (> 1
> day) that I'd expect.
>
> Any thoughts there?

Nevermind, I just wasn't waiting long enough. Everything looks fine now. I'm
going to go ahead and mark this fixed.

[Michael Vogt (mvo)]

(In reply to comment #13)
> >
> > Can you please see if the latest upload is any better? It works around a problem
> > in gamin that kept it from getting all the update information.
> >
>
> Initial tests looks like this one is much better. One thing I'm a little
> curious about, how often does it look for updates? I have to manually look for
> package updates before it appears, unless it's set at a longer interval (> 1
> day) that I'd expect.

The default setting "doing a apt-get udpate (in the background silently) once
per day". If you want it more often, you have to use either synaptic ("reload")
or apt-get update.

Does that mean that the cron job is not triggerd each day? If so, that would be
another bug.

update-notifier itself monitors the update directory of apt/synaptic and notice
changes there in <1minute.

I hope that answers your question :)