Written by zago84 the 22 Nov 12 at 13:32.

I think it's really useful if during upgrade process, by a drop-down menu in the same update manager window, you can choose the behavior before the end one of them:

- no action
- restart
- turn off

I thought about a drop-down menu that allow you to change your choice at any time during upgrade. Or more simply and less invasively a drop-down menu hidden under a simple icon like a gear.

So, after starting update process, you can get away from the PC and it will do what you choose.

I think it's really useful if during upgrade process, by a drop-down menu in the same update manager window, you can choose the behavior before the end one of them: - no action - restart - turn off I thought about a drop-down menu that allow you to change your choice at any time during upgrade. Or more simply and less invasively a drop-down menu hidden under a simple icon like a gear. So, after starting update process, you can get away from the PC and it will do what you choose.

Written by mikysett the 3 Dec 12 at 16:57.

If the size of the upgrade is really big, when you click on "update" a pop-up will appear telling: "Download and install all this stuff will take a lot of time for me, perhaps you wont be there then anymore, do you want I shoot down automatically when I've done?", with "yes", "no" and "config" buttons.
With this solution you can add in the parameters the minimum size of the download to make the pop-up appear.

So people can make the choice they want without having additional buttons to care about.

If the size of the upgrade is really big, when you click on "update" a pop-up will appear telling: "Download and install all this stuff will take a lot of time for me, perhaps you wont be there then anymore, do you want I shoot down automatically when I've done?", with "yes", "no" and "config" buttons. With this solution you can add in the parameters the minimum size of the download to make the pop-up appear. So people can make the choice they want without having additional buttons to care about.

Written by barrientosa the 14 Apr 12 at 06:14.

I think it's nice to show a message to users in case of failure, however it would save time if the update-manager can just check other servers around if your local mirror is overloaded and proceed with the upgrade silently without bothering you.

Nevertheless as a last resource I agree that update-manager should show some sort of message to the user, but only in case that all the mirrors are collapsed or something like that.

I think it's nice to show a message to users in case of failure, however it would save time if the update-manager can just check other servers around if your local mirror is overloaded and proceed with the upgrade silently without bothering you. Nevertheless as a last resource I agree that update-manager should show some sort of message to the user, but only in case that all the mirrors are collapsed or something like that.

Written by puxkggn the 28 Apr 12 at 13:17.

Update manager should not be doing fall backs something without showing a message to the user that it does.
In this case the Update manager should pick another one until it has either found a working mirror or doesn't find one.
In the found a working mirror it displays a message to the user while continuing. (The message is for information not for confirmation.) And in the latter it's of course impossible to continue.

Update manager should not be doing fall backs something without showing a message to the user that it does. In this case the Update manager should pick another one until it has either found a working mirror or doesn't find one. In the found a working mirror it displays a message to the user while continuing. (The message is for information not for confirmation.) And in the latter it's of course impossible to continue.

Written by Aielyn the 4 Oct 12 at 12:34.

While Solutions #1 and #2 are good in general, it is not always appropriate to have the update manager automatically pull files from an alternate mirror without allowing the user input.

For instance, for some, there are limits to downloads from most mirrors, but unlimited downloads from certain ISP-related mirrors. This occurs with Telstra in Australia, where file downloads from the AARNet Mirror are unlimited. For large updates, a switch to a different mirror could result in a significant dent in the download limit for the user. However, for small updates, the user might not be overly concerned, and may allow it anyway.

Which of the approaches to use could be set on first use of the Update manager, with "Silent" being the default option (as many users do not require information on alternate mirror usage at all) and the other options being "Automatic", "Manual", and "Off", with obvious meanings.

While Solutions #1 and #2 are good in general, it is not always appropriate to have the update manager automatically pull files from an alternate mirror without allowing the user input. For instance, for some, there are limits to downloads from most mirrors, but unlimited downloads from certain ISP-related mirrors. This occurs with Telstra in Australia, where file downloads from the AARNet Mirror are unlimited. For large updates, a switch to a different mirror could result in a significant dent in the download limit for the user. However, for small updates, the user might not be overly concerned, and may allow it anyway. Which of the approaches to use could be set on first use of the Update manager, with "Silent" being the default option (as many users do not require information on alternate mirror usage at all) and the other options being "Automatic", "Manual", and "Off", with obvious meanings.

Written by fernando_silva the 2 May 12 at 00:43.

Add an new item on the top of the "Software Centre", on the right side, called "System Updates", and create a more simple user-interface for the update-manager, integrated to the "Software Centre".

Add an new item on the top of the "Software Centre", on the right side, called "System Updates", and create a more simple user-interface for the update-manager, integrated to the "Software Centre".

Written by arjo129 the 15 Jan 12 at 03:00.

A seperate icon should appear in the topo right hand corner with a notification claiming that the system needs to be updated. When updating a package one can simply check the progress by clicking on the icon.

A seperate icon should appear in the topo right hand corner with a notification claiming that the system needs to be updated. When updating a package one can simply check the progress by clicking on the icon.

Written by deltrem the 21 Jan 12 at 19:46.

Mozilla is implementing a series of improvements to Firefox called Silent Update, because Mozilla received feedback that Firefox updates were too obtrusive.

Since Firefox is open source and since Ubuntu updates are too obtrusive, let's copy Silent Update from Firefox to Ubuntu.

The Silent Update improvements are:
- Lessen how often the “What’s New” page is shown
- Lessen how often the update user interface is displayed
- Add-ons Default to Compatible
- Apply updates on shutdown
- Improved process flow for updating when there are incompatible add-ons

http://blog.mozilla.com/futurereleases/2011/10/04/mozilla-firefox-and-silent-up dates/
https://wiki.mozilla.org/Features/Release_Tracking

Mozilla is implementing a series of improvements to Firefox called Silent Update, because Mozilla received feedback that Firefox updates were too obtrusive. Since Firefox is open source and since Ubuntu updates are too obtrusive, let's copy Silent Update from Firefox to Ubuntu. The Silent Update improvements are: - Lessen how often the “What’s New” page is shown - Lessen how often the update user interface is displayed - Add-ons Default to Compatible - Apply updates on shutdown - Improved process flow for updating when there are incompatible add-ons http://blog.mozilla.com/futurereleases/2011/10/04/mozilla-firefox-and-silent-updates/ https://wiki.mozilla.org/Features/Release_Tracking

Written by primefalcon the 25 Jan 12 at 01:59.

This way everything would be handled through Ubuntu's software centre

This way everything would be handled through Ubuntu's software centre

Written by arjo129 the 1 Feb 12 at 10:01.

This does not solve the fact that a seperate indicator pops up but it deals with the fact that the progress bar hovers over the desktop by putting the progress bar as a menu indicator.

This does not solve the fact that a seperate indicator pops up but it deals with the fact that the progress bar hovers over the desktop by putting the progress bar as a menu indicator.

Written by jonasPlatte the 1 Dec 11 at 20:46.

The GPG-key should automatically be imported when you add a ppa using the "Software-sources" settings.
But, for security reasons, there should not only be a prompt to type your password, but a prompt that tells you for example that the operation you want to do could be dangerous for the system and that you should only do this if you trust the source.

The GPG-key should automatically be imported when you add a ppa using the "Software-sources" settings. But, for security reasons, there should not only be a prompt to type your password, but a prompt that tells you for example that the operation you want to do could be dangerous for the system and that you should only do this if you trust the source.

Written by jonasPlatte the 1 Dec 11 at 20:52.

I also think it would be good that when you try to install (Software Center) or update (Update Manager) some packages, which source is "untrusted" (no GPG-key of the author imported) then you should get a prompt that asks you if you are really sure to install / update that package(s) instead of getting an failure dialog box.

I also think it would be good that when you try to install (Software Center) or update (Update Manager) some packages, which source is "untrusted" (no GPG-key of the author imported) then you should get a prompt that asks you if you are really sure to install / update that package(s) instead of getting an failure dialog box.

Written by bufke the 11 Oct 11 at 21:38.

run dpkg --configure -a on boot if auto updates are turned on. This way the updates have a chance to finish. Ideally the user would be notified of this so that they don't assume the computer is not broken and hard shutdown again.

run dpkg --configure -a on boot if auto updates are turned on. This way the updates have a chance to finish. Ideally the user would be notified of this so that they don't assume the computer is not broken and hard shutdown again.

Written by abdulet the 18 Oct 11 at 12:55.

Instead of run dpgk --configure -a each boot, register the different steps of the update process, at boot time check if there is any problem and run dpkg if needed

Instead of run dpgk --configure -a each boot, register the different steps of the update process, at boot time check if there is any problem and run dpkg if needed

Written by mactrent the 27 Oct 11 at 17:52.

When Update Manager starts and encounters an error as described above, it tells the user to run dpkg to reconfigure.
Is there a reason it doesn't simply run automatically?

When Update Manager starts and encounters an error as described above, it tells the user to run dpkg to reconfigure. Is there a reason it doesn't simply run automatically?