Ubuntu QA:
BlogBrainstormPackage status
Log in
Ubuntu QA
Update manager
Idea sandbox Idea sandbox
Popular ideas Popular ideas
Ideas in development Ideas in development
Implemented ideas Implemented ideas

Popular ideas Here are the last 6 months most popular ideas about Update manager.

update-manager should choose automatically a mirror to update in case of failure  
Written by barrientosa the 14 Apr 12 at 06:14. New
This idea is related to bug #873468 in launchpad (https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/873468)

The problem is sometimes when you are upgrading your distro, there is an upgrade failure due to overloaded mirrors.

Steve Langasek (vorlon) suggested in post #16 that in case that update-manager should offer "the opportunity later to try the upgrade again when it's more likely to succeed", i.e. when mirrors are not so saturated with requests.
84
votes
up equal down
Solution #1: Update manager should silently use alternate mirrors
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.
8
votes
up equal down
Solution #2: Update manager should visible use alternate mirrors
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.

See the 3 comments or propose a solution >>

Simpler import of GPG-keys  
Written by jonasPlatte the 1 Dec 11 at 20:46. New
I think it is too hard to import GPG-keys of repositories that you added in the "Software-sources" settings. If you add a ppa there, the key will not automatically be imported causing a failure when trying to install the program in Software Center ("can't install from untrusted source" or sth like that).
In the commandline, it works perfect: add-apt-repository ask you if you are sure to add the ppa and then imports the GPG-key. Also, apt-get asks you if you want to install from an untrusted source, if the key of a program you are about to install is missing.
48
votes
up equal down
Solution #1: Import the GPG-keys automatically
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.
29
votes
up equal down
Solution #2: Add possibility to install / update from untrusted sources
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.

See the 1 comments or propose a solution >>

Update manager should notify in advance if installing updates needs rebooting.  
Written by amoalsale the 3 May 12 at 04:52. New
Many times when we get notification that updates are available for the system we often click on install update button without even looking at the details as we know keeping the system up-to-date keeps it stable. But many times once updating is finished systems asks for reboot and everytime its not possible to reboot immediately. For example when we are working on remote sessions on telnet or ssh or editing something important on internet.
It may also be observed that untill you do not reboot the system it behaves irratically.
26
votes
up equal down
Solution #1: Update manager should notify if updates require reboot.
Written by amoalsale the 3 May 12 at 04:52.
a simple notification like
"Installing these updates will require reboot"
should be shown in advance.
5
votes
up equal down
Solution #2: Service restart
Written by benoyanthony the 15 May 12 at 10:09.
Other than complete reboot, system should initiate service restart with confirmation from user.

See the 5 comments or propose a solution >>

Software Cannot Be Uninstalled from the Software Update Notification Window  
Written by foxmajik the 26 Jan 12 at 21:09. New
In the Android Market when I am presented an app update there is an uninstall button as well.

This often makes me go "oh I forgot that app was installed, I'll go ahead and uninstall it" or "I don't want that update, I'd rather uninstall that app" or "I didn't realize that application was installed and I don't need it so I'll remove it to save bandwidth and disk space."
-9
votes
up equal down
Solution #1: Place an Uninstall Button for Packages on the Software Update Window
Written by foxmajik the 26 Jan 12 at 21:09.
Ubuntu the only option is to uncheck the update and have it come back next time updates are presented. I have to use a separate tool to make the notification go away permanently.

I propose adding an uninstall button directly on the update window to reduce the number of steps required to make an unwanted application go away.
-10
votes
up equal down
Solution #2: Right-click menu item
Written by christopher_lees the 28 Jan 12 at 09:44.
Right-click on the package you want to remove, and then click on "Remove Package" in the menu.

This would be a less cluttersome solution.

After selecting "Remove Package" it would warn you of any other changes needed to be made (such as removing dependent packages) and then recalculate the update.
17
votes
up equal down
Solution #3: Add a "View in Software Centre" button
Written by JW_00000 the 9 Feb 12 at 20:02.
I propose to add a link to that package in the Ubuntu Software Centre. That way, if you don't remember what the package was for, or if you wanted to remove it, or if you wanted to rate the package or comment on it, or anything else, you could click this "View in Software Centre" option, and do what you want there.

This option could be added in a right click menu, or as a button, or whatever seems most fit.
-3
votes
up equal down
Solution #4: Combine solution 1 and 3: Both "uninstall"- and "view in software center"-button
Written by eklem the 22 Feb 12 at 10:32.
Let the user easily remove a package, or choose to get more info/rate etc from Software center.
5
votes
up equal down
Solution #5: Only Software Center
Written by grissir the 22 Feb 12 at 21:24.
The software-center should performe updates, without an extra program

See the 1 comments or propose a solution >>

The update-manager is very outdated  
Written by fernando_silva the 2 May 12 at 00:43. New
The update-manager is very outdated and it's not integrated with the rest of the system.
6
votes
up equal down
Solution #1: Integrate the update-manager to the "Software Centre"
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".

See the 5 comments or propose a solution >>

Include prior kernels in the repositories  
Written by lewac the 7 May 12 at 15:38. New
Recently we upgraded to 12.04 from 11.10, kubuntu 32 bit. And lost google-earth in the process (OS freezes). There's a bug report on it but its not fixed yet. So to make things a bit easier why not retain a coupla previous kernels within the repositories? That way what worked prior to updates/upgrades will probably work again (if it happens to be a kernel issue like this one).

One may require some type of "Regress" checkbox within the package maintainers (synaptic, muon, whatever)... or a new source list could be implemented to make the prior kernel(s) available.

Of course would not normally regress unless a specific app critical to normal usage went bust from a subsequent kernel update (such as was my (and many others) situation).
3
votes
up equal down
Solution #1: Add a repository
Written by lewac the 7 May 12 at 15:38.
which would include at least a couple of past kernels.

See the 1 comments or propose a solution >>