Bug 816509

I also reproduced this bug. I have set frequency with gsettings and it still doesn't show up.

I propose this bug as final blocker per final criterion:
The default update manager in release-blocking desktops must not periodically check for updates when the system is booted live, but must periodically check for updates when running on an installed system

Fedora 17-TC2 x86_64 Gnome 3.4
Updated from F17-Beta
Compaq 6910p Core2Duo
Ran updates yesterday from CLI, today didn't run update and ran "Update software" and found 50 updates, no notifications in the system tray

Discussed in the 2012-05-01 blocker bug review meeting. Accepted as a Fedora 16 final blocker as it violates the following beta release criterion [1]:

The default update manager in release-blocking desktops must not periodically check for updates when the system is booted live, but must periodically check for updates when running on an installed system

[1] https://fedoraproject.org/wiki/Fedora_17_Beta_Release_Criteria

(In reply to comment #3)
> Discussed in the 2012-05-01 blocker bug review meeting. Accepted as a Fedora 16
> final blocker as it violates the following beta release criterion [1]:

Whoops, used an old template - I meant Fedora 17

Looking at the settings we have,

frequency-get-updates 86400 How often to check for updates
frequency-updates-notification 604800 How often to notify the user that non-critical updates are available

We check for updates once a day, and notify only once per week for non-critical updates

(In reply to comment #5)
> We check for updates once a day, and notify only once per week for non-critical
> updates

Correct. I spoke with Adam about the procedure to test this properly about two weeks ago. QA:Testcase_desktop_updates needs to be updated to change frequency-updates-notification too.

Richard.

I changed frequency-updates-notification to 900 and it didn't helped. System still didn't show notification even when I wait for one hour.

I agree that we should amend test case.

It works for me with updates from updates testing. I set reasonable frequency time and I got notification.

petr: you have to log out and log back in after changing the frequency-updates-notification setting, we think. and it's all a bit 'temperamental'. so I suspect updates-testing doesn't have much to do with it, and it was more to do with rebooting or restarting the session after you installed the updates.

I think if we just amend the test case, that'll be fine; I don't think this is actually broken.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

I've amended the test case, I think it's okay now. We should re-test with TC2 and no updates to be sure.

I just tested with TC3. The other factor to take into account is that the silent automatic security updating monkeys with things.

I did a clean TC3 install, booted, set all three keys, and waited.

I left it up for 24 minutes, watching htop, and saw a packagekitd and yumBackEnd process hanging around, seemingly not doing much. Nothing got installed.

I got bored, booted to runlevel 3, installed htop and jnettop, and rebooted. I watched with htop and jnettop. I saw it, quite slowly, download the available security updates (including a kernel) and install them. That took about 10 minutes.

Once it was done I verified the transaction with 'yum history' and waited another 10 minutes or so. No further update check seemed to happen. I could probably have waited a bit longer, though.

I rebooted, and after about five minutes, got an update notification.

So I got the notification on the third boot. On the second, the auto-security update happened. On the first...I'm not sure if it was trying to do the auto-security update and  being really slow about it, or just nothing. But it does seem the update notification ultimately works, so I think we can close this bug. I'll update the test case again to advise more patience. :)



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers