F20 offline updates: way too frequent

[Thomas Gilliard]

I found this very annoying when testing for #Fedora-qa where there was a 
long delay on reboot as the updates were applied.

  Automatic downloads can be turned off when not wanted:[1].

It can a risk to leave them turned off in a non-testing environment.

Tom Gilliard


{1}http://wiki.sugarlabs.org/go/Fedora_21#Turn_off_gnome_automatic_background_updates


On 12/28/2013 5:30 PM, Adam Williamson wrote:
> On Sat, 2013-12-28 at 20:36 +0000, Naheem Zaffar wrote:
>> The default notification required a reboot to action.
>>
>> (If you ingore it and shutdown, the updates will not be carried out or
>> prompted at next boot).
>>
>> An issue is that even though you dont hve to reboot straight away,
>> knowing that there are updates that need to be applied through
>> rebooting is itself a nag. Too many and people will get desensitised
>> to the need to apply updates and that is IMO a bad thing.
>>
>> Knowing that your system is not up to date can also cause a feel of
>> unease when using the system.
>>
>> Updates are important but there is a social aspect to them too.
>> physical notification should be on a weekly basis and upon booting the
>> system they should be automatically applied or a prompt given so that
>> you can apply them and not boot, then reboot to get the updates.
> This is actually already how it works, or how it's designed to. It's not
> hard to confirm: read the settings in dconf
> org.gnome.settings-daemon.plugins.updates . It notifies of non-security
> updates once a week, and security updates immediately.